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.
Web Tools Platform Release 3.0 Requirements
Note: This is a draft of the requirements document and is expected to change.
Last revised: July 15, 2007
Please send your feedback to wtp-dev@eclipse.org
Introduction
This document captures the requirements for the Web Tools Platform Project Release 3.0. The inputs for this requirement will be from the WTP community of Users, Adopters and Developers and the Eclipse Requirements Council. The document will be maintained by the WTP PMC members and the WTP Component leads.
Release Themes
Themes and their priorities communicate the main objectives and their importance to the project. The following themes are derived from those defined by the Eclipse Requirement council for the Eclipse Ganymede release and from the WTP 2.0 release themes. These will be prioritized based on the community feedback. New themes could be synthesized from the community requirements.
Theme Categorization
(Note: The following definition is provided by the Eclipse Requirements Council
Eclipse themes are described in one of four categories.
- Active themes are those that are ongoing and changing. From time to time, some Active themes will become Persistent and Pervasive.
- Persistent and Pervaisve themes are not time or release specific. Persistent and Pervasive themes are not only a signal of importance, but permanence.
- Deferred Themes are not an indication of priority, but are an indication that there are technical or resource inhibitors preventing them from becoming an Ative Theme. Deferred themes are a signal to the ecosystem that help is needed.
- Pending Themes are new and interesting themes that have not yet been properly explored and discussed to become an Active theme.