Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
WTP 3.2 Project Plan
WTP 3.2 Release Outline
The committers of WTP would like to have an off-cycle release, roughly end-of-year. This document is an outline to get the discussions more focused. As we progress, the Project Leads will do their detailed planning, and we will iterate.
Goals and Themes
Note: some of the items below depend on schedules of final specifications, and are subject to change.
- JPA 2.0 Support
- JSF 2.0 Support
- Java EE 6 Toleration or Basic Support
- JavaScript improvements
Assumptions
The release will be a formal release, following all the familiar processes as if it were a simultaneous release (in addition to those formal ones required by the Eclipse Foundation, such as a Release Review).
WTP 3.2 will be on Galileo Stream (Eclipse 3.5), and, technically, will be released for Galileo SR1.
We are assuming we will not "move up" to Eclipse 3.6 stream until January, 2010.
To minimize work in multiple streams, some components (and perhaps even whole sub-projects) may stay strictly as "service releases" and stay as close to Galileo Service stream as possible.
Milestones
- 7/6: Official Start date. (though some teams may begin work earlier, in their own side-streams).
- 8/7: Milestone 1
- 9/18: Milestone 2 <ensure that M2 "goes with" SR1>
- 9/25 Galileo SR1
- 10/30 Milestone 3 (API, Functional Freeze, shutdown phase begins)
- 12/18 Release of WTP 3.2
- 2/26 Galileo SR2
- 3/15 WTP 3.2.1 Service Release
- 6/29/10 WTP 3.3