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

WTP 2.0 Ramp down Plan for Europa

Revision as of 03:14, 4 February 2007 by Unnamed Poltroon (Talk) (added more descriptions)

Ramp down for Europa

For reference, see the Europa Simultaneous Release, in particular the Milestones and Release Candidates

From M6 to RC1 on May 18th, we expect each component lead (or delegate) to review and verify their teams' bugs.

After the first RC is produced, other RCs will be produced, if needed, every week.

After the first RC is produced, the time for general improvements is long past. The following describes the types of bugs that would be appropriate:

    • A regression
    • A P1 or P2 bug, one that is blocking or critical, and some cases of major severities.
    • And, besides the above, there should be a simple, safe, well understood fix that is well isolated from effecting other components, that has been well reviewed and well tested.
    • As each week passes, the criteria for weighing the benefit-to-risk ratio criteria gets higher and higher, and as such requires a larger number of PMC members to review.
      • May 18th, RC 1 produced
      After the 18th, besides the normal component team review, at least 1 PMC member must also review and vote +1 after reviewing the bug for appropriateness and risk.
      • May 25
      • June 1
      After June 1, besides the normal component team review, at least 2 PMC members must also review and vote +1 after reviewing the bug for appropriateness and risk.
      • June 8
      • June 15
      After the 15th, besides the normal component team review, at least 3 PMC member must also review and vote +1 after reviewing the bug for appropriateness and risk.
      • June 22
      Do zip, update, site preparations
      • June 29
      Release

Back to the top