Jump to: navigation, search

Difference between revisions of "DTP 1.5 Rampdown Policy"

Line 3: Line 3:
  
 
Note that this document will be updated as necessary during the DTP 1.5 release.
 
Note that this document will be updated as necessary during the DTP 1.5 release.
 +
 +
'''[4/26/07]:''' The ramp down for builds RC1 -- RC4 is under review by the DTP PMC.
  
 
==Purpose==
 
==Purpose==
Line 25: Line 27:
 
*Monday, May 21, through Friday, June 1: Testing & Fix Pass. All bugs must be approved by project lead, who must post the bug list(s) to [mailto:dtp-dev@eclipse.org dtp-dev].
 
*Monday, May 21, through Friday, June 1: Testing & Fix Pass. All bugs must be approved by project lead, who must post the bug list(s) to [mailto:dtp-dev@eclipse.org dtp-dev].
  
===TBD: DTP 1.5RC1===
+
===May 23: DTP 1.5RC1===
 
*TBD: Testing Pass
 
*TBD: Testing Pass
 
*TBD: 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.
 
*TBD: 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.
 +
 +
===May 30: DTP 1.5RC2===
 +
 +
===June 13: DTP 1.5RC3===
 +
 +
===June 20: DTP 1.5RC4===
  
 
===Additional RC Builds===
 
===Additional RC Builds===
 
Additional RC builds will be scheduled as necessary.
 
Additional RC builds will be scheduled as necessary.

Revision as of 15:14, 26 April 2007

Back to DTP Main Page

Status

Note that this document will be updated as necessary during the DTP 1.5 release.

[4/26/07]: The ramp down for builds RC1 -- RC4 is under review by the DTP 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

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.

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, June 1: Testing & Fix Pass. All bugs must be approved by project lead, who must post the bug list(s) to dtp-dev.

May 23: 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.

May 30: DTP 1.5RC2

June 13: DTP 1.5RC3

June 20: DTP 1.5RC4

Additional RC Builds

Additional RC builds will be scheduled as necessary.