WTP 3.0.x Maintenance Schedule

From Eclipsepedia

Revision as of 11:55, 25 September 2008 by Hjzhang.ca.ibm.com (Talk | contribs)

Jump to: navigation, search

Contents

WTP 3.0.x Maintenance Schedule

WTP 3.0.1 is the first WTP Ganymede maintenance offering, delivered in mid August.

WTP 3.0.2 is the coordinated Eclipse Ganymede SR1 maintenance offering. The WTP 3.0.2 deliverable will line up with all other Ganymede maintenance deliverables.

WTP 3.0.3 is the coordinated Eclipse Ganymede SR2 maintenance offering. The WTP 3.0.3 deliverable will line up with all other Ganymede maintenance deliverables.

For severe issues that require an immediate patch, see WTP Patches.

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 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 final build
Aug 22 - 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 17 - RC3 & final build (updated)
Sept 23 - 3.0.2 GA (updated)

3.0.3 schedule:

10/03 M build
10/17 M build
10/24 RC1 (PMC review starts after RC1, initially one vote)
10/31 RC2 (after RC2, two PMC votes)
11/7 RC3 (after RC3, three PMC votes)
11/14 3.0.3 Release


3.0.4 schedule:

Jan 9 - M build
Jan 23 - M build
Jan 30 - RC1
All changes after Jan 30 require PMC approval (1 vote)
(Official Ganymede RC1 date is Feb 4, we are declaring early)
Feb 6 - RC2
All changes after Feb 6 require PMC approval (2 votes)
(Official Ganymede RC2 date is Feb 11, we are declaring early)
Feb 13 - final build
Feb 18 - 3.0.3 GA

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.


Back to Web Tools Wiki Home