DTP 1.9.1 Schedule and Rampdown Policy

← Back to DTP Main Page

Purpose

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

Schedule

DTP is on the Indigo SR1 release train as a +1 project. Those dates are [here].

• 1.9.1RC1 - 8/16/11
• 1.9.1RC2 - 8/30/11
• 1.9.1RC3 - 9/6/11
• 1.9.1RC4 - 9/13/11
• 1.9.1 Release - 9/20/11

Things to Keep in Mind

• 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 re-spin and retest.
• During the test/fix phase for the RC, 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.
• 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 re-spin the build, taking the re-spun build and pushing it to the update site.
• DTP builds will take place at 5am (Shanghai time).
• In general, builds occur Mon - Fri at 5am 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, 8/12/11, and continuing through Tuesday, 9/13/11, the latest available DTP 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 build 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). The I-builds occur on the Friday before the +1 RC date.

• RC1
  • After this build, we will be in a Test and Fix phase and only delivering critical fixes
  • We will continue to do RC2 nightly builds during this period
  • If a RC1 re-spin is required, it will be requested on an as-needed basis
  • All commits must be approved by a team lead
  • After release, the DTP will again be open for code delivery

• RC2
  • After this build, we will be in a Test and Fix phase and only delivering critical fixes
  • We will continue to do RC3 nightly builds during this period
  • If a RC2 re-spin is required, it will be requested on an as-needed basis
  • All commits must be approved by a team lead
  • After release, DTP will again be open for code delivery

• RC3
  • After this build, we will be in a Test and Fix phase only and delivering critical, showstopper bug fixes as necessary
  • There will be no nightly or integration builds during this period
  • If a build is required, it will be requested on an as-needed basis and any re-spin will be considered our RC4 candidate. If no build is required, the final RC3 candidate will become our RC4 candidate
  • Committers must annotate bugs proposed for inclusion in the release 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
  • Three 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)

• Release