Changes between Version 1 and Version 2 of release_strategy


Ignore:
Timestamp:
04/07/08 01:32:17 (17 years ago)
Author:
arnulf
Comment:

typos

Legend:

Unmodified
Added
Removed
Modified

  • TabularUnified release_strategy

    v1 v2  
    11Release strategy:
    22 * Stable releases are created on a time schedule: every six months
    3  * Release Candidate 1 is build two weeks after RC0
    4  * Release Candidate 2 is build two weeks after RC1
    5  * Final Release is build two weeks after RC2
     3 * Release Candidate 1 is built two weeks after RC0
     4 * Release Candidate 2 is built two weeks after RC1
     5 * Final Release is built two weeks after RC2
    66
    77The Technical Steering Committee (TSC) can postpone a release by vote on the mailing list.
    88
    99Branch strategy:
    10  * Trunk is for development and is automatically build with uneven version numbers
     10 * Trunk is for development and is automatically built with uneven version numbers
    1111 * Even numbered branch is created from trunk on code freeze (version RC0)
    1212 * Automated builds based on trunk will use the next uneven version number immediately after code freeze
    1313 * Fixes are committed to both trunk and even numbered branch
    14  * Release Candidates are build from the even numbered branch
     14 * Release Candidates are built from the even numbered branch
    1515