Changes between Version 12 and Version 13 of ReleaseSchedule


Ignore:
Timestamp:
Nov 27, 2009, 2:17:01 PM (13 years ago)
Author:
Beman Dawes
Comment:

Remove exact dates; the calendar now serves this purpose

Legend:

Unmodified
Added
Removed
Modified

  • ReleaseSchedule

    v12 v13  
    11= Release Schedule =
    2 
    3 == Next Release ==
    4 
    5 '''Note well: Changes must always be committed to trunk and be stable on trunk regression testing before being merged to branches/release.'''
    6 
    7  * '''September 13, 2009:''' branches/release closed for new libraries and breaking changes to existing libraries. Still open for bug fixes and other routine changes to all libraries.
    8  * '''September 20, 2009:''' Release managers start QA checks.
    9  * '''October 4, 2009:''' branches/release closed for major code changes. Still open for serious problem fixes and docs changes.
    10  * '''October 11, 2009:''' branches/release closed for all library changes except when specific permission given by release manager(s).
    11  * '''October 18, 2009:''' Beta release target date. Further betas and/or release candidates as feedback dictates.
    12  * '''November 1, 2009:''' Release ship date.
    13 
    14 == Future Releases ==
    152
    163Releases are scheduled for the first day of the second month of each quarter:
    … …  
    229
    2310Release milestones
     11
     12'''Note well: Changes must always be committed to trunk and be stable on trunk regression testing before being merged to branches/release.'''
    2413
    2514 * 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.'''