Subject: Re: [boost] is review system in place is extremely slow? (was Re: [rfc] rcpp)
From: Vladimir Prus (vladimir_at_[hidden])
Date: 2010-02-28 13:58:27
Gennadiy Rozental wrote:
> Paul A. Bristow wrote:
>> But nobody has yet responded to the vital question of whether there are
>> resources to support a parallel tree to trunk,
>> in addition to sandbox, for what we are calling 'candidate' libraries. It
>> really needs to have an identical structure,
>> and tests which are run regularly, like trunk. This will encourage more users,
>> who have an important, and often informed, voice in reviews.
> IMO we do not need this. Candidate libraries should compile and test
> against last release. We can't expect to sync all development efforts.
This is pretty straight-forward to implement:
1. Create a branch off the last release
2. For each proposed library living in sandbox, add a couple of svn:externals
into the new branch.
3. Modify status/Jamfile.v2 to only run the tests for the new libraries.
4. Have one, or more people run tests on the new branch.
5. Adjust reporting process to produce one more set of tables.
Of this, (1) and (2) is done in a matter of minutes. (3) requires really
minimal hacking. (4) requires a volunteer. I personally don't know how to
do (5) but should not be hard either.
So, where do we go from here?
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk