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) |
(→Process) |
||
Line 7: | Line 7: | ||
*Bugzilla will be used to capture the requirements. Use the keyword, '''plan''', to tag the enhancement request. For example, see [https://bugs.eclipse.org/bugs/show_bug.cgi?id=154115 JDT Plan item ] | *Bugzilla will be used to capture the requirements. Use the keyword, '''plan''', to tag the enhancement request. For example, see [https://bugs.eclipse.org/bugs/show_bug.cgi?id=154115 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. | *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 | + | *We will use the wtp-dev mailing list and the newsgroups initially for all communication. |
*PMC will conduct periodic review meetings to discuss and finalize the initial set of requirements. | *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. | *PMC will iterate through this process during the first few milestones to arrive at the final requirements document. |
Revision as of 00:22, 8 August 2007
This is the landing page for information on WTP 3.0 Requirements
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. For example, 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.
- 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
Feedback
Please give your feedback using any of the following mechanisms
- Bugzilla
- Add an enhancement request
- Comment on existing enhancement requests
- Mailing-List
- WTP developer mailing list wtp-dev@eclipse.org
- ATF developer mailing list atf-dev@eclipse.org
- Dali EJB ORM developer mailing list dali-dev@eclipse.org
- JSF Tools developer mailing list wtp-jsf-dev@eclipse.org
- Meetings
- WTP will host Requirements review calls where you can get clarification on existing requirements from the project leads and the WTP PMC memebers.
Meetings
- WTP 3.0 Requirements review call
- Date: 14th August, 2007
- Time: 11.00 AM PST
- Duration : 1 hour
- Dial-in numbers
- Toll Free: 877-421-0030
- Toll (USA): 770-615-1247
- Participant Passcode: 800388
- Toll Free: 877-421-0030
Documentation
- WTP 3.0 Requirements documentation
- Status of the First draft by component team
Completed = In Progress = Not Started =