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 Ganymede Milestone Sign-off Policy"

(New page: ==Status== '''[12/7/07]:''' This document is a '''draft''' and has not been approved by the DTP PMC. ==Introduction== As both an Eclipse project and a member of coordinated releases (Calli...)
 
Line 4: Line 4:
 
As both an Eclipse project and a member of coordinated releases (Callisto, Europa, Ganymede), it is imperative that DTP milestones, release candidates, and releases are of acceptable quality.
 
As both an Eclipse project and a member of coordinated releases (Callisto, Europa, Ganymede), it is imperative that DTP milestones, release candidates, and releases are of acceptable quality.
 
==Process==
 
==Process==
 +
1. For each DTP milestone, release candidate and release date, the PMC will determine a "candidate build" date on which the associated DTP build will be taken as the testing target.
 +
2. For each DTP milestone, release candidate and release date, the PMC will determine a sign-off close date and publish it to the dtp-pmc mailing list.
 +
3. Each DTP project lead should work with their teams to test the DTP candidate build.
 +
4. By the sign-off close date, each DTP project lead will send an email to dtp-pmc expressing one of the following sign-off options:

Revision as of 13:45, 7 December 2007

Status

[12/7/07]: This document is a draft and has not been approved by the DTP PMC.

Introduction

As both an Eclipse project and a member of coordinated releases (Callisto, Europa, Ganymede), it is imperative that DTP milestones, release candidates, and releases are of acceptable quality.

Process

1. For each DTP milestone, release candidate and release date, the PMC will determine a "candidate build" date on which the associated DTP build will be taken as the testing target. 2. For each DTP milestone, release candidate and release date, the PMC will determine a sign-off close date and publish it to the dtp-pmc mailing list. 3. Each DTP project lead should work with their teams to test the DTP candidate build. 4. By the sign-off close date, each DTP project lead will send an email to dtp-pmc expressing one of the following sign-off options:

Copyright © Eclipse Foundation, Inc. All Rights Reserved.