Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "DTP 1.5 Rampdown Policy"
Line 10: | Line 10: | ||
===May 11: DTP 1.5RC0=== | ===May 11: DTP 1.5RC0=== | ||
− | *Monday, May 14, through Friday, May 18: Testing | + | *Monday, May 14, through Friday, May 18: Testing Pass |
− | *Monday, May 21, through Friday, May 25: Fix | + | *Monday, May 21, through Friday, May 25: Testing & Fix Pass. All bugs must be approved by project lead, who must post bug list to [mailto:dtp-dev@eclipse.org dtp-dev]. |
+ | |||
+ | ===May 28: DTP 1.5RC1=== | ||
+ | *Monday, May 28, through Friday, June 1: Testing Pass | ||
+ | *Monday, June 4, through Friday, June 8: Testing & Fix Pass. All bugs must approved by PMC. Committers should petition the [mailto:dtp-pmc@eclipse.org 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. |
Revision as of 13:11, 27 February 2007
Status
2/27: This document is a draft and has not been reviewed/approved by the PMC.
Purpose
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 Cycles
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 bug list to dtp-dev.
May 28: DTP 1.5RC1
- Monday, May 28, through Friday, June 1: Testing Pass
- Monday, June 4, through Friday, June 8: 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.