[asterisk-dev] Asterisk Release Schedule

[Gregory Boehnlein]

Darnit.. I just spent an hour redoing my slides discussing the Current
Release structure! :)

But this looks good. Very Ubuntu.

> -----Original Message-----
> From: asterisk-dev-bounces at lists.digium.com [mailto:asterisk-dev-
> bounces at lists.digium.com] On Behalf Of Russell Bryant
> Sent: Wednesday, October 07, 2009 3:52 PM
> To: Asterisk Developers Mailing List
> Subject: [asterisk-dev] Asterisk Release Schedule
> 
> Greetings,
> 
> This document discusses proposed changes to Asterisk release policy.  I
> look forward to your feedback!
> 
> Thanks,
> 
> 
> --------------------------------------------------------------
> 
> 
>                        Asterisk Release Schedule
> 
>                     Copyright (c) 2009, Digium, Inc.
>                           All Rights Reserved.
> 
>                          Document Version: 0.5
>                         Last Updated: 2009-10-07
> 
>           Asterisk Development Team <asteriskteam at digium.com>
> 
> 
>    Table of Contents
> 
>    1. Introduction
>    2. Release Types
>    2.1. Standard
>    2.2. Long Term Support (LTS)
>    3. Release Numbering Scheme
>    4. Release Schedule
> 
> 
>                             1. Introduction
> 
>    This document discusses an updated release schedule for the
>    Asterisk project. Previously, release schedules for a given
>    Asterisk release series have been handled on a case by case basis.
>    Instead, we will now have defined time frames for how long a
>    release series will be maintained. We also introduce the concept
>    of a release type, which will dictate how long a release series
>    will be maintained. Changes to the numbering scheme of Asterisk
>    releases are discussed, as well.
> 
> 
>                             2. Release Types
> 
>    Each release series will be specified as one of two types. There
>    are Standard releases, and Long Term Support (LTS) releases. A
>    release series is feature frozen. Full maintenance of a release
>    series means that there will be updates that include general bug
>    fixes. Security only maintenance means that a release series will
>    only be updated to address important security related issues.
> 
> 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
> 
> asterisk-dev mailing list
> To UNSUBSCRIBE or update options visit:
>    http://lists.digium.com/mailman/listinfo/asterisk-dev
> 
> --
> This message has been scanned for viruses and
> dangerous content by N2Net Mailshield, and is
> believed to be clean.