Changes between Version 1 and Version 2 of proposals/release_strategy


Ignore:
Timestamp:
04/27/10 10:08:28 (15 years ago)
Author:
fxp
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • proposals/release_strategy

    v1 v2  
    11== Current release strategy ==
    2 Release strategy:
    3  * Stable releases are created on a time schedule: every six months
    4  * Release Candidate 1 is built two weeks after RC0
    5  * Release Candidate 2 is built two weeks after RC1
    6  * Final Release is built two weeks after RC2
    7 
    8 The Project Steering Committee (PSC) can postpone a release by vote on the mailing list.
    9 
    10 Branch strategy:
    11  * Trunk is for development and is automatically built with uneven version numbers
    12  * Even numbered branch is created from trunk on code freeze (version RC0)
    13  * Automated builds based on trunk will use the next uneven version number immediately after code freeze
    14  * Fixes are committed to both trunk and even numbered branch
    15  * Release Candidates are built from the even numbered branch
    16 
    17 For releasing files on sourceforge.net follow [http://apps.sourceforge.net/trac/sourceforge/wiki/Release%20files%20for%20download these instructions] (release manager only)
    18 
    19 Uploading can be done through SCP with the following command: {{{scp FILE jsmith@frs.sourceforge.net:uploads}}}
     2[wiki:release_strategy]
    203
    214== Comments & new questions ==
    225 * We don't have automatic build system.
    23  * Where to annouce even/uneven release ?
    24  * Where to release even/uneven release ? Separate folders ?
    25  * What's an "unstable" or alpha release ?
    26  * When is alpha release made ?
     6 * Where to annouce stable/"unstable" release ?
     7 * Where to release stable/"unstable" release ? Separate folders ?
     8 * What's an "unstable" release ? alpha release ?
     9 * When is "unstable" release made ?
    2710
    2811== Proposal ==
     
    3922The Project Steering Committee (PSC) can postpone a stable release by vote on the mailing list.
    4023
    41 Between two stable releases, one or more alpha releases could be created. Alpha releases can be unstable.
     24Between two stable releases, one or more alpha releases could be created. Alpha release can be unstable.
    4225
    4326Release strategy for alpha release: