Doug Gregor wrote:
When we release 1.34.0, we switch to Subversion. The repository layout (documented at http://svn.boost.org/trac/boost/wiki/ BoostSubversion) contains two branches, "stable" and "devel". Changes go into devel first, get tested, then migrate to the "release-ready" stable branch. IIRC, this is one of the recommendations in Beman's proposal, and it's much easier to enforce in the world of Subversion.
One thing that is 'merely' a matter of good engineering practice, but which Subversion makes much easier through atomic commits, is that changesets should be minimal and self-contained, and never contain unrelated changes. This helps tremendously when merging changesets across branches, and figuring out a cause of a regression (say). FWIW, Stefan -- ...ich hab' noch einen Koffer in Berlin...