Thu Oct 11 06:49:58 2012

Asterisk developer's documentation

Asterisk Release and Commit Policies

The information contained on this page may be out of date. To make sure you get the most current information, please make sure that you are using the documentation generated from Asterisk trunk.

Asterisk Release Status

For more information on the current status of each Asterisk release series, please see the Asterisk Release Status page:

Commit Monitoring

To monitor commits to Asterisk and related projects, visit The Digium mailing list server hosts a number of mailing lists for commits.

Asterisk 1.0

SVN Branch

Release and Commit Policy

No more releases of Asterisk 1.0 will be made for any reason.

No commits should be made to the Asterisk 1.0 branch.

Asterisk 1.2

SVN Branch

Release and Commit Policy

There will be no more scheduled releases of Asterisk 1.2.

Commits to the Asterisk 1.2 branch should only address security issues or regressions introduced by previous security fixes. For a security issue, the commit should be accompanied by an Asterisk Security Advisory and an immediate release. When a commit goes in to fix a regression, the previous security advisory that is related to the change that introduced the bug should get updated to indicate that there is an updated version of the fix. A release should be made immediately for these regression fixes, as well.

Asterisk 1.4

SVN Branch

Release and Commit Policy

Asterisk 1.4 is receiving regular bug fix release updates. An attempt is made to make releases of every four to six weeks. Since this release series is receiving changes for all types of bugs, the number of changes in a single release can be significant. 1.4.X releases go through a release candidate testing cycle to help catch any regressions that may have been introduced.

Commits to Asterisk 1.4 must be to address bugs only. No new features should be introduced into Asterisk 1.4 to reduce the number of changes to this established release series. The only exceptions to this rule are for cases where something that may be considered a feature is needed to address a bug or security issue.

Asterisk 1.6

SVN Branch

Release and Commit Policy

Asterisk 1.6 is managed in a different way than previous Asterisk release series. From a high level, it was inspired by the release model used for Linux 2.6. The intended time frame for 1.6.X releases is every 2 or 3 months. Each 1.6.X release gets its own branch. The 1.6.X branches are branches off of trunk. Once the branch is created, it only receives bug fixes. Each 1.6.X release goes through a beta and release candidate testing cycle.

After a 1.6.X release is published, it will be maintained until 1.6.[X + 3] is released. While a 1.6.X release branch is still maintained, it will receive only bug fixes. Periodic maintenance releases will be made and labeled as 1.6.X.Y. 1.6.X.Y releases should go through a release candidate test cycle before being published.

For now, all previous 1.6 release will be maintained for security issues. Once we have more 1.6 releases to deal with, this part of the policy will likely change.

For some history on the motivations for Asterisk 1.6 release management, see the first two sections of this mailing list post.

Asterisk Trunk

SVN Branch

Release and Commit Policy

No releases are ever made directly from Asterisk trunk.

Asterisk trunk is used as the main development area for upcoming Asterisk 1.6 releases. Commits to Asterisk trunk are not limited. They can be bug fixes, new features, and architectural improvements. However, for larger sets of changes, developers should work with the Asterisk project leaders to schedule them for inclusion. Care is taken not to include too many invasive sets of changes for each new Asterisk 1.6 release.

No changes should go into Asterisk trunk that are not ready to go into a release. While the upcoming release will go through a beta and release candidate test cycle, code should not be in trunk until the code has been tested and reviewed such that there is reasonable belief that the code is ready to go.

Asterisk Team Branches

SVN Branch

Release and Commit Policy

The Asterisk subversion repository has a special directory called "team" where developers can make their own personal development branches. This is where new features, bug fixes, and architectural improvements are developed while they are in progress.

Just about anything goes as far as commits to this area goes. However, developers should keep in mind that anything committed here, as well as anywhere else on Digium's SVN server, falls under the contributor license agreement.

In addition to each developer having their own space for working on projects, there is also a team/group folder where group development efforts take place.

Finally, in each developer folder, there is a folder called "private". This is where developers can create branches for working on things that they are not ready for the whole world to see.

Generated on Thu Oct 11 06:49:58 2012 for Asterisk - the Open Source PBX by  doxygen 1.5.6