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 "WTP 3.0.x Maintenance Schedule"
m (→WTP 3.0.1) |
m (→WTP 3.0.1 & 3.0.2) |
||
Line 1: | Line 1: | ||
− | = WTP 3.0. | + | = WTP 3.0.x Maintenance = |
== DRAFT == | == DRAFT == | ||
Line 5: | Line 5: | ||
WTP 3.0.1 is the first WTP Ganymede maintenance offering, delivered in mid August. | WTP 3.0.1 is the first WTP Ganymede maintenance offering, delivered in mid August. | ||
− | WTP 3.0.2 is the coordinated fall Eclipse Ganymede maintenance offering. The WTP 3.0.2 deliverable will line up with all other Ganymede deliverables. | + | WTP 3.0.2 is the coordinated fall Eclipse Ganymede maintenance offering. The WTP 3.0.2 deliverable will line up with all other Ganymede maintenance deliverables. |
+ | WTP 3.0.3 (not in plan yet) is the coordinated spring Eclipse Ganymede maintenance offering. The WTP 3.0.3 deliverable will line up with all other Ganymede maintenance deliverables. | ||
== Schedule Details == | == Schedule Details == | ||
− | + | M-builds are declared weekly. Only teams with significant change in a given week (either released, affected, or accumulated) need to perform a full smoke test, and other teams can decide on the appropriate level of testing. | |
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
3.0.1 schedule: | 3.0.1 schedule: | ||
:July 4 - M build | :July 4 - M build | ||
+ | :July 11 - M build | ||
:July 18 - M build | :July 18 - M build | ||
:July 25 - RC1 | :July 25 - RC1 | ||
Line 34: | Line 27: | ||
3.0.2 schedule: | 3.0.2 schedule: | ||
− | :Aug 22 - | + | :Aug 22 - M build |
:Aug 29 - M build | :Aug 29 - M build | ||
− | :Sept 5 - | + | :Sept 5 - RC1 |
::All changes after Sept 5 require PMC approval (1 vote) | ::All changes after Sept 5 require PMC approval (1 vote) | ||
− | :Sept 12 - | + | :Sept 12 - RC2 |
::All changes after Sept 12 require PMC approval (2 votes) | ::All changes after Sept 12 require PMC approval (2 votes) | ||
− | :Sept 19 - | + | :Sept 19 - RC3 & final build |
:Sept 25 - 3.0.2 GA | :Sept 25 - 3.0.2 GA | ||
+ | |||
+ | 3.0.3 schedule: | ||
+ | :TBD | ||
== Scope == | == Scope == | ||
Line 53: | Line 49: | ||
In general, we will avoid changing the interface or behaviour of any public method as per the WTP API Policy. | In general, we will avoid changing the interface or behaviour of any public method as per the WTP API Policy. | ||
+ | |||
+ | All bundle versions must be updated (an increment in the service level) when the first change is made to it in a service release. | ||
== Bug Approval == | == Bug Approval == | ||
− | All bugs must be approved by the project lead. Starting | + | All bugs must be approved by the project lead or 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). |
+ | |||
+ | Starting after RC1, all bugs must also be approved by the normal [[WTP_PMC_Defect_Review | PMC Approval Process]]. | ||
<br> | <br> | ||
[[Web_Tools_Project | Back to Web Tools Wiki Home]] | [[Web_Tools_Project | Back to Web Tools Wiki Home]] | ||
[[Category:Eclipse Web Tools Platform Project]] | [[Category:Eclipse Web Tools Platform Project]] |
Revision as of 11:56, 17 June 2008
WTP 3.0.x Maintenance
DRAFT
WTP 3.0.1 is the first WTP Ganymede maintenance offering, delivered in mid August.
WTP 3.0.2 is the coordinated fall Eclipse Ganymede maintenance offering. The WTP 3.0.2 deliverable will line up with all other Ganymede maintenance deliverables.
WTP 3.0.3 (not in plan yet) is the coordinated spring Eclipse Ganymede maintenance offering. The WTP 3.0.3 deliverable will line up with all other Ganymede maintenance deliverables.
Schedule Details
M-builds are declared weekly. Only teams with significant change in a given week (either released, affected, or accumulated) need to perform a full smoke test, and other teams can decide on the appropriate level of testing.
3.0.1 schedule:
- July 4 - M build
- July 11 - M build
- July 18 - M build
- July 25 - RC1
- All changes after July 25 require PMC approval (1 vote)
- Aug 1 - RC2
- All changes after Aug 1 require PMC approval (2 votes)
- Aug 8 - RC3 & final build
- Aug 15 - 3.0.1 GA
3.0.2 schedule:
- Aug 22 - M build
- Aug 29 - M build
- Sept 5 - RC1
- All changes after Sept 5 require PMC approval (1 vote)
- Sept 12 - RC2
- All changes after Sept 12 require PMC approval (2 votes)
- Sept 19 - RC3 & final build
- Sept 25 - 3.0.2 GA
3.0.3 schedule:
- TBD
Scope
All WTP 3.0.x releases are service releases for critical defects, regressions, and adopter issues only. Specifically, there should be:
- No UI changes
- No NL (translation) changes
- No API changes, or changes affecting adopter usage scans
All exceptions require PMC approval.
In general, we will avoid changing the interface or behaviour of any public method as per the WTP API Policy.
All bundle versions must be updated (an increment in the service level) when the first change is made to it in a service release.
Bug Approval
All bugs must be approved by the project lead or 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).
Starting after RC1, all bugs must also be approved by the normal PMC Approval Process.