This is the mail archive of the
mailing list for the GCC project.
Re: GCC 3.3 branch open
The rules have always been that fixes on the release branch and for
I do make exceptions, where warranted, and I will continue to do that.
However, the threshold is pretty high. Largely, the point of the bug-fix
releases is to remove obstacles that are preventing people from upgrading to
the current release series. A bug that has always existed does not
constitute such an obstacle.
----- Original Message -----
From: "Kelley Cook" <email@example.com>
To: "Mark Mitchell" <firstname.lastname@example.org>
Sent: Friday, August 08, 2003 12:00 PM
Subject: Re: GCC 3.3 branch open
> Mark Mitchell wrote:
> > The 3.3 branch is now open, under the usual regression-only check-in
> > rules.
> Is this really the usual checkin rules for a branch?
> For example after 3.1 was released you said:
> > 1. Anyone who can normally approve patches can approve patches that
> > fix regressions from previously released versions of GCC.
> > 2. I will review and approve patches that do not fix regressions if
> > a) they appear safe
> > b) they fix very important problems, or
> > c) they add support for new platforms, language features, etc.
> > that we did not support before -- and that we cannot, therefore,
> > be regressing.
> > Please make your case explicitly; assume I know very little (a
> > good assumption!) and explain why your patch fits these criteria.
> -- http://gcc.gnu.org/ml/gcc/2002-05/msg01212.html
> I thought regression-only was only the requirement when the next release
> was close. I personally would think that important bug fixes should not
> necessarily have to wait for 3.4, even if that bug has been always
> present in GCC.
> You, of course, are the release manager, so it is your call to make.
> Kelley Cook