Changes between Version 4 and Version 5 of ReleaseSchedule
- Timestamp:
- Aug 18, 2008, 8:23:53 PM (14 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
ReleaseSchedule
v4 v5 6 6 7 7 * '''August 18, 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. 8 * '''September 19, 2008:''' branches/release branches/release closed for routine code changes and fixes. Still open for serious problem fixes and docs changes.8 * '''September 19, 2008:''' 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. 9 9 * '''October 3, 2008:''' branches/release closed for routine code changes and fixes. Still open for serious problem fixes and docs changes. 10 10 * '''October 10, 2008:''' branches/release closed for all library changes except when specific permission given by release manager(s). … … 24 24 25 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. 26 * Six weeks before release: branches/release close sfor new libraries and major upgrades or breaking changes to existing libraries. Still open for bug fixes and other minor changes to all libraries.26 * 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 27 * Four weeks before release: branches/release closed for routine code changes and fixes. Still open for serious problem fixes and docs changes. 28 28 * Three weeks before release: branches/release closed for all library changes except when specific permission given by release manager(s).