[boost] Why the integration branchmust remain clean, etc.

Subject: [boost] Why the integration branchmust remain clean, etc.
From: David Abrahams (dave_at_[hidden])
Date: 2009-06-08 07:48:11

I just realized I can articulate what's not working for me about the
current trunk/release branch arrangement.  

* IIUC, there are always lots of failures on the trunk because there's
  no pressure to keep it clean.

* Before I check in a change in one of my libraries, I want to make sure
  I haven't broken anything else in boost.  So naturally, I run the
  whole regression suite (there oughta be a better way!)

* But since the trunk is not clean, I spend a lot of time analyzing
  problems that have nothing to do with my library.  That's a real
  disincentive to making changes in Boost.  In fact, I am confident my
  low activity in the repo over the last year or so is primarily caused
  by the amount of labor associated with testing my changes.

Now, maybe you'll suggest that I test my own library, then damn the
torpedoes and check in the changes, and let other people complain to me
when their libraries break.  That would work... except that many people
aren't paying attention to the health of their libraries on the trunk.

I suppose another approach might be to test against the release branch,
then svn switch to the trunk and check in my changes there.  But that is
still laborious.

I'm not sure what to do about this, but it's really killin' me.

-- 
Dave Abrahams
BoostPro Computing
http://www.boostpro.com