Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: for the plan.

Jump to: navigation, search

WTP 3.4.x Maintenance

WTP 3.4.x Maintenance Plan


WTP 3.4.1 is for the first Juno simultaneous maintenance offering, delivered on the fourth Friday of September, 2012

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


Typically, M-builds are declared weekly.

3.4.1 schedule

6/16 Map files branched, M (continuous) builds started
Project lead review and approval until July 1
7/1 Declared M-build
PMC 1 review: July 2 - July 8
7/8 Declared M-build
PMC 2 review: July 9 - July 15
7/15 Declared M-build <== final build, unless blockers found
PMC 3 review: July 16 - July 22
7/22 Declared M-build <== final build, if needed
July 23 - July 30 is "quiet week" to allow in depth testing with no changes
7/30 Official Release


All WTP 3.4.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.

Back to the top