Peter Dimov wrote:
Beman Dawes:
The 1.36.0 release schedule has been set. For details, see http://svn.boost.org/trac/boost/wiki/ReleaseSchedule
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. :-)
If yes, we'll need two release branches, one for 1.36.0, one for 1.35.x.
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?
I thought that was clear from previous messages, but I'll mention what my understanding is... "branches/release" is for 1.36.0 *only*. There needs to be another branch for 1.35.1 (perhaps "branches/release_1_35_1") which I would guess the manager for the 1.35.1 release would take care of by branching from "tags/release/Boost_1_35_0". As for the starting point for 1.36, it's always been the rolling "branches/release" i.e. 1.35.x, which is now the 1.36.x branch :-) It also means that patches that go into the 1.35.1 branch would also likely need to go into the 1.36.x branch. -- -- Grafik - Don't Assume Anything -- Redshift Software, Inc. - http://redshift-software.com -- rrivera/acm.org (msn) - grafik/redshift-software.com -- 102708583/icq - grafikrobot/aim,yahoo,skype,efnet,gmail