[asterisk-dev] Asterisk 1.6 Release Management Proposal

[Daniel Hazelbaker]

On Oct 17, 2007, at 1:39 PM, Russell Bryant wrote:

> Michiel van Baak wrote:
>> Makes sence.
>> Some patches will need 3 additional commits right?
>> bugfixes to critical bugs that are in all 1.6 versions
>> should go to 3 1.6 releases.
>>
>> Just trying to get the whole picture here.
>
> Correct.  Security issues will likely require a number more  
> commits, but I don't
> know what that number is going to be.  See another part of this  
> thread for that
> discussion.  :)

Since I already deleted that part of the thread and I am too lazy to  
go dig it up...  From a "user" standpoint it doesn't sound like it  
would be any different (or perhaps only slightly different) than  
now.  At some point some "major" set of updates will be moved in  
(remodeling the entire config file system, etc) that will bump  
Asterisk up to 1.8, 2.0, whatever.  But for your average user when  
1.6.(X+1) comes out they will upgrade if either 1) it provides small  
new features they have been waiting for; or 2) it fixes a bug they  
are dealing with wether security or not just as they do now.

It seems like this change is more for developers than users (though  
granted many users are developers in a project like this). To the  
user the 1.6.x versions should simply be more stable than they have  
been in the past.  To that end, it seems to me that as a matter of  
normality security fixes should only need to be applied to the most  
recent released 1.6.x version (which would become 1.6.x.y) and the  
current development 1.6.x branch.  Obviously the development branch  
so it makes it into the next version, but also a "quick fix" to the  
released version so we don't have to wait for development to become  
stable.

Sorry for the long winded theory.

Daniel

> Russell Bryant
> Senior Software Engineer
> Open Source Team Lead
> Digium, Inc.