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

Last revised: November 21, 2007

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

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 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.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:

  • Quality: significant reduction of defect backlog
  • Java 6 support
  • IPv6 support
  • Support for "application" mode in the Java 1.5+ (JVMTI) Profiler

Planning Process

Input from Community (August 10 – August 24):

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.

Input from Contributors (August 10 – August 24):

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

Input from Committers/PMC (August 10 – August 24):

Committers, project leads, and PMC can propose enhancements or improvements that are aligned with overall project goals and roadmap. For example, the AG representative will propose via the 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 (August 27 - Oct 18)

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.

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. (Oct 11)

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.5 Draft Plan. (Oct 18)

Community Review of 4.5 Draft Plan (Oct 18)

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. 

Approval of Final Plan (October 24):

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 on the TPTP website and announced to the community via the PMC and news mailing lists or the TPTP newsgroup.

Tentative 4.5 Development Schedule

Release Milestones


Start Date

 End Date


Iteration 3

Wed 3-Oct-07

Wed 14-Nov-07

Defect Fixing + Unit Tests and Test Automation for API

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 + API freeze

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

Detailed Schedule


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.

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.