[asterisk-dev] Asterisk Release Schedule

[Rod Dorman]

On Wednesday, October 7, 2009, 16:22:55, Gregory Boehnlein wrote:
> Darnit.. I just spent an hour redoing my slides discussing the Current
> Release structure! :)
>
> But this looks good. Very Ubuntu.

It's also very similar to Postfix which is another successful open
source project.


>>    The numbering scheme can be interpreted as:
>> 
>>    <Concept>.<Feature>.<Minor>[.Patch]
>> 
>>      * Concept - Something close to a complete rewrite would be
>>        required to increase this number.
>> 
>>      * Feature - An update to this number indicates an update to the
>>        major feature set.
>> 
>>      * Minor - This number reflects an update with bug fixes only.
>> 
>>      * Patch - This number will be optionally used to reflect trivial
>>        changes to a patch release. This is most often used for
>>        security updates.

>> 2.1. Standard
>> 
>>    Standard releases are maintained for one year from their release
>>    date. Once the year is complete, the release series will be
>>    covered with security fixes only for one additional year.
>> 
>> 2.2. Long Term Support (LTS)
>> 
>>    Long Term Support releases will be maintained for four years after
>>    being released. After the four years are complete, the release
>>    series will be covered for security fixes only for one additional
>>    year.
>> 
>> 
>>                       3. Release Numbering Scheme
>> 
>>    The Asterisk 1.6.X releases have played out differently than
>>    originally envisioned. The time between each 1.6.X release has
>>    been longer than expected, and the number of significant changes
>>    to the code has been quite high in each version. So, to better
>>    reflect the reality of what each new feature release contains,
>>    there will be no 1.6.3. Instead, the next feature release will be
>>    Asterisk 1.8.
>> 
>>    The numbering scheme can be interpreted as:
>> 
>>    <Concept>.<Feature>.<Minor>[.Patch]
>> 
>>      * Concept - Something close to a complete rewrite would be
>>        required to increase this number.
>> 
>>      * Feature - An update to this number indicates an update to the
>>        major feature set.
>> 
>>      * Minor - This number reflects an update with bug fixes only.
>> 
>>      * Patch - This number will be optionally used to reflect trivial
>>        changes to a patch release. This is most often used for
>>        security updates.
>> 
>> 
>>                           4. Release Schedule
>> 
>>    The following table shows the release schedule for all existing
>>    Asterisk releases, as well as the schedule for the next planned
>>    release.
>> 
>>    +----------------------------------------------------------------+
>>    | Release | Release  | Release    | Security Fix    | EOL        |
>>    | Series  | Type     | Date       | Only            |            |
>>    |---------+----------+------------+-----------------+------------|
>>    | 1.2.X   |          | 2005-11-21 | 2007-08-07      | 2010-11-21 |
>>    |---------+----------+------------+-----------------+------------|
>>    | 1.4.X   | LTS      | 2006-12-23 | 2010-12-23      | 2011-12-23 |
>>    |---------+----------+------------+-----------------+------------|
>>    | 1.6.0.X | Standard | 2008-10-01 | 2010-04-01 ***  | 2010-10-01 |
>>    |         |          |            |                 | ***        |
>>    |---------+----------+------------+-----------------+------------|
>>    | 1.6.1.X | Standard | 2009-04-27 | 2010-04-27      | 2011-04-27 |
>>    |---------+----------+------------+-----------------+------------|
>>    | 1.6.2.X | Standard | TBD (Q4    | TBD + 1 year    | TBD + 2    |
>>    |         |          | 2009)      |                 | years      |
>>    |---------+----------+------------+-----------------+------------|
>>    | 1.8.X   | LTS      | TBD        | TBD + 4 years   | TBD + 5    |
>>    |         |          |            |                 | years      |
>>    +----------------------------------------------------------------+
>> 
>>    Table 1: Asterisk Release Schedule (*** Dates extended due to the
>>    timing of the new policy)
>> 
>> 
>> --
>> Russell Bryant
>> Digium, Inc. | Engineering Manager, Open Source Software
>> 445 Jan Davis Drive NW - Huntsville, AL 35806 - USA
>> Check us out at: www.digium.com & www.asterisk.org
>> 
>> _______________________________________________
>> --Bandwidth and Colocation Provided by http://www.api-digital.com--
>> 
>> AstriCon 2009 - October 13 - 15 Phoenix, Arizona
>> Register Now: http://www.astricon.net
>> 



-- 
rodd at polylogics.com     "The avalanche has already started, it is too
Rod Dorman              late for the pebbles to vote." - Ambassador Kosh