WTP Release 1.5.x Maintenance Plan and Policies
This document is to capture the important information for WTP 1.5.x maintenance release that will be of interest to adopters and committers.
The general PMC policy as agreed to and published on wtp-dev on 6/13/2006 (See 1.5.1 change policy).
- General expectation: 1.5 adopters should be able to take 1.5.1 and 1.5.2 without problems
- Binary compatibility is required among all point releases and 1.5
- Source compatibility is required among all point releases and 1.5
- Full project interoperability among these releases (e.g., a project created in 1.5.1 must be usable in 1.5 without changes)
- Without prior PMC approval, no new, changed, or deleted
- Extension points
- Features (including major UI changes)
- Changes to non-APIs must be announced on the wtp-dev mailing list. You are also required to run the adopter usage scanner to ensure WTP adopters are not affected by these changes. See the non-API change policy and how to run the adopter usage scanner.
- Bug fixes and performance enhancements are generally ok and do not require PMC approval until rampdown
UI and National Language Impacts
In order to avoid large differences between documentation (which may have screen shots, etc.) and large differnces with potentially translated versions of WTP, UI and PII changes should be kept to a minimum. Specifically, Only fixed where the doc or non-NL bug is less bad than the original bug. When required, we will track with a new bug, marked minor, that simply says something like "untranslated string" with details (which string, which plugin) listed in the body of the bug. That way we'll know if we are getting too many and should re-consider plans.
8/15 Deadline for "Hot bugs" to be proposed from adopters.
9/15 Release candidate
9/29 1.5.1 Release (as part of Callisto Maintenance Release)
1Q 2007 1.5.2