From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 8682 invoked by alias); 11 Jun 2012 09:18:38 -0000 Received: (qmail 8672 invoked by uid 22791); 11 Jun 2012 09:18:37 -0000 X-SWARE-Spam-Status: No, hits=-4.9 required=5.0 tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,KHOP_RCVD_TRUST,KHOP_THREADED,RCVD_IN_DNSWL_LOW,RCVD_IN_HOSTKARMA_YE X-Spam-Check-By: sourceware.org Received: from mail-ob0-f175.google.com (HELO mail-ob0-f175.google.com) (209.85.214.175) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Mon, 11 Jun 2012 09:18:23 +0000 Received: by obhx4 with SMTP id x4so7302062obh.20 for ; Mon, 11 Jun 2012 02:18:23 -0700 (PDT) MIME-Version: 1.0 Received: by 10.60.26.133 with SMTP id l5mr15570784oeg.28.1339406303250; Mon, 11 Jun 2012 02:18:23 -0700 (PDT) Received: by 10.76.83.230 with HTTP; Mon, 11 Jun 2012 02:18:23 -0700 (PDT) In-Reply-To: References: <4EA8296F.2020300@redhat.com> Date: Mon, 11 Jun 2012 09:18:00 -0000 Message-ID: Subject: Re: Renaming Stage 1 and Stage 3 From: Richard Guenther To: Gerald Pfeifer Cc: gcc@gcc.gnu.org, Ian Lance Taylor Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-IsSubscribed: yes Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-owner@gcc.gnu.org X-SW-Source: 2012-06/txt/msg00136.txt.bz2 On Mon, Jun 11, 2012 at 12:03 AM, Gerald Pfeifer wrote: > On Mon, 31 Oct 2011, Ian Lance Taylor wrote: >> No opinion on your actual question, but note that there is no more >> stage2. =A0We now go directly from stage1 to stage3. =A0This is just ano= ther >> feature of gcc development seemingly designed to confuse newbies, and >> evidently even confuses experienced developers. > > So, let's fix this! =A0In fact, this is something Mark, David and me > discussed at the last GCC Summit and which fell through the cracks > on my side. > > Instead of renaming Stage 3 to Stage 2 at that point we figured that > using different terminology would reduce confusion. =A0I am not wedded > to Stage A and B, though this seems to be the most straightforward > option (over colors, Alpha and Beta carrying a different meaning in > software development,...). > > Thoughts? Eh - why not give them names with an actual meaning? "Development Stage" and "Stabilizing Stage"? I realize those are rather long names, but you can always put short forms in tables, like Dev Stage and Stab Stage. Richard. > Gerald > > Index: develop.html > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > RCS file: /cvs/gcc/wwwdocs/htdocs/develop.html,v > retrieving revision 1.127 > diff -u -3 -p -r1.127 develop.html > --- develop.html =A0 =A0 =A0 =A022 Mar 2012 07:57:04 -0000 =A0 =A0 =A01.1= 27 > +++ develop.html =A0 =A0 =A0 =A010 Jun 2012 21:54:42 -0000 > @@ -97,30 +97,27 @@ well), then we can seriously confuse use > > =A0

Schedule

> > -

Development on our main branch will proceed in three stages.

> +

Development on our main branch will proceed as two main stages > +followed by concrete preparations for the release.

> > -

Stage 1

> +

Stage A

> > =A0

During this period, changes of any nature may be made to the > =A0compiler. =A0In particular, major changes may be merged from branches. > -Stage 1 is feature driven and will last at least four months. > -In order to avoid chaos, the Release Managers will ask for a list of > +Stage A is feature driven and will last at least four months.

> + > +

In order to avoid chaos, the Release Managers will ask for a list of > =A0major projects proposed for the coming release cycle before the start > =A0of this stage. =A0They will attempt to sequence the projects > =A0in such a way as to cause minimal disruption. =A0The Release Managers > =A0will not reject projects that will be ready for inclusion before the > -end of Stage 1. =A0Similarly, the Release Managers have no special > +end of this stage. =A0Similarly, the Release Managers have no special > =A0power to accept a particular patch or branch beyond what their status > =A0as maintainers affords. =A0The role of the Release Managers is merely > -to attempt to order the inclusion of major features in an organized > +to help order the inclusion of major features in an organized > =A0manner.

> > -

Stage 2

> - > -

Stage 2 has been abandoned in favor of an extended feature driven > -Stage 1 since the development of GCC 4.4.

> - > -

Stage 3

> +

Stage B

> > =A0

During this two-month period, the only (non-documentation) changes > =A0that may be made are changes that fix bugs or new ports which do not > @@ -196,7 +193,7 @@ remain working, to avoid impeding other > > =A0

Schedule

> > -

At the conclusion of Stage 3, the trunk will go into release > +

At the conclusion of Stage B, the trunk will go into release > =A0branch mode which allows documentation and regression fixes only. > =A0During this phase, the focus will be fixing any regressions > =A0from the previous release, so that each release is better than the one > @@ -204,7 +201,7 @@ before.

> > =A0

At the point the trunk is in a state suitable for releasing > =A0a release branch will be created, a release candidate is made available > -and Stage 1 of the next release cycle starts. > +and Stage A of the next release cycle starts. > =A0The decision on when this point is reached is up to the Release Manage= rs. > =A0In particular at this point no P1 regressions are present on the trunk= .

> > @@ -460,7 +457,7 @@ stages of development, branch points, an > =A0 =A0 =A0 =A0+-- GCC 4.7 branch created ------+ > =A0 =A0 =A0 =A0| =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 \ > =A0 =A0 =A0 =A0v =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 =A0v > - =A0GCC 4.8 Stage 1 (starts 2012-03-02) =A0 =A0 =A0GCC 4.7.0 release (20= 12-03-22) > + =A0GCC 4.8 Stage A (starts 2012-03-02) =A0 =A0 =A0GCC 4.7.0 release (20= 12-03-22) > =A0 =A0 =A0 =A0| > =A0 =A0 =A0 =A0| > =A0 =A0 =A0 =A0v