Boost logo

Boost :

From: Vladimir Prus (ghost_at_[hidden])
Date: 2007-09-06 02:17:22


Frank Birbacher wrote:

> Hi!
>
> Vladimir Prus schrieb:
>> 2. Say Boost 1.35 is released. Week later, a big source-incompatible
>> change to some library is merged to release-ready tree. Week later, a
>> serious bug is found in another library. Is there a place where that bug
>> can be fixed? Release-ready tree already has source-incompatible change
>> to other library? In other words -- from which tree is 1.35.1 going to be
>> released?
>
> Should we have a "release-ready tree" and a "release-1-35-fixing" branch
> which gets all fixes merged in? The "source incompatible" change would
> only go into the release-ready-tree but not into the release-1-35-fixing
> tree (which can be tagged as release-1-35-1 when done fixing/when
> releasing).

That's what I'm driving at.

- Volodya


Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk