Changes between Version 16 and Version 17 of RFC/4_ReleaseProcedure

Timestamp:

01/07/15 18:55:35 (10 years ago)

Author:

helena

Comment:

--

RFC/4_ReleaseProcedure

@@ -23 +23 @@
 
 Step 1 - Proposal of release:
-   When a developer feels that it is time for a new release, she or he should propose the launch of a new release process on the developers mailing list ([http://lists.osgeo.org/mailman/listinfo/grass-dev grass-dev AT lists.osgeo.org]). The Project manager (or if exists the Release manager) then collects reactions to decide whether there is sufficient support for this proposal.
+   When a developer feels that it is time for a new release, she or he should propose the launch of a new release process on the developers mailing list ([http://lists.osgeo.org/mailman/listinfo/grass-dev grass-dev AT lists.osgeo.org]). The Project manager (or if exists the Release manager) then collects reactions and decides whether there is sufficient support for this proposal.
 
 Step 2 (day X) - Soft freeze of release branch:
    * If support is lacking, a list of outstanding issues (managed via http://trac.osgeo.org/grass/) that need to be solved before a soft freeze should be sent to the developers mailing list. 
-   * If sufficient support is present, a first announcement is sent by the Release manager to the developers mailing list about the upcoming release along with a trac planning page (section). This announcement has as immediate effect a soft freeze meaning that commits should be limited to non-invasive backports from the development branch/trunk. The announcement mail also contains an approximate time table for the release, including begin of hard freeze, RC1, RC2, final release and the link to the trac page. Sufficient time should be left between the soft freeze and the hard freeze. Any backports during the soft freeze should be announced on the developers mailing list with 24 hours advance to allow possible discussion.
+   * If sufficient support is present, the first announcement is sent by the Release manager to the developers mailing list about the upcoming release along with a trac planning page (section). Immediate effect of this announcement is a soft freeze, meaning that commits should be limited to non-invasive backports from the development branch/trunk. The announcement should also include an approximate time table for the release, including the start of hard freeze, RC1, RC2, final release and the link to the trac page. Sufficient time should be left between the soft freeze and the hard freeze. Any backports during the soft freeze should be announced on the developers mailing list with 24 hours advance to allow possible discussion.
 
 Step 3 (X+30 days) - Hard freeze & RC1:
-   Once any necessary backports are done, a hard freeze is announced by the Release manager and RC1 is released based on the frozen code (release branch).
+   Once all necessary backports are done, a hard freeze is announced by the Release manager and RC1 is released based on the frozen code (release branch).
 
 Step 4 - Bug squashing: