Skip to main content

Notice: This Wiki is now read only and edits are no longer 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.1 Rampdown Policy"

(New page: ← Back to DTP Main Page ==Status== Note that this document will be updated as necessary during the DTP 1.5.1 release. ==Purpose== This document defi...)
 
Line 7: Line 7:
 
This document defines a set of ''rampdown cycles'' for DTP 1.5.1. The goal is to ensure that DTP stability and completeness converges on the 1.5.1 release dates, while allowing mechanisms for changes as necessary.  
 
This document defines a set of ''rampdown cycles'' for DTP 1.5.1. The goal is to ensure that DTP stability and completeness converges on the 1.5.1 release dates, while allowing mechanisms for changes as necessary.  
  
==Rampdown Cycle Phases==
+
==Testing & Fix Pass==
 
+
===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.
 
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.

Revision as of 11:42, 17 July 2007

Back to DTP Main Page

Status

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

Purpose

This document defines a set of rampdown cycles for DTP 1.5.1. The goal is to ensure that DTP stability and completeness converges on the 1.5.1 release dates, while allowing mechanisms for changes as necessary.

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: Builds and promotion decisions occur on the days noted, at 10EST.

  • September 12 (Wednesday): DTP 1.5.1 Release Candidate Build
  • September 12 (Wednesday) through September 25 (Tuesday): Testing & Fix Pass
    • Committers must annotate bugs proposed for inclusion in 1.5.1 with risks and nature of fix
    • Committers must petition DTP PMC using BZ for inclusion of specific bugs
    • Two positive PMC votes allows modifications to fix a specific bug to be delivered
  • September 26 (Wednesday): Last possible DTP 1.5.1 Build
  • September 28 (Friday): DTP 1.5.1 Release

Back to the top