Peter Dimov wrote:
Rene Rivera:
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".
Which would lose all fixes currently on the branch.
True, but it should be easy enough to merge specific changes from "branches/release" to a 1.35.1 branch.
I think that the trunk is quite competitive as a starting point for 1.36, because it is currently being integration tested, whereas release+merges is not.
Well the testing of "branches/release" has never stopped. -- -- 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