[Asterisk-Dev] Re: cvs revision tags

[Tony Mountifield]

In article <393913036.20051121010200 at polylogics.com>,
Rod Dorman <rodd at polylogics.com> wrote:
> On Sunday, November 20, 2005, 17:24:03, SteveK wrote:
> > On Nov 20, 2005, at 5:07 PM, Rod Dorman wrote:
> >>   ...
> >> The only remaining question I have is will any bug/security patches
> >> ever be applied to the v1-2-0 branch, i.e. is there ever any point to
> >> doing a "cvs update -r v1-2-0" ?
> >
> > v1-2-0 is probably not a branch, but a tag;  so (unless the tags are  
> > moved), it would never change.  It is probably exactly equivalent to  
> > v1.2.0.
> >
> > If you already have v1.2.0, cvs update -r v1-2-0 should do nothing.
> >
> > It's there to document exactly what v1.2.0 is; similarly, v1-2-1 will  
> > document v1.2.1, etc.
> 
> OK,  I guess the question I should be asking is, is there a branch based
> on  version  1.2.0  that  will  have  critical  bug and security patches
> applied to it but not experimental/new feature code changes.

No. What you've just described is in fact the v1-2 branch, of which v1-2-1
will be the next released snapshot.

> It  would  be  the  equivalent of what OpenBSD calls the patch or stable
> branch  http://www.openbsd.org/stable.html  essentially  it's  what  one
> would want to track on a production system.

Yes, that's v1-2. It will only have bug fixes, and not experimental or new
features. The latter will continue to go into HEAD.

Cheers
Tony
-- 
Tony Mountifield
Work: tony at softins.co.uk - http://www.softins.co.uk
Play: tony at mountifield.org - http://tony.mountifield.org