Difference between revisions of "WTP 3.1 Project Plan"

From Eclipsepedia

Jump to: navigation, search
Line 4: Line 4:
 
The Eclipse Board has mandated that all top-level projects should keep their project plan in a standard format. See, [[Development_Resources/Project_Plan]] for details. The following process is to help automate as much of the plan as possible.
 
The Eclipse Board has mandated that all top-level projects should keep their project plan in a standard format. See, [[Development_Resources/Project_Plan]] for details. The following process is to help automate as much of the plan as possible.
 
* We will use Bugzilla to track the features. Use the ''''plan'''' keyword to submit feature requests for this release.
 
* We will use Bugzilla to track the features. Use the ''''plan'''' keyword to submit feature requests for this release.
* Component leads will triage these requests. A feature request will have the following stages in a release:
+
* Project leads will triage these requests. A feature request will have the following stages in a release:
 
{| border="1"
 
{| border="1"
 
|Proposed
 
|Proposed
|These are features that the Component Lead has triaged for the release. These are items that are either being investigated or items that the project would like to explore but are not yet Committed. Most of the features should start as proposed items. After a review and some amount of detailed planning, their status will either become committed or deferred.<br>'''The Component Lead will set the ''Target Milestone'' field of the bug to ''3.1'''''.<br>
+
|These are features that the Project Lead has triaged for the release. These are items that are either being investigated or items that the project would like to explore but are not yet Committed. Most of the features should start as proposed items. After a review and some amount of detailed planning, their status will either become committed or deferred.<br>'''The Project Lead will set the ''Target Milestone'' field of the bug to ''3.1'''''.<br>
 
|-
 
|-
 
|Committed
 
|Committed
|These are features that project team is definitely going to address in the release. Resources and some amount of detailed plans have been identified for such items. <br>'''The Component Lead will set the ''Target Milestone'' field of the bug to the specific milestones in which it will be available.'''<br>
+
|These are features that project team is definitely going to address in the release. Resources and some amount of detailed plans have been identified for such items. <br>'''The Project Lead will set the ''Target Milestone'' field of the bug to the specific milestones in which it will be available.'''<br>
 
|-
 
|-
 
|Deferred
 
|Deferred
|These are valid features that started in a '''Proposed''' state but will not be addressed in this release. Each such item will have a brief note explaining the cause for the deferral. <br>'''The Component Lead will set the ''Target Milestone'' field of the bug to ''Future'''''
+
|These are valid features that started in a '''Proposed''' state but will not be addressed in this release. Each such item will have a brief note explaining the cause for the deferral. <br>'''The Project Lead will set the ''Target Milestone'' field of the bug to ''Future'''''
 
|}
 
|}
* The PMC and the Component Leads will identify ''Themees'' for this release. '''If applicable''', feature requests can be linked to a theme. The mechanism for defining a theme and linking a  feature request to a theme is to be determined.
+
* The PMC and the Project Leads will identify ''Themees'' for this release. '''If applicable''', feature requests can be linked to a theme. The mechanism for defining a theme and linking a  feature request to a theme is to be determined.
 +
 
 +
== TimeLine ==
 +
{| border="3"
 +
|+ Planning Roadmap
 +
! Due Date!! Task Description!! Owner!! Status
 +
|-
 +
!
 +
|
 +
|
 +
|-
 +
| July 24, 2008
 +
| First iteration of themes and features planned for the release
 +
| PMC and Project Leads
 +
|
 +
|-
 +
| July 31, 2008
 +
| Publish draft plan in the standard format
 +
| PMC
 +
|
 +
|-
 +
| August 21, 2008
 +
| Second iteration of the project plan
 +
| WTP Project Leads
 +
|
 +
|-
 +
| September 04, 2008
 +
| PMC Review and Publish the initial plan document
 +
| PMC
 +
|
 +
|-
 +
|
 +
| Update plan to reflect committed tasks for milestone
 +
| WTP Project Leads
 +
|
 +
|-
 +
|-
 +
| Initial Milestones
 +
| Iterate until the feature freeze milestone
 +
|PMC
 +
|
 +
|}
 +
 
 +
Task completed = [[Image:Checkmark.gif]]

Revision as of 20:44, 9 July 2008

This is the home page for information on the planning for the Web Tools Platform (WTP) Project 3.1 release.

Planning Process

The Eclipse Board has mandated that all top-level projects should keep their project plan in a standard format. See, Development_Resources/Project_Plan for details. The following process is to help automate as much of the plan as possible.

  • We will use Bugzilla to track the features. Use the 'plan' keyword to submit feature requests for this release.
  • Project leads will triage these requests. A feature request will have the following stages in a release:
Proposed These are features that the Project Lead has triaged for the release. These are items that are either being investigated or items that the project would like to explore but are not yet Committed. Most of the features should start as proposed items. After a review and some amount of detailed planning, their status will either become committed or deferred.
The Project Lead will set the Target Milestone field of the bug to 3.1.
Committed These are features that project team is definitely going to address in the release. Resources and some amount of detailed plans have been identified for such items.
The Project Lead will set the Target Milestone field of the bug to the specific milestones in which it will be available.
Deferred These are valid features that started in a Proposed state but will not be addressed in this release. Each such item will have a brief note explaining the cause for the deferral.
The Project Lead will set the Target Milestone field of the bug to Future
  • The PMC and the Project Leads will identify Themees for this release. If applicable, feature requests can be linked to a theme. The mechanism for defining a theme and linking a feature request to a theme is to be determined.

TimeLine

Planning Roadmap
Due Date Task Description Owner Status
July 24, 2008 First iteration of themes and features planned for the release PMC and Project Leads
July 31, 2008 Publish draft plan in the standard format PMC
August 21, 2008 Second iteration of the project plan WTP Project Leads
September 04, 2008 PMC Review and Publish the initial plan document PMC
Update plan to reflect committed tasks for milestone WTP Project Leads
Initial Milestones Iterate until the feature freeze milestone PMC

Task completed = Checkmark.gif