Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

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

1.2.Xx

 

2005-11-21

2007-08-07

2010-11-21

1.4.Xx

LTS

2006-12-23

2011-04-21

2012-04-21

1.6.0.Xx

Standard

2008-10-01

2010-05-01

2010-10-01

1.6.1.Xx

Standard

2009-04-27

2010-05-01

2011-04-27

1.6.2.Xx

Standard

2009-12-18

2011-04-21

2012-04-21

1.8.Xx

LTS

2010-10-21

2014-10-21

2015-10-21

10.Xx

Standard

2011-12-15

2012-12-15

2013-12-15

11.x

LTS

2012-10-25

2016-10-25

2017-10-25

12.x

Standard

2013-12-20

2014-12-20

2015-12-20

13.x

LTS

2014-10-24

2020-10-24

2021-10-24

14.xStandard2016-09-262017-09-262018-09-26

15.x

Standard

2017-10-03

2018-10-03

2019-10-03

16.xLTS2018-10-092022-10-092023-10-09
17.xStandard2019-10-282020-10-282021-10-28
18.xLTS2020-10-202024-10-202025-10-20
19.xStandard2021-11-022022-11-022023-11-02
20.xLTS2022-10-192026-10-192027-10-19
21.xStandard2023-10-182025-10-182026-10-18

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.

...

For developers, it is useful to be aware of when the major feature freeze (major features are defined as those which introduce incompatible changes, break binary compatibility, or make substantial core changes) for a particular branch will occur. The major feature freeze for a branch will occur 3 months prior to the release of a new Asterisk version, and a reminder announcement will be posted to the asterisk-dev mailing list approximately 60 days prior to the feature freeze. Asterisk versions are slated to be released the 3rd Wednesday of October. The major feature freeze for a branch will occur the 3rd Wednesday of July. An announcement reminder will be posted to the asterisk-dev mailing list the 3rd Wednesday of May. Major feature freeze consists of the creation of the release series branch. Features can continue to be placed into the release series branch alongside bug fixes according to policy. New major changes or breaking changes are no longer acceptable in the release series once the major feature freeze has been done. 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.

...