Last revised:
Please send comments about this planning process to the tptp-pmc@eclipse.org
This document lays out the process and associated timeline for creating the
development plan for the TPTP 4.5 release. It details various steps for
soliciting and integrating input from the community, contributors and
committers in selecting the feature and
The TPTP 4.5 release is targeted for general availability in June, 2008 and development is expected to start in early October. It is likely to have five development iterations prior to a GA-production build and final candidate test cycle. The first iteration will be used mostly for fixing defects and reducing backlog, as well as completion of test automation activities. A number of new capabilities and technologies are under development. Here is short (and necessarily incomplete) list of priorities:
TPTP project welcomes input from the community on new features and enhancements to existing features. The preferred method for providing such input is by submitting enhancement requests in Bugzilla entries by August 17, 2007 (if a similar item does not exist) and then by voting for existing enhancement requests. The voting deadline is August 24, 2007. Your input will help project leads and committers to prioritize enhancements and defects fixes for inclusion in TPTP 4.5.
Note: Each Bugzilla user is allowed a maximum of 10 votes with no more than 3 votes per bug entry.
Contributors (through their RG/PG representatives) are requested to provide
information on availability of resources for 4.5 release cycle and propose via the
tptp-pmc@eclipse.org
Committers, project leads, and
Project Leads will communicate to lead committers preliminary guidance on resource availability for each component.
Lead Committers assimilate Community, Contributor, Architecture, Themes & Priorities inputs, and component maintenance needs (e.g., defect backlog age/size) to produce a prioritized list of candidate requirements (roughly balanced partitioning of P1/P2/P3 priorities).
Project Leads scrutinize Lead Committer proposals to ensure appropriate consideration of Community, Contributor, Architecture, and Themes & Priorities inputs, and balance between enhancements and maintenance. Project Leads will produce a consolidated project-wide prioritized candidate requirements.
Component Leads should drive analysis of candidate requirements, preparation of description documents, and review by AG. The document should include description of user visible functionality, architectural issues that span other components/projects, high-level implementation plan and effort estimates.
Project Leads will consolidate component level draft plans into project-wide
draft plan.
The draft plan document will be published on TPTP website and announced to community via tptp-news, tptp-pmc, and the tptp newsgroup for review and feedback. This is an opportunity for gaining community acceptance as well as an opportunity for the community to commit additional contributions to address requirements deferred due to resource gaps.
Project leaders will drive analysis of the feedback and necessary changes to
the draft plan.
|
Release Milestones |
|||
|
Milestone |
Start
Date |
End
Date |
Description |
|
Iteration 3 |
|
|
Defect
Fixing + Unit Tests and Test Automation for |
|
Iteration
4 |
Thurs,
15-Nov-07 |
Fri,
4-Jan-08 |
Feature
Development + additional defect fixing |
|
Iteration
5 |
Mon, 7-Jan-08 |
Fri,
15-Feb-08 |
Feature
Development + additional defect fixing |
|
Iteration
6 |
Mon,
18-Feb-08 |
Fri,
04-Apr-08 |
Additional
defect fixing + |
|
Iteration
7 |
Mon,
07-Apr-08 |
Fri,
02-May-08 |
Critical
and blocking defects |
|
Iteration
8 |
Mon,
05-May-08 |
Fri,
06-June-08 |
Shutdown;
Marching to 4.5 GA |
Plan items targeted for this release represent the addition of new features or areas where existing features will be significantly reworked or enhanced. To see a comprehensive list of enhancements submitted for TPTP project, click the link below. Please vote for enhancements that you would like to see in this release.
Quality improvement is a high priority for this release and will receive
increased attention and resource allocation. This will include fixing
outstanding defects reported in the Bugzilla, creation of additional unit level
tests for Public