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.
Difference between revisions of "DTP Ganymede Milestone Sign-off Policy"
Line 8: | Line 8: | ||
*Each DTP project lead should work with their teams to test the DTP candidate build. | *Each DTP project lead should work with their teams to test the DTP candidate build. | ||
*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: | *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: | ||
+ | **Accepted: "In the project lead's best judgement, their project components are ready for the milestone/release candidate/release." | ||
+ | **Accepted, with reservations: "In the project lead's best judgement, their project components are ready for the milestone/release candidate/release, with the following reservations." Next, a list of Bugzilla entries specific to that project, which the project lead would ideally like to see resolved, but not enough strictly to postpone the milestone/release candidate/release completion. | ||
+ | **Declined: "In the project lead's best judgement, their project components are not ready for the milestone/release candidate/release." Next, a list of Bugzilla entries specific to that project, which the project lead believes must be resolved before milestone/release candidate/release completion. |
Revision as of 14:16, 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
- 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.
- 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.
- Each DTP project lead should work with their teams to test the DTP candidate build.
- 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:
- Accepted: "In the project lead's best judgement, their project components are ready for the milestone/release candidate/release."
- Accepted, with reservations: "In the project lead's best judgement, their project components are ready for the milestone/release candidate/release, with the following reservations." Next, a list of Bugzilla entries specific to that project, which the project lead would ideally like to see resolved, but not enough strictly to postpone the milestone/release candidate/release completion.
- Declined: "In the project lead's best judgement, their project components are not ready for the milestone/release candidate/release." Next, a list of Bugzilla entries specific to that project, which the project lead believes must be resolved before milestone/release candidate/release completion.