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.
Difference between revisions of "WTP Requirements Main"
(→TimeLine) |
(→TimeLine) |
||
Line 24: | Line 24: | ||
| Publish the WTP 3.0 Requirements process and schedule (this document) to the WTP community | | Publish the WTP 3.0 Requirements process and schedule (this document) to the WTP community | ||
| PMC | | PMC | ||
− | |[[Image:Checkmark.gif], July 3rd, 2007 | + | |[[Image:Checkmark.gif]], July 3rd, 2007 |
|- | |- | ||
| July 17, 2007 | | July 17, 2007 | ||
Line 62: | Line 62: | ||
|} | |} | ||
− | Task completed = [[Image:Checkmark.gif] | + | Task completed = [[Image:Checkmark.gif]] |
==Meetings== | ==Meetings== |
Revision as of 17:26, 3 July 2007
- Work-in-progress. Please do not edit
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
- 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.