Re: [boost] 1.35 release approach (was [1.34.0] Deadline)

From: Doug Gregor (dgregor_at_[hidden])
Date: 2007-05-07 08:40:46

On May 4, 2007, at 8:35 PM, David Abrahams wrote:

>
> on Fri May 04 2007, Douglas Gregor <doug.gregor-AT-gmail.com> wrote:
>
>> On Wed, 2007-05-02 at 18:30 -0400, Beman Dawes wrote:
>>> That isn't at all what I had in mind. Rather, a release, say 1.35  
>>> would
>>> start with the previous release - 1.34 in this case. Developers, who
>>> have been working in devel (which is equivalent to the old HEAD),
>>> branch/tag their code at the point they think it is OK as  
>>> "stable". Then
>>> when it comes time to do a release a script run by the release  
>>> manager
>>> tries to merge code for the library from "stable" to the release
>>> candidate branch (working in library dependency order, with cycles
>>> broken when necessary).
>>
>> I'm a bit confused... is "stable" a branch, or just a way to refer to
>> certain points in the development of a library?
>
> What's the difference (in the SVN world)?

What I meant was: is "stable" some snapshot of Boost (as a whole)  
that we'll be running regression tests on, or is it just some kind of  
library-specific label that is transient and used only to merge  
things into the current release branch?

        - Doug