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.
WTP 3.6.x Maintenance
Contents
WTP 3.6.x Maintenance Plan
Overview
- WTP 3.6.1 is for the first Luna simultaneous maintenance offering, delivered on the fourth Friday of September, 2014(9/26)
- WTP 3.6.2 is for the second Luna simultaneous maintenance offering, delivered on the fourth Friday of February, 2015(2/27)
For severe issues that require an immediate patch, see WTP Patches.
For overall Luna Maintenance dates, see Luna#SR1 and Luna#SR2.
Schedule
Typically, M-builds are declared every other week.
3.6.1 schedule
- 7/24 M (continuous) builds started
- Project lead review and approval until August 15
- 8/14 Declared M-build(RC1)
- PMC +1 review: August 16 - August 29
- 8/28 Declared M-build (RC2)
- PMC +2 review: August 30 - September 5
- 9/4 Declared M-build (RC3) <== final build, unless blockers found
- PMC +3 review: September 6 - 27(GA)
- 9/12 Declared M-build (RC4) <== final build, if needed
- September 12 - September 26 is "quiet" to allow in depth testing with no changes
- 9/26 Official Release
- 7/24 M (continuous) builds started
3.6.2 schedule
- 10/9 M (continuous) builds started
- Project lead review and approval until January 15
- 1/16 Declared M-build(RC1)
- PMC +1 review: January 16 - January 29
- 1/30 Declared M-build (RC2)
- PMC +2 review: January 31 - February 6
- 2/6 Declared M-build (RC3) <== final build, unless blockers found
- PMC +3 review: February 6 - 27(GA)
- 2/13 Declared M-build (RC4) <== final build, if needed
- February 13 - February 27 is "quiet" to allow in depth testing with no changes
- 2/27 Official Release
- 10/9 M (continuous) builds started
Scope
All WTP 3.6.x releases are service releases for critical defects, regressions, and adopter issues only. Specifically, there should be:
- No UI changes (that would effect documentation, tutorials, etc.)
- No NL changes (that would invalidate translations)
- No API changes, or changes affecting known adopter usage.
- No new function or features (especially those that would require an increment in minor version field).
Exceptions to the above are sometimes required, but they require WTP PMC approval.
In general, we will avoid changing the interface or behavior of any public method even if non-API.
All bundle versions must be updated (with an increment in the service level field) when the first change is made to for a service release. Similar for any feature (directly or indirectly) that includes the bundle. If a bundle (or feature) does not change, it's version should not change.
Bug Approval
All bugs must be approved by the project lead or their delegate using the bugzilla review flag. Project leads should send a note to wtp-releng to notify everyone of their choice or change in delegate(s).
After the first maintenance release candidate, all bugs must also be approved by the normal PMC Approval Process.