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.
Difference between revisions of "DTP Europa Build Schedule"
Line 4: | Line 4: | ||
==Introduction== | ==Introduction== | ||
+ | DTP 1.5 is part of the Europa release. As such, our milestones, release candidates, and final release date are determined by Europa. DTP is a "+1 dependency" on the Eclipse platform, and the dates of specific milestones can be found here, Milestones and Release Candidates section. Within these milestones and release candidates, DTP will have regular "integration builds" (or "I-builds") so that adopters can check progress toward eventual milestones. As discussed in the [[DTP_1.5_Project_Plan | DTP 1.5 Project Plan]], DTP will strive to have an I-build as soon as possible after platform milestone and release candidate builds. The purpose of this page is to supplement the project plan with further definition of terms and dates. | ||
+ | |||
+ | ==Definition of Terms== | ||
+ | Following general Eclipse usage, DTP 1.5 will have the following types of builds: | ||
+ | |||
+ | *Nightly Build (N-build): Created from CVS head and posted with minimal testing. Primarily designed for use by committers and adopters requiring certain bug fixes or enhancements as early as possible. | ||
+ | *Integration Build (I-build): A nightly build that is smoke tested for major functionality and found to be in at least reasonable working order. | ||
+ | *Milestone (M-build): An I-build that has been substantially tested and functioning correctly in all major aspects. | ||
+ | *Release Candidate (RC): Similar to a M-build, but with the expectation that remaining bugs will be fixed in a ramp-down (endgame) mode. | ||
+ | |||
+ | ==DTP 1.5 I-build Dates== | ||
+ | The following is the projected I-build dates for DTP 1.5. Note that these dates may be adjusted going forward as experience demands, and that hitting each of these dates is a complex function involving many interdependent tasks, so no absolute guarantee can be offered in advance. |
Revision as of 16:59, 8 February 2007
Document Status
2/8/07: This is a draft document. It has not been reviewed and approved by the DTP PMC, so it should be taken only as one possible option.
Introduction
DTP 1.5 is part of the Europa release. As such, our milestones, release candidates, and final release date are determined by Europa. DTP is a "+1 dependency" on the Eclipse platform, and the dates of specific milestones can be found here, Milestones and Release Candidates section. Within these milestones and release candidates, DTP will have regular "integration builds" (or "I-builds") so that adopters can check progress toward eventual milestones. As discussed in the DTP 1.5 Project Plan, DTP will strive to have an I-build as soon as possible after platform milestone and release candidate builds. The purpose of this page is to supplement the project plan with further definition of terms and dates.
Definition of Terms
Following general Eclipse usage, DTP 1.5 will have the following types of builds:
- Nightly Build (N-build): Created from CVS head and posted with minimal testing. Primarily designed for use by committers and adopters requiring certain bug fixes or enhancements as early as possible.
- Integration Build (I-build): A nightly build that is smoke tested for major functionality and found to be in at least reasonable working order.
- Milestone (M-build): An I-build that has been substantially tested and functioning correctly in all major aspects.
- Release Candidate (RC): Similar to a M-build, but with the expectation that remaining bugs will be fixed in a ramp-down (endgame) mode.
DTP 1.5 I-build Dates
The following is the projected I-build dates for DTP 1.5. Note that these dates may be adjusted going forward as experience demands, and that hitting each of these dates is a complex function involving many interdependent tasks, so no absolute guarantee can be offered in advance.