Jump to: navigation, search

Difference between revisions of "DTP 1.5 Rampdown Policy"

Line 14: Line 14:
  
 
==Rampdown Cycles==
 
==Rampdown Cycles==
 +
 +
'''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===
 
===May 11: DTP 1.5RC0===

Revision as of 13:18, 27 February 2007

Back to DTP Main Page

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 Cycle Phases

Testing Pass

Testing & Fix Pass

Rampdown Cycles

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 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.

Additional RC Builds

Additional RC builds will be scheduled as necessary.