Changes between Version 3 and Version 4 of ReleaseSchedule
- Timestamp:
- Aug 18, 2008, 8:09:50 PM (14 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
ReleaseSchedule
v3 v4 5 5 '''Note well: Changes must always be committed to trunk and be stable on trunk regression testing before being merged to branches/release.''' 6 6 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.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 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 9 * '''October 3, 2008:''' branches/release closed for routine code changes and fixes. Still open for serious problem fixes and docs changes. … … 23 23 Release milestones 24 24 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.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 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 27 * Four weeks before release: branches/release closed for routine code changes and fixes. Still open for serious problem fixes and docs changes.