[Asterisk-Dev] stable/feature freeze?

[Greg Boehnlein]

On Wed, 18 May 2005, Russell Bryant wrote:

> Jeremy McNamara wrote:
> > For once RoyK and me agree on something - I was quite annoyed when I 
> > found out that the new branch of code was called 'stable' when it is 
> > really just a point in time that was decided that nothing major would be 
> > done to that tree and hopefully someday it would become 'stable'.
> 
> If I knew a way to make everyone stop referring to it as the "stable" 
> branch and just refer to it as the "1.0" branch, then I would happily do 
> it.  I agree that "stable" is a bad name, and it just causes stress for 
> me.  I maintain the branch on my own, and pretty much the only time 
> anyone talks to me about it is when they want to complain about their 
> specific problem and want to know why it was a problem in the first 
> place, and then why it wasn't fixed yesterday.

Well, that isn't exactly completely true.. Occassionally I ask you to 
patch the tree with totally inappropriate, non-relevant code. ;) While I'm 
not a maintainer, as time permits I do run through the Bug Tracker and try 
to bring appropriate patches to bear.

Most of the work that I do is against the 1.0 tree, as I'm a big believer 
in running code that is feature frozen when I have to feed my family based 
on it. In many cases, I get flack when I submit patches and updates 
because I generally do not include patches for Head.

When 1.2 is deemed ready for release, I'll focus my energies on that.

-- 
    Vice President of N2Net, a New Age Consulting Service, Inc. Company
         http://www.n2net.net Where everything clicks into place!
                             KP-216-121-ST