From: Robert Ramey (ramey_at_[hidden])
Date: 2007-08-01 12:17:25
Doug Gregor wrote:
> On Aug 1, 2007, at 11:25 AM, Robert Ramey wrote:
>> Douglas Gregor wrote:
>>> Until someone gets regression.py updated to work with Subversion, no
>>> tests are run. My understanding of the new testing scheme is that
>>> most of the testing will go on the trunk, but that we'll also
>>> periodically test the stable branch (less frequently). No triggers;
>>> I expect perhaps 2 days of the week will test stable, the rest
>>> testing trunk. Or, for those with the resources, test both nightly.
>> To me, this doesn't sound anything like Beman's proposal which
>> seemed to
>> gained a consensus.
> Frankly, I lost track of that discussion, so my impression of its
> result may be wrong.
> Since this is not related to Subversion, it belongs in a different
Hmmm - well I think you're wrong about that - But its easy to make
a new thread.
The thrust of Beman's proposal is actually quite simple. It consists of
a) designate an branch/trunk as the "Current Release".
b) ALL development occurs on branches.
c) Testing is applied to branches as requested.
d) At the discretion of the release manager, Development branches
are merged into the "Current Release" and the whole system is tested.
e) Each time the "Current Release" test passes more tests than the
previous one, A tag is added by the release manager and a new
download package is automatically created. I would anticipate this
happing about once/month.
The only things we're missing right now are c) - which I believe will be
doable in the near future. And a set of "best practices" for for
developers and the release manager. This is just a question of agreeing
on how to use SVN as regards branches.
If you had nothing else to do, you could make the "Current Release"
/main/trunk etc ONLY updateable by the release manager. Who would
do this by merging in branches which have passed their tests. Then
we'd be in business
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk