Changes between Version 2 and Version 3 of ReleaseSchedule


Ignore:
Timestamp:
Aug 18, 2008, 8:00:26 PM (14 years ago)
Author:
Beman Dawes
Comment:

Update for 1.37.0

Legend:

Unmodified
Added
Removed
Modified

  • ReleaseSchedule

    v2 v3  
    55'''Note well: Changes must always be committed to trunk and be stable on trunk regression testing before being merged to branches/release.'''
    66
    7  * '''May, 2008:''' branches/release opens for all stable changes, including bug fixes, major library upgrades, and, with permission, new libraries. Breaking changes should be coordinated with libraries affected.
    8  * '''June 19, 2008:''' branches/release closes for new libraries and major upgrades or breaking changes to existing libraries. Still open for bug fixes and minor changes to all libraries.
    9  * '''July  3, 2008:''' branches/release closes for routine minor changes and fixes. Still open for serious problem fixes.
    10  * '''July 10, 2008:''' branches/release closes for all library changes except when specific permission given by release manager(s).
    11  * '''July 17, 2008 (sooner if possible):''' Beta 1 target date. Further betas and/or release candidates as feedback dictates.
    12  * '''July 31, 2008:''' Release ship date.
     7 * '''August 18, 2008:''' branches/release opens for all stable changes, including bug fixes, and major upgrades to existing libraries. Breaking changes should be coordinated with libraries affected. New libraries may be added with permission of a release manager.
     8 * '''September 19, 2008:''' branches/release branches/release closed for routine code changes and fixes. Still open for serious problem fixes and docs changes.
     9 * '''October  3, 2008:''' branches/release closed for routine code changes and fixes. Still open for serious problem fixes and docs changes.
     10 * '''October 10, 2008:''' branches/release closed for all library changes except when specific permission given by release manager(s).
     11 * '''October 17, 2008:''' Beta release target date. Further betas and/or release candidates as feedback dictates.
     12 * '''October 31, 2008:''' Release ship date.
    1313
    1414== Future Releases ==
    … …  
    2323Release milestones
    2424
    25  * One week after prior release ships: branches/release opens for all stable changes, including bug fixes, major library upgrades, and, with permission, new libraries. Breaking changes should be coordinated with libraries affected.
    26  * Six weeks before release: branches/release closes for new libraries and major upgrades or breaking changes to existing libraries. Still open for bug fixes and minor changes to all libraries.
    27  * Four weeks before release: branches/release closes for routine minor changes and fixes. Still open for serious problem fixes.
    28  * Three weeks before release: branches/release closes for all library changes except when specific permission given by release manager(s).
    29  * Two weeks before release (sooner if possible): Beta 1 target date. Further betas and/or release candidates as feedback dictates.
     25 * One week after prior release ships: branches/release opens for all stable changes, including bug fixes, and major upgrades to existing libraries. Breaking changes should be coordinated with libraries affected. New libraries may be added with permission of a release manager.
     26 * Six weeks before release: branches/release closes for new libraries and major upgrades or breaking changes to existing libraries. Still open for bug fixes and other minor changes to all libraries.
     27 * Four weeks before release: branches/release closed for routine code changes and fixes. Still open for serious problem fixes and docs changes.
     28 * Three weeks before release: branches/release closed for all library changes except when specific permission given by release manager(s).
     29 * Two weeks before release: Beta target date. Further betas and/or release candidates as feedback dictates.
    3030
    3131== Schedule Rationale ==