| 28 | | If support is lacking, a list of outstanding issues 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 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. 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. |
| | 28 | * 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. |
| | 29 | * If sufficient support is present, a first announcement is sent 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. |
