Jump to: navigation, search

Difference between revisions of "WTP 3.1 Project Plan"

(TimeLine)
 
(43 intermediate revisions by 7 users not shown)
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''''' (2.1 for JPT).<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 ''Themes'' for this release. '''If applicable''', feature requests can be linked to a theme. Use the '''Status Whitboard''' field in the bugzilla to associate a feature with a theme. For example, if you would like to associate a feature with the theme, '''Ease of Use''', add '''EaseOfUse''' to the Whiteboard field. Plan items that have no themes will appear in the '''Other''' category.
 +
 
 +
* Project leads should update the '''projectplanurl''' field for their subproject from the Eclipse Portal as described in the [http://wiki.eclipse.org/Development_Resources/HOWTO/Project_Meta-Data  Project Metadata wiki].
 +
 
 +
== Project Plans ==
 +
* Each subproject has a project plan in CVS at the following location
 +
** Repository Path: '''/cvsroot/org.eclipse'''
 +
** Module: '''www/webtools/standard-project-plans'''
 +
*[[Development_Resources/Project_Plan#Tools_for_Editing_your_Plan|Tools for editing the project plan]]
 +
* Project plan for a subproject can be viewed from its home page, '''Project Plan''' section. Click on the link that says, '''pending standard form'''. They are also listed here for convenience.
 +
**[http://www.eclipse.org/projects/project-plan.php?projectid=webtools.common WTP Common Tools]
 +
**[http://www.eclipse.org/projects/project-plan.php?projectid=webtools.dali Dali Java Persistence Tools] 
 +
**[http://www.eclipse.org/projects/project-plan.php?projectid=webtools.ejbtools EJB Tools] 
 +
**[http://www.eclipse.org/projects/project-plan.php?projectid=webtools.jeetools Java EE Tools] 
 +
**[http://www.eclipse.org/projects/project-plan.php?projectid=webtools.jsf JSF Tools] 
 +
**[http://www.eclipse.org/projects/project-plan.php?projectid=webtools.servertools Server Tools]
 +
**[http://www.eclipse.org/projects/project-plan.php?projectid=webtools.sourceediting Source Editing] 
 +
**[http://www.eclipse.org/projects/project-plan.php?projectid=webtools.webservices Web Services]
 +
**[http://www.eclipse.org/projects/project-plan.php?projectid=webtools.releng WTP Releng]
 +
 
 +
== Summary Bugzilla Queries ==
 +
 
 +
The following table shows all 'plan' (keyword) items for all targets and components.
 +
 
 +
[https://bugs.eclipse.org/bugs/report.cgi?x_axis_field=target_milestone&y_axis_field=component&z_axis_field=&query_format=report-table&short_desc_type=allwordssubstr&short_desc=&classification=WebTools&keywords_type=allwords&keywords=plan&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&format=table&action=wrap Plan Summary Table]
 +
 
 +
The following table shows all items targeted for WTP 3.1 that are not plan items, per se.
 +
 
 +
[https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&classification=WebTools&keywords_type=nowords&keywords=plan&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&cmdtype=doit&field0-0-0=target_milestone&type0-0-0=anywordssubstr&value0-0-0=3.1%2C+2.1 WTP 3.1 Targeted bugs]
 +
 
 +
=== Triage bugzilla for candidate items to target to 3.1 ===
 +
 
 +
As planning progresses, we will expect these types of bugs (major, or ones with many votes) to become less and less in number.
 +
 
 +
* [https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&classification=WebTools&product=Dali+JPA+Tools&product=Java+Server+Faces&product=Web+Tools&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=nowords&keywords=plan&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=votes&type0-0-0=greaterthan&value0-0-0=2&field0-1-0=target_milestone&type0-1-0=nowordssubstr&value0-1-0=2.0.1%2C+2.0.2%2C+3.0.1%2C+3.0.2%2C+3.1%2C+2.1 Most voted bugs not targeted to WTP 3.1] (~48)
 +
 
 +
* [https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&classification=WebTools&product=Dali+JPA+Tools&product=Java+Server+Faces&product=Web+Tools&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=nowords&keywords=plan&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=bug_severity&type0-0-0=anywordssubstr&value0-0-0=Blocker%2C+Critical%2C+Major&field0-1-0=target_milestone&type0-1-0=nowordssubstr&value0-1-0=1.5.5%2C+2.0.1%2C+2.0.2%2C+3.0.1%2C+3.0.2%2C+3.1%2C+2.1 Major items without a 3.1 target] (~180)
 +
 
 +
== TimeLine ==
 +
* Realligned dates to reflect schedule set by the [http://dev.eclipse.org/mhonarc/lists/eclipse.org-planning-council/msg01422.html Project Council]
 +
{| border="3"
 +
|+ Planning Roadmap
 +
! Due Date!! Task Description!! Owner!! Status
 +
|-
 +
!
 +
|
 +
|
 +
|-
 +
| August 29, 2008
 +
| First iteration of themes and features planned for the release
 +
| PMC and Project Leads
 +
|[[Image:Checkmark.gif]]
 +
|-
 +
| September 26, 2008
 +
| PMC Review and Publish draft plan in the standard format
 +
| PMC
 +
|[[Image:Checkmark.gif]]
 +
|-
 +
|-
 +
| October 24, 2008
 +
| PMC Review and Publish the plan document for the Planning Council
 +
| PMC
 +
|[[Image:Checkmark.gif]]
 +
|-
 +
|
 +
| Update plan to reflect committed tasks for milestone
 +
| WTP Project Leads
 +
|[[Image:Checkmark.gif]]
 +
|-
 +
|
 +
|}
 +
 
 +
Task completed = [[Image:Checkmark.gif]]
 +
 
 +
 
 +
 
 +
[[Category:Eclipse Web Tools Platform Project]]

Latest revision as of 16:02, 11 February 2009

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 (2.1 for JPT).
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 Themes for this release. If applicable, feature requests can be linked to a theme. Use the Status Whitboard field in the bugzilla to associate a feature with a theme. For example, if you would like to associate a feature with the theme, Ease of Use, add EaseOfUse to the Whiteboard field. Plan items that have no themes will appear in the Other category.
  • Project leads should update the projectplanurl field for their subproject from the Eclipse Portal as described in the Project Metadata wiki.

Project Plans

Summary Bugzilla Queries

The following table shows all 'plan' (keyword) items for all targets and components.

Plan Summary Table

The following table shows all items targeted for WTP 3.1 that are not plan items, per se.

WTP 3.1 Targeted bugs

Triage bugzilla for candidate items to target to 3.1

As planning progresses, we will expect these types of bugs (major, or ones with many votes) to become less and less in number.

TimeLine

Planning Roadmap
Due Date Task Description Owner Status
August 29, 2008 First iteration of themes and features planned for the release PMC and Project Leads Checkmark.gif
September 26, 2008 PMC Review and Publish draft plan in the standard format PMC Checkmark.gif
October 24, 2008 PMC Review and Publish the plan document for the Planning Council PMC Checkmark.gif
Update plan to reflect committed tasks for milestone WTP Project Leads Checkmark.gif

Task completed = Checkmark.gif