Bugzilla Housecleaning Processes

Introduction

As discussed at the June 10, 2009 and June 17, 2009 PMC meetings, we will follow these Bugzilla housecleaning processes to ensure Bugzilla defects and enhancements reflect the current state of the project.

These Bugzilla housecleaning processes are intended to communicate a clear statement to the open-source community and our consuming products that TPTP is in maintenance mode and is only focusing on unresolved defects relative to our current resource levels. Our intent here is to solicit feedback via email and Bugzilla to determine those enhancements/defects of importance to the open-source community and our consuming products. In addition, we hope the open-source community will response with contributions/resources to address some of these enhancements/defects, similar to the outcome of the TPTP 4.5 Component Reorganization.

Bugzilla housecleaning will be completed at the end of each TPTP release.

Enhancements

• All enhancements will be resolved as WONTIFX with the follow comment:

As of TPTP 4.6.0, TPTP is in maintenance mode and focusing on improving quality by resolving relevant defects and increasing test coverage through test creation, automation, Build Verification Tests (BVTs), and expanded run-time execution.  As such, TPTP is not committing to delivering enhancements.  For this enhancement to be considered, please re-open with an attached patch including the Description Document (see http://www.eclipse.org/tptp/home/documents/process/development/description_documents.html), code (see http://www.eclipse.org/tptp/home/documents/resources/TPTPDevGuide.htm), and test cases (see http://www.eclipse.org/tptp/home/documents/process/TPTP_Testing_Strategy.html).

Defects

Newer Unresolved Defects

• For all unresolved and untargeted (--- or Future) defects opened less than 2 years before the General Availability (GA) date of the current TPTP release (for example, opened between June 24, 2007 - June 24, 2009 for TPTP 4.6), the following reminder email¹ will be sent by the Project Lead to the originator of the defect:

As of TPTP 4.6.0, TPTP is in maintenance mode and focusing on improving quality by resolving relevant defects and increasing test coverage through test creation, automation, Build Verification Tests (BVTs), and expanded run-time execution.  Please confirm if the following defect(s) are still relevant and reproducible in the latest TPTP release (http://www.eclipse.org/tptp/home/downloads/):

<defect list>

¹ If the originator of the defect has an inactive Bugzilla account (for example, inactive email address), the defect is triaged by the Project Lead and if no longer relevant, resolved as WONTIFX with the follow comment:

As of TPTP 4.6.0, TPTP is in maintenance mode and focusing on improving quality by resolving relevant defects and increasing test coverage through test creation, automation, Build Verification Tests (BVTs), and expanded run-time execution.  Since this originator of this defect has an inactive Bugzilla account, it may be no longer relevant.  If this defect is still relevant and reproducible in the latest TPTP release (http://www.eclipse.org/tptp/home/downloads/), please re-open.

Older Unresolved Defects

• All unresolved and untargeted (--- or Future) defects opened more than 2 years before the General Availability (GA) date of the current TPTP release (for example, opened on or before June 23, 2007 for TPTP 4.6, released on June 24, 2009) will be resolved¹ as WONTIFX with the follow comment:

As of TPTP 4.6.0, TPTP is in maintenance mode and focusing on improving quality by resolving relevant defects and increasing test coverage through test creation, automation, Build Verification Tests (BVTs), and expanded run-time execution.  Since this defect is more than 2 years old, it may be no longer relevant.  If this defect is still relevant and reproducible in the latest TPTP release (http://www.eclipse.org/tptp/home/downloads/), please re-open.

¹ All defects must be triaged by the Project Lead before resolving as WONTIFX.

Newer Resolved/Unverified Defects

• For all resolved and unverified defects resolved less than 1 year before the General Availability (GA) date of the current TPTP release (for example, opened between June 24, 2008 - June 24, 2009 for TPTP 4.6), the following reminder email¹ will be sent by the Project Lead to the originator of the defect:

As of TPTP 4.6.0, TPTP is in maintenance mode and focusing on improving quality by resolving relevant defects and increasing test coverage through test creation, automation, Build Verification Tests (BVTs), and expanded run-time execution.  Please verify and close the following defect(s) using the latest TPTP release (http://www.eclipse.org/tptp/home/downloads/):

<defect list>

¹ If the originator of the defect has an inactive Bugzilla account (for example, inactive email address), the defect is verified by the Project Lead and verified/closed with the follow comment:

Since this originator of this defect has an inactive Bugzilla account, this defect has been verified/closed by the Project Lead.  If this defect is still unresolved and reproducible in the latest TPTP release (http://www.eclipse.org/tptp/home/downloads/), please re-open.

Older Resolved/Unverified Defects

• All resolved and unverified defects resolved more than 1 year before the General Availability (GA) date of the current TPTP release (for example, opened on or before June 23, 2008 for TPTP 4.6, released on June 24, 2009) will be verified/closed¹ with the follow comment:

Since this defect has been resolved and unverified for more than 1 year, it is considered to be fixed.  If this defect is still unresolved and reproducible in the latest TPTP release (http://www.eclipse.org/tptp/home/downloads/), please re-open.

¹ Bugzillas resolved as a duplicate of another Bugzilla will not be verified/closed.