[asterisk-dev] Asterisk Release Schedule

[Johan Wilfer]

Russell Bryant skrev:
> Greetings,
> 
> This document discusses proposed changes to Asterisk release policy.  I
> look forward to your feedback!
<snip>
> 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.

>    +----------------------------------------------------------------+
>    | 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      |
>    +----------------------------------------------------------------+

For some time ago there was a lot of talk about the Asterisk code base 
changing to fast, to much. Despite the sometimes harsh words we have 
seen many compatibility-options since then making it a lot easier to 
upgrade between release series.

In light of this I would suggest adding a year or two to the EOL of the 
release series, stretching the period when only security issues are 
fixed. For example look at 1.2 that have spend approx 3 years that way 
when end-of-life is reached.

The point is - how much work is involved in making these security fixes?
I this this would make those users who hire an asterisk-consultant very 
happy... Could this be done with a resonable efort?

Greetings
Johan Wilfer