OpenTM2 Release Version Number Policy

OpenTM2 version number consists of up to two digits separated by dot.

• First two digits are used for major release number. 
  
• Second digit in a release number indicates a maintenance update.

Ticket Life Cycle

Here is a description of the life cycle of an OpenTM2 Trac ticket, a feature request or a bug report, from initial submission through implementation and review to release.

Feature Proposals and Design

1. All design proposals (for any additions and changes) must be proposed on the opentm2-design mailing list.
2. The proposal email itself must include:
   
1. The proposed (new or changed) change description
   
2. A Trac ticket number
3. A Suggested proposal reviewer
   
4. A deadline for comments (usually two weeks from proposal).
3. Background information in the proposal can be helpful if the topic is complex. If there is a lot of information, write a design doc.
   
4. The proposal must be reviewed by someone before submitting, and the reviewer must reply to the posting.
5. In the OpenTM2 Steering Committee meeting, we have a regular agenda item to confirm recent proposals (before or after code submission). Here we confirm that someone has reviewed it and no one objects.
6. Changes that are discovered to not have proposal is withdrawn at or before the development freeze milestone.
7. Major functionality or disruptive changes need to be implemented on a branch. The change there must be reviewed and confirmed before merging it to the trunk.
   

OpenTM2 Coding Style Guidelines

The OpenTM2 coding guidelines are described in the [TBD].

OpenTM2 Release Process

The release task list contains the list of things to complete when releasing a a new version of the OpenTM2 deliverable.