Difference between revisions of "DTP 1.9 Schedule and Rampdown Policy"

From Eclipsepedia

Jump to: navigation, search
(Rampdown Cycles)
m (Integration Builds)
 
Line 33: Line 33:
  
 
==Integration Builds==
 
==Integration Builds==
Starting with RC1, the latest available DTP 1.8 integration build (done each Friday, as noted above) will be tested for promotion. If no substantial defects are found, then the build will be promoted.
+
Starting with RC1, the latest available DTP 1.9 integration build (done each Friday, as noted above) will be tested for promotion. If no substantial defects are found, then the build will be promoted.
  
 
==Testing & Fix Pass==
 
==Testing & Fix Pass==

Latest revision as of 23:33, 28 September 2010

Back to DTP Main Page

Contents

[edit] Status

  • 9/21/10 - Draft started, to be reviewed by PMC

[edit] Purpose

This document defines a schedule and set of ramp-down policies for DTP 1.9 (Indigo). The goal is to ensure that DTP stability and completeness converges on the 1.9 release dates, while allowing mechanisms for changes as necessary.

[edit] Schedule

DTP is on the Indigo release train as a +1 project. These dates are based on the Indigo Simultaneous Release Plan

  • 1.9M1 - August 16, 2010 (publicly available 8/20/10)
  • 1.9M2 - September 27, 2010 (publicly available 10/1/10)
  • 1.9M3 - November 8, 2010 (publicly available 11/12/10)
  • 1.9M4 - December 13, 2010 (publicly available 12/17/10)
  • 1.9M5 - February 7, 2011 (publicly available 2/11/11)
  • 1.9M6 - March 11, 2011 (publicly available 3/18/11)
  • 1.9M7 - May 2, 2011 (publicly available 5/6/11)
  • 1.9RC1 - May 16, 2011 (publicly available 5/20/11)
  • 1.9RC2 - May 23, 2011 (publicly available 5/28/11)
  • 1.9RC3 - May 30, 2011 (publicly available 6/3/11)
  • 1.9RC4 - June 6, 2011 (publicly available 6/10/11)
  • 1.9 Release - June 22, 2011

[edit] Builds Reminder

  • Nightly builds take place from Monday to Thursday. Integration builds takes place on Friday.
  • During a test phase, there are no builds. We take the build before the test phase and test it. If we run across extreme issues, we will respin and retest.
  • During the test/fix phase for the RCs, we will do regular daily builds. Once we are in the test/fix phase, where PMC approvals are needed, we will not build nightly, but will build as needed (RC1 and beyond).
  • On Push days, we will take the Monday Shanghai build (which is our Sunday at 2pm PST) and if it's good, we will push it to the update site that Monday evening (SH Tuesday a.m.). If things are not good, we will fix the issues and respin the build, taking the respun build and pushing it to the update site.
  • DTP builds will take place at 5am (Shanghai time).
  • In general, builds occur Mon - Fri at 2pm Shanghai time, which is equivalent to Sun - Thu 2pm PST.
  • DTP committers should refrain from updating map files for +/- 30 minutes around the start of the build, to avoid version inconsistencies in the map file set.
  • See the Build Transition page for additional details about regular DTP builds

[edit] Integration Builds

Starting with RC1, the latest available DTP 1.9 integration build (done each Friday, as noted above) will be tested for promotion. If no substantial defects are found, then the build will be promoted.

[edit] Testing & Fix Pass

A period of intensive testing, including bug fixes based on the approval policies described below. Nightly builds will be produced during this period as necessary to make bug fixes available to the DTP community.

[edit] Rampdown Cycles

Note: Builds occur on the days noted, at 5am (Shanghai time).

TBD

[edit] 1.9M3

[edit] 1.9M4

[edit] 1.9M5

[edit] 1.9M6

[edit] 1.9M7

[edit] 1.9RC1

[edit] 1.9RC2

[edit] 1.9RC3

[edit] 1.9RC4