Changes between Version 8 and Version 9 of ReleaseSchedule


Ignore:
Timestamp:
Feb 11, 2009, 1:03:39 PM (14 years ago)
Author:
Beman Dawes
Comment:

Change to first day of second month of each quarter

Legend:

Unmodified
Added
Removed
Modified

  • ReleaseSchedule

    v8 v9  
    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  * '''November 3, 2008:''' branches/release opens for merging 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.
    87 * '''December 20, 2008:''' branches/release closed for new libraries and breaking changes to existing libraries. Still open for bug fixes and other routine changes to all libraries.
    98 * '''January 3, 2009:''' branches/release closed for major code changes. Still open for serious problem fixes and docs changes.
    … …  
    1413== Future Releases ==
    1514
    16 Releases are scheduled for the last day of the first month of each quarter:
     15Releases are scheduled for the first day of the second month of each quarter:
    1716
    18  * January 31
    19  * April 30
    20  * July 31
    21  * October 31
     17 * February 1
     18 * May 1
     19 * August 1
     20 * November 1
    2221
    2322Release milestones
    2423
    25  * One week after prior release ships: branches/release opens for merging 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.
     24 * One week after prior release ships: branches/release opens for merging 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.'''
    2625 * Seven weeks before release: branches/release closed for new libraries and breaking changes to existing libraries. Still open for bug fixes and other routine changes to all libraries.
    2726 * Five weeks before release: QA checks on snapshot doc builds, inspect status, getting started guide, and install.