Changes between Version 12 and Version 13 of RFC/4_ReleaseProcedure

Timestamp:

Jan 6, 2015, 5:43:58 PM (9 years ago)

Author:

smitch

Comment:

2 small grammar fixes plus remove tbd based on email list traffic

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 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 to decide whether there is sufficient support for this proposal.
 
 Step 2 (day X) - Soft freeze:
    * 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 the developers mailing list about the upcoming release. 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. 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, a first announcement is sent to the developers mailing list about the upcoming release. 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. 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:
@@ -33 +33 @@
 
 Step 4 - Bug squashing:
-   All developers concentrate on fixing the remaining bugs during a defined period of no more than 2 weeks. Any commits from that point on can only be well-tested, non-invasive bug fixes. ~~[tbd: a specific svn branch with access limited to a release team of 2-3 developers can be created. Any fix has to be sent to the release team for approval and commit.]~~
+   All developers concentrate on fixing the remaining bugs during a defined period of no more than 2 weeks. Any commits from that point on can only be well-tested, non-invasive bug fixes. 
 
 Step 5 (X+44 days) - RC2: