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.
Difference between revisions of "WTP Requirements Main"
(→Documentation) |
(→Documentation) |
||
Line 107: | Line 107: | ||
|- | |- | ||
! Server Runtime (JST and WST) | ! Server Runtime (JST and WST) | ||
− | ! [[Image: | + | ! [[Image:Checkmark.gif]] |
− | ! | + | ! AV |
|- | |- | ||
! Web Projects (JST and WST) | ! Web Projects (JST and WST) |
Revision as of 14:40, 26 July 2007
This is the landing page for information on WTP 3.0 Requirements
Contents
Process
- PMC will identify and propose the main themes for the release. This will include the themes defined by the Eclipse Requirement Council
- PMC will initiate and gather requirements from the WTP community of users, adopters and developers
- Bugzilla will be used to capture the requirements. Use the keyword, plan, to tag the enhancement request. See JDT Plan item
- Component Leads will triage the requirements and update the requirements document with a set of high-level items. Each item should have an entry in Bugzilla.
- We will use the wtp-dev mailing list and the newsgroups initially for all communication [TBD]
- PMC will conduct periodic review meetings to discuss and finalize the initial set of requirements.
- PMC will iterate through this process during the first few milestones to arrive at the final requirements document.
TimeLine
Meetings
Documentation
- WTP 3.0 Requirements documentation
- Status of the First draft by component
Completed = In Progress = Not Started =