From: Beman Dawes (bdawes_at_[hidden])
Date: 2008-05-24 07:22:06
Peter Dimov wrote:
> Beman Dawes:
>> The 1.36.0 release schedule has been set. For details, see
> No mention of 1.35.1? I (and others) have been committing fixes to the
> release branch, expecting it to become .1 some day. Will it? As a release
> manager of the 1.35.x family you ought to have an opinion. :-)
It is fine with me if someone else manages a 1.35.1 release, although it
isn't clear to me who that someone would be. Dave Abrahams is
interested, but I doubt he has the time available.
I'm personally concentrating on smoothing out the regular quarterly
release process so that releases happen as scheduled and with more
quality assurance than is currently the case. That leaves me no time to
manage point releases.
> If yes, we'll need two release branches, one for 1.36.0, one for 1.35.x.
Yes. branches/release will be for 1.36.0. I haven't given any thought to
what the other should be named.
> Either way: what would the procedure for the 1.36 branch be? What is its
> starting point,
> and who's going to do the merging?
Each individual library's maintainer. That's the only approach I know of
that scales, and avoids the release managers becoming bottlenecks.
Good questions, thanks!
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk