Changes between Version 5 and Version 6 of ReleaseSchedule


Ignore:
Timestamp:
Oct 21, 2008, 12:51:52 PM (14 years ago)
Author:
Beman Dawes
Comment:

Add a five week milestore for QA

Legend:

Unmodified
Added
Removed
Modified

  • ReleaseSchedule

    v5 v6  
    2525 * 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.
    2626 * Six weeks before release: branches/release closed 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 * Five weeks before release: QA checks on snapshot doc builds, inspect status, getting started guide, and install.
    2728 * Four weeks before release: branches/release closed for routine code changes and fixes. Still open for serious problem fixes and docs changes.
    2829 * Three weeks before release: branches/release closed for all library changes except when specific permission given by release manager(s).