DTP 1.5 Rampdown Policy
2/27: This document is a draft and has not been reviewed/approved by the PMC.
Note that this document will be updated as necessary during the DTP 1.5 release.
This document defines a set of rampdown cycles for DTP 1.5. The goal is to ensure that DTP stability and completeness converges on the 1.5 release dates, while allowing mechanisms for changes as necessary. Since this document is about the rampdown, only cycles post DTP 1.5RC0 will be detailed below.
Rampdown Cycle Phases
A period of testing during which no changes are made to the DTP code line, unless approved by the PMC. Nightly builds will not be produced during this pass. In general, we ask everyone in the DTP community to test the target build as thoroughly as possible.
Testing & Fix Pass
A Testing Pass including bug fixes based on the approval policies described below. Nightly build will be produced during this period as necessary to make bug fixes available to the DTP community.
Note: In order to promote a Release Candidate (RC), we must be able to test a build near the RC date. Thus, since RC promotions are scheduled for Mondays, committers should plan to have completed work in time for the previous Thursday's build. The Thursday build will be tested and, if no stop-ship bugs are found (as determined by the project leads and PMC, including recommendations from the community), then the Thursday build will be promoted at 5EST on the following Monday.
May 11: DTP 1.5RC0
- Monday, May 14, through Friday, May 18: Testing Pass
- Monday, May 21, through Friday, May 25: Testing & Fix Pass. All bugs must be approved by project lead, who must post the bug list(s) to dtp-dev.
TBD: DTP 1.5RC1
- TBD: Testing Pass
- TBD: Testing & Fix Pass. All bugs must approved by PMC. Committers should petition the dtp-pmc mailing list for approval and any community member should do the same for bugs that they feel should be addressed in DTP 1.5.
Additional RC Builds
Additional RC builds will be scheduled as necessary.