diff mbox

[wwwdocs] Reduce references to stages in develop.html

Message ID alpine.LNX.2.00.1202122058010.5509@gerinyyl.fvgr
State New
Headers show

Commit Message

Gerald Pfeifer Feb. 12, 2012, 8:54 p.m. UTC 
This is in preparation of some potentially future changes in
relation to the currently confusing naming of Stages 1 and 3.

It reduces references to concrete stages and slightly reformats
here and there.

Committed.

Gerald
diff mbox

Patch

Index: develop.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/develop.html,v
retrieving revision 1.121
diff -u -3 -p -r1.121 develop.html
--- develop.html	12 Feb 2012 19:32:38 -0000	1.121
+++ develop.html	12 Feb 2012 19:52:17 -0000
@@ -106,14 +106,14 @@  compiler.  In particular, major changes 
 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
 major projects proposed for the coming release cycle before the start
-of Stage 1.  They will attempt to sequence the projects
+of this stage.  They will attempt to sequence the projects
 in such a way as to cause minimal disruption.  The Release Managers
 will not reject projects that will be ready for inclusion before the
-end of Stage 1.  Similarly, the Release Managers have no special power
-to accept a particular patch or branch beyond what their status
-as maintainers affords.  The role of the Release Managers during Stage 1
-is merely to attempt to order the inclusion of major features in an
-organized manner.</p>
+end of Stage 1.  Similarly, the Release Managers have no special
+power to accept a particular patch or branch beyond what their status
+as maintainers affords.  The role of the Release Managers is merely
+to attempt to order the inclusion of major features in an organized
+manner.</p>
 
 <h4><a name="stage2">Stage 2</a></h4>
 
@@ -135,7 +135,7 @@  release.  Therefore, more radical change
 cycle, so that we have time to fix any problems that result.</p>
 
 <p>In order to reach higher standards of quality, we must focus on
-fixing bugs; by working exclusively on bug-fixing through Stage 3
+fixing bugs; by working exclusively on bug-fixing through this stage
 and before branching for the release, we will have a higher quality
 source base as we prepare for a release.</p>
 
@@ -196,8 +196,8 @@  remain working, to avoid impeding other 
 
 <h3>Schedule</h3>
 
-<p>At the conclusion of Stage 3, the trunk will go into release branch
-mode which allows documentation and regression fixes only.
+<p>At the conclusion of Stage 3, the trunk will go into release
+branch mode which allows documentation and regression fixes only.
 During this phase, the focus will be fixing any regressions
 from the previous release, so that each release is better than the one
 before.</p>