There are multiple supported release series of Asterisk. Once a release series is made available, it is supported for some period of time. During this initial support period, releases include changes to fix bugs that have been reported and features that have been added following policy (features must not introduce backwards incompatible behavior and must include tests when possible). At some point, the release series will be deprecated and only maintained with fixes for security issues. Finally, the release will reach its End of Life, where it will no longer receive changes of any kind.
The type of release defines how long it will be supported. A Long Term Support (LTS) release will be fully supported for 4 years, with one additional year of maintenance for security fixes. Standard releases are supported for a shorter period of time, which will be at least one year of full support and an additional year of maintenance for security fixes.
The following table shows the release time lines for all releases of Asterisk, including those that have reached End of Life.
|Release Series||Release Type||Release Date||Security Fix Only||EOL||Current Status|
New releases of Asterisk will be made roughly once a year, alternating between standard and LTS releases. Within a given release series that is fully supported, bug fix updates are provided roughly every 4 to 6 weeks. For a release series that is receiving only maintenance for security fixes, updates are made on an as needed basis.
If you're not sure which one to use, choose either the latest release for the most up to date features, or the latest LTS release for a platform that may have less features, but will usually be around longer.
For developers, it is useful to be aware of when the next release branch will be created. Upon creation of the branch it becomes bound by the same policies as any release branch: no introduction of incompatible changes, no breaking of binary compatibility, and no substantial core changes. The creation of the release branch occurs the 2nd Wednesday of August. A reminder is sent a week before to the asterisk-dev mailing list on the 1st Wednesday of August. Once the release branch is created it will receive all bug fixes and feature changes which also go into the existing release branches. On the 2nd Wednesday of September an initial release candidate for the new version is created alongside release candidates for all other current supported release series. Additional release candidates will be created as needed based on fixes for issues reported. On the 3rd Wednesday of October full releases for all supported release series are created.
For additional information on policies please see the Software Configuration Management Policies wiki page.
|Asterisk Release Branch Creation Reminder||1st Wednesday of August|
|Asterisk Release Branch Creation||2nd Wednesday of August|
|First Release Candidate of Asterisk Branch||2nd Wednesday of September|
|First Release of Asterisk from Branch||3rd Wednesday of October|