DTP 1.8 Schedule and Rampdown Policy

From Eclipsepedia

Jump to: navigation, search

Back to DTP Main Page

Contents

Status

  • 6/11/09 - Draft, to be reviewed by PMC
  • 11/23/09 - added section about temporary Helios branch

Purpose

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

Schedule

  • 1.8M1 - August 7, 2009 (publicly available 8/21/09)
  • 1.8M2 - September 18, 2009 (publicly available 10/2/09)
  • 1.8M3 - October 30, 2009 (publicly available 11/13/09)
  • 1.8M4 - December 11, 2009 (publicly available 12/18/09)
    • We have done a temporary branch to provide Helios builds using the 1.7.2 code.
    • To minimize changes to the existing 1.7.2 build process (which uses the HEAD branch), the plan is to create a temporary 1.8 branch for the feature projects and releng projects. This will be used for the Helios milestone built starting in M4.
    • When we are ready to branch the source plugins, we will then create a 1.7.2 branch to be used by the 1.7.2 build; and 1.8 build will switch to use the HEAD branch for feature and releng projects.
    • Xiaoying has submitted this BZ for the task: https://bugs.eclipse.org/bugs/show_bug.cgi?id=295563
  • 1.8M5 - January 29, 2010 (publicly available 2/5/10)
  • 1.8M6 - March 12, 2010 (publicly available 3/19/10) (API Freeze)
  • 1.8M7 - April 30, 2010 (publicly available 5/7/10) (Feature Freeze)
  • 1.8RC1 - May 14, 2010 (publicly available 5/17/10)
  • 1.8RC2 - May 21, 2010 (publicly available 5/24/10)
  • 1.8RC3 - May 28, 2010 (publicly available 5/31/10)
  • 1.8RC4 - June 4, 2010 (publicly available 6/11/10)
  • 1.8RC5 - June 14, 2010 (publicly available 6/18/10)
  • 1.8 Release - June 23, 2010
    • Helios release train as a +1 project. Those dates are [here].

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 (<date> 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

Integration Builds

Starting on Friday, <date>, and continuing through Tuesday, <date>, 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.

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.

Rampdown Cycles

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

1.8M4

  • I-Build Friday, <date> (SH)
  • Enter Test & Fix phase with Component Lead approval through Tuesday, <date> (SH)
    • We will continue to do M4 nightly builds during this period
  • Development resumes for M5 on Wednesday, <date> (SH)
  • M4 publicly available with rest of release train on Monday, <date>

1.8M5

  • I-Build Tuesday, <date> (SH)
  • Enter Test & Fix phase with Component Lead approval through Monday, <date> (SH)
    • We will continue to do M5 nightly builds during this period
  • Development resumes for M6 on Tuesday, <date>(SH)
  • M5 publicly available with rest of release train on Monday, <date>(SH)

1.8M6 (API Freeze)

  • I-Build Tuesday, <date> (SH)
  • Enter Test & Fix phase with Component Lead approval through Monday, <date> (SH)
    • We will continue to do M6 nightly builds during this period
  • Development resumes for M7 on Tuesday, <date> (SH)
  • M6 publicly available with rest of release train on Monday, <date> (SH)

1.8 M7 (Feature Freeze)

  • I-Build Friday, <date> (SH)
  • Enter Test & Fix phase with Team Lead approval through Wednesday, <date> (SH)
    • If a M7 respin is required, it will be requested on an as-needed basis
  • Development resumes for critical fixes for RC1 on Thursday, <date>
  • M7 publicly available with rest of release train on Monday, <date>

1.8RC1

  • Build Monday, <date> (SH)
  • Enter Test & Fix phase with Team Lead approval for critical fixes through Friday, <date> (SH)
    • If a RC1 respin is required, it will be requested on an as-needed basis
  • RC1 publicly available with rest of release train on Monday, <date>

1.8RC2

  • Build Monday, <date> (SH)
    • After this build, we will be in a Test and Fix phase only and delivering critical, showstopper bug fixes as necessary
  • Enter Test & Fix phase with PMC approval for critical fixes through Friday, <date> (SH)
    • There will be no nightly or integration builds during this period
    • If a RC2 respin is required, it will be requested on an as-needed basis
    • Committers must annotate bugs proposed for inclusion in 1.8 with risks and nature of fix
    • Committers must get modifications reviewed by one other committer on project
    • Committers must petition DTP PMC using BZ for inclusion of specific bugs
    • Four positive PMC votes allows modifications to fix a specific bug to be delivered (unless a PMC member is abstaining, in which case all remaining PMC members must still vote positive)
  • RC2 publicly available with rest of release train on Monday, <date>

1.8RC3

  • Build Monday, <date> (SH)
  • Enter Test & Fix phase with PMC approval for super-critical fixes through Friday, <date> (SH)
    • There will be no nightly or integration builds during this period
    • If a RC3 respin is required, it will be requested on an as-needed basis
    • Committers must annotate bugs proposed for inclusion in 1.8 with risks and nature of fix
    • Committers must get modifications reviewed by one other committer on project
    • Committers must petition DTP PMC using BZ for inclusion of specific bugs
    • Four positive PMC votes allows modifications to fix a specific bug to be delivered (unless a PMC member is abstaining, in which case all remaining PMC members must still vote positive)
  • RC3 publicly available with rest of release train on Monday, <date>

1.8RC4

  • Build Monday, <date> (SH)
  • Enter Test & Fix phase with PMC approval for super-critical fixes through Friday, <date> (SH)
    • There will be no nightly or integration builds during this period
    • If a RC4 respin is required, it will be requested on an as-needed basis
    • Committers must annotate bugs proposed for inclusion in 1.8 with risks and nature of fix
    • Committers must get modifications reviewed by one other committer on project
    • Committers must petition DTP PMC using BZ for inclusion of specific bugs
    • Four positive PMC votes allows modifications to fix a specific bug to be delivered (unless a PMC member is abstaining, in which case all remaining PMC members must still vote positive)
  • RC4 publicly available with rest of release train on Monday, <date>

1.8RC5

  • Build Monday, <date> (SH)
  • Enter Test & Fix phase with PMC approval for super-critical fixes through Friday, <date> (SH)
    • There will be no nightly or integration builds during this period
    • If a RC5 respin is required, it will be requested on an as-needed basis
    • Committers must annotate bugs proposed for inclusion in 1.8 with risks and nature of fix
    • Committers must get modifications reviewed by one other committer on project
    • Committers must petition DTP PMC using BZ for inclusion of specific bugs
    • Four positive PMC votes allows modifications to fix a specific bug to be delivered (unless a PMC member is abstaining, in which case all remaining PMC members must still vote positive)
  • RC5 publicly available with rest of release train on Monday, <date>

1.8 Release

Friday, June 23, 2010