Proposed changes to Asterisk release and support cycles
As documented here, the current plans for Asterisk 11 and later releases state that there will be a Long Term Support (LTS) release every three years, and two regular releases in the years between.
Some of Digium's large customers (both commercial and open-source) have expressed some concerns about the amount of time between the LTS releases, and the amount of time that an LTS release would be supported after its 'replacement' LTS release has been made (which would be one year, based on the current plans). After a great deal of discussion amongst Digium's development team and project management, we've decided to propose changing the release plans somewhat. The new plan would have an LTS release every other year, and regular releases in between them. This would accomplish a few things:
Users of LTS releases would have two years to migrate to a new LTS release before their current one enters the 'security fix only' state, and an additional year if they are willing to continue using it during that time.
Features added to Asterisk would become available in LTS releases as much as a year sooner than they would have otherwise.
It does have some potential downsides, though:
The Asterisk development team (both Digium and community developers) would be 'signing up' to maintain an additional branch; in general, there would be as many as four active branches (not counting those in 'security fix only' state), instead of three.
With the increased frequency of LTS releases, there would be additional pressure to make LTS releases be primarily 'stabilization' releases, instead of adding a lot of new features (or making significant architectural changes). With only one year between LTS and non-LTS releases, more concerted effort would be necessary to increase confidence in the code base before releasing it as an LTS.
The proposed new plan would look like this:
|
發表於 2012-2-1 06:09
| 
