Beman Dawes wrote:
That would work, and avoid having two directories named trunk. OTOH it now has two directories named 1_35_0.
Is there any point having two copies of the final for a release? Wouldn't it be potentially less confusing for the release manager to move 1_35_0 from svn/boost/branches/release to svn/boost/release at the time of release? And since there would only be one release work-in-progress directory at a time under branches/release, the release level could be eliminated.
So after 1.35.0 ships, the tree would look like:
svn/boost/
trunk/
tags/ ... release/ ... 1_34_1 1_35_0 branches/ 1_36_0 libraries/ python/ serialization/
Yep, we don't need copies of release-candidates lying around: once these become official releases, they can be moved to the /release/ directory. Merrily painting that bike shed yours, John.