Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Difference between revisions of "DTP 1.5 Rampdown Policy"

Line 22: Line 22:
  
 
===May 11: DTP 1.5RC0===
 
===May 11: DTP 1.5RC0===
*Through Wednesday, May 9: Testing & Fix Pass: Standard DTP policies apply.
+
*''Through'' Wednesday, May 9: Testing & Fix Pass: Standard DTP policies apply.
 
*Thursday, May 10: DTP 1.5RC0 candidate build
 
*Thursday, May 10: DTP 1.5RC0 candidate build
*Thursday, May 10, until Friday, May 11: DTP 1.5RC0 candidate promotion testing
+
*Thursday, May 10, ''until'' Friday, May 11: DTP 1.5RC0 candidate promotion testing
  
 
===May 23: DTP 1.5RC1===
 
===May 23: DTP 1.5RC1===
*Friday, May 11, through Tuesday, May 15: Testing Pass
+
*Friday, May 11, ''through'' Tuesday, May 15: Testing Pass
*Wednesday, May 16, through Monday, May 21: Testing & Fix Pass. All bugs must approved by project lead.
+
*Wednesday, May 16, ''through'' Monday, May 21: Testing & Fix Pass. All bugs must approved by project lead.
 
*Tuesday, May 22: DTP 1.5RC1 candidate build
 
*Tuesday, May 22: DTP 1.5RC1 candidate build
*Tuesday, May 22, until Wednesday, May 23: DTP 1.5RC1 candidate promotion testing
+
*Tuesday, May 22, ''until'' Wednesday, May 23: DTP 1.5RC1 candidate promotion testing
  
 
===May 30: DTP 1.5RC2===
 
===May 30: DTP 1.5RC2===
  
*Wednesday, May 23, through Thursday, May 24: Testing Pass
+
*Wednesday, May 23, ''through'' Thursday, May 24: Testing Pass
*Friday, May 25, through Monday, May 28: Testing & Fix Pass. All bugs must approved by project lead who must notify the [mailto:dtp-pmc@eclipse.org dtp-pmc] mailing list.
+
*Friday, May 25, ''through'' Monday, May 28: Testing & Fix Pass. All bugs must approved by project lead who must notify the [mailto:dtp-pmc@eclipse.org dtp-pmc] mailing list.
 
*Tuesday, May 29: DTP 1.5RC2 candidate build
 
*Tuesday, May 29: DTP 1.5RC2 candidate build
*Tuesday, May 29, until Wednesday, May 30: DTP 1.5RC2 candidate promotion testing
+
*Tuesday, May 29, ''until'' Wednesday, May 30: DTP 1.5RC2 candidate promotion testing
  
 
===June 13: DTP 1.5RC3===
 
===June 13: DTP 1.5RC3===
  
*Wednesday, May 30, through Monday, June 4: Testing Pass
+
*Wednesday, May 30, ''through'' Monday, June 4: Testing Pass
*Tuesday, June 5, through Monday, June 11: 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.
+
*Tuesday, June 5, ''through'' Monday, June 11: 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.
 
*Tuesday, June 12: DTP 1.5RC3 candidate build
 
*Tuesday, June 12: DTP 1.5RC3 candidate build
*Tuesday, June 12, until Wednesday, June 13: DTP 1.5RC3 candidate promotion testing
+
*Tuesday, June 12, ''until'' Wednesday, June 13: DTP 1.5RC3 candidate promotion testing
  
 
===June 20: DTP 1.5RC4===
 
===June 20: DTP 1.5RC4===
  
*Wednesday, June 13, through Thursday, June 14: Testing Pass
+
*Wednesday, June 13, ''through'' Thursday, June 14: Testing Pass
*Friday, June 15, through Monday, June 18: 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.
+
*Friday, June 15, ''through'' Monday, June 18: 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.
 
*Tuesday, June 19: DTP 1.5RC4 candidate build
 
*Tuesday, June 19: DTP 1.5RC4 candidate build
*Tuesday, June 19, until Wednesday, June 20: DTP 1.5RC4 candidate promotion testing
+
*Tuesday, June 19, ''until'' Wednesday, June 20: DTP 1.5RC4 candidate promotion testing
  
 
===Post DTP 1.5RC4 through Europa Release===
 
===Post DTP 1.5RC4 through Europa Release===
*Wednesday, June 20 until Europa release (est. Friday, June 29): Testing Pass
+
*Wednesday, June 20 ''until'' Europa release (est. Friday, June 29): Testing Pass
  
 
===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 16:02, 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 RC0 -- 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

May 11: DTP 1.5RC0

  • Through Wednesday, May 9: Testing & Fix Pass: Standard DTP policies apply.
  • Thursday, May 10: DTP 1.5RC0 candidate build
  • Thursday, May 10, until Friday, May 11: DTP 1.5RC0 candidate promotion testing

May 23: DTP 1.5RC1

  • Friday, May 11, through Tuesday, May 15: Testing Pass
  • Wednesday, May 16, through Monday, May 21: Testing & Fix Pass. All bugs must approved by project lead.
  • Tuesday, May 22: DTP 1.5RC1 candidate build
  • Tuesday, May 22, until Wednesday, May 23: DTP 1.5RC1 candidate promotion testing

May 30: DTP 1.5RC2

  • Wednesday, May 23, through Thursday, May 24: Testing Pass
  • Friday, May 25, through Monday, May 28: Testing & Fix Pass. All bugs must approved by project lead who must notify the dtp-pmc mailing list.
  • Tuesday, May 29: DTP 1.5RC2 candidate build
  • Tuesday, May 29, until Wednesday, May 30: DTP 1.5RC2 candidate promotion testing

June 13: DTP 1.5RC3

  • Wednesday, May 30, through Monday, June 4: Testing Pass
  • Tuesday, June 5, through Monday, June 11: 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.
  • Tuesday, June 12: DTP 1.5RC3 candidate build
  • Tuesday, June 12, until Wednesday, June 13: DTP 1.5RC3 candidate promotion testing

June 20: DTP 1.5RC4

  • Wednesday, June 13, through Thursday, June 14: Testing Pass
  • Friday, June 15, through Monday, June 18: 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.
  • Tuesday, June 19: DTP 1.5RC4 candidate build
  • Tuesday, June 19, until Wednesday, June 20: DTP 1.5RC4 candidate promotion testing

Post DTP 1.5RC4 through Europa Release

  • Wednesday, June 20 until Europa release (est. Friday, June 29): Testing Pass

Additional RC Builds

Additional RC builds will be scheduled as necessary.

Back to the top