Robert Ramey wrote:
Vladimir Prus wrote:
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.
I think this is even simpler
1) use the release branch 2) put the library to be tested into that branch - only on the local testing machine. 3) CD to boost/libs/newlib/test 4) run ../../../tools/src/library_test.sh (or bat) --toolset=msvc-7.1 (or whatever) 5) this will create a pair of local html tables in boost/libs/newlib/test which show all test results.
This only requires a tester.
I think all these tests require manual steps from the tester. The automated procedure I have suggested requires just adding a single command invocation to the periodic command invocation service of your operating system -- which is *much* less burden. - Volodya