Eclipse Test & Performance Tools Platform (TPTP) Project
Release 4.3 Planning Process

Last revised 09:00 PDT 4 May 2006

    Please send comments about this planning process to the PMC mailing list.

This document lays out the process and associated timeline for creating development plan for 4.3 release. It details various steps for soliciting and integrating input from community, contributors and committers  in selecting feature and API set to be developed. This is a working document and as such will be updated with additional information and refinement to the dates as they become available.


The TPTP 4.3 release is targeted for general availability in October, 2006 and development is expected to start in early July. It is likely to have two development iterations followed by a short iteration to produce GA build. The first iteration will be used mostly for fixing defects and reducing backlog. A number of new capabilities and technologies are underdevelopment and many of these are previewed in TPTP 4.2 release (see release plan and download pages for details). We expect that some of these efforts would mature and qualify to become part of official 4.3 release. Here is short (and necessarily incomplete) list of priorities:

Planning Process

Input from Community (May 8 - June 2):

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 (if a similar item does not exist) or by voting for an existing enhancement request. Your input will help project leads and committers to prioritize for inclusion in TPTP 4.3.

Each Bugzilla user is allowed a maximum of 10 votes with no more than 3 votes per bug entry. Deadline for submission of your votes is June 2, 2006.

Input from Contributors (May 8 - June 2):

Contributors (through their RG/PG representatives) are requested to provide information on availability of resources for 4.3 release cycle and propose via tptp-pmc mailing list a prioritized list of Bugzilla enhancements/defects roughly equal to the size of their resource commitments.

Input from Committers/PMC (May 8 - June 2):

Committers, project leads, and PMC can propose enhancements or improvements that are aligned with overall project goals and roadmap. For example, AG representative proposes via tptp-pmc mailing list a list of Bugzilla enhancements and defects appropriate for advancing the project in alignment with the TPTP and Eclipse Architecture Plans.

Preparation of Draft Plan (May 29 - June 16)

Project Leads will communicate to lead committers preliminary guidance on resource availability for each component. (June 5)

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). (June 7)

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. (June 9)

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. (June 5 - June 15)

PMC/RG reviews proposed prioritization of requirements relative to community votes, contributor requests, themes & priorities, and project advancement; Outcome is PMC/RG approved candidate list of requirements. (June 12-15)

Project Leads will consolidate component level draft plans into project-wide draft plan. PMC/PG will review the draft plan proposed by the Project Leads and suggest refinements to ensure resource feasibility, architectural alignment, requirements alignment across all TPTP projects. The expected outcome is approved TPTP 4.3 Draft Plan. (June 16-22)

Community Review of 4.3 Draft Plan (June 23 - July 7)

The draft plan document will be published around June 23rd on TPTP website and announced to community via tptp-news, tptp-pmc, and tptp newsgroup for review and feedback. This is an opportunity for gaining community acceptance as well as an opportunity for community to commit additional contributions to address requirements deferred due to resource gaps. 

Approval of Final Plan (July 12):

Project leaders will drive analysis of the feedback and necessary changes to the draft plan. PMC/PG will review updated plan document and vote to approve the plan. The approved release plan will be published around July 12th on the TPTP website and announced to the community via tptp-news, tptp-pmc, and tptp newsgroup.

Tentative 4.3 Development Schedule

Release Milestones

Milestone Start Date  End Date Description
Iteration 1 Monday, 10-Jul-06 Friday, 11-Aug-06* Defect Fixing + Unit Tests and Test Automation for API
Iteration 2 Monday, 14-Aug-06* Friday, 22-Sep-06 Feature Development + additional defect fixing
Maintenance Release 4.2.1 Monday, 25-Sep-06 Friday, 29-Sep-06 Bug fixes from Iteration 1 + other targeted fixes
Iteration 3 Monday, 2-Oct-06 Friday, 27-Oct-06 Shutdown; Marching to 4.3 GA

* May adjust duration for I1 and I2 based on goals for clearing defect backlog and delivering high priority feature requests.


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.

List of Enhancement Requests


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 API and infrastructure measuring API test coverage. To see a list of known defects, click the link below.

List of Defects