On 28-11-12 15:49, Dan Creswell wrote:
I'd like to be able to run an experimental test suite with a stable River
trunk to test the test suite so to speak.
I think that's wise equally I'm pondering how you cope with trunk moving on
and breaking a bunch of your tests for which there would be fixes in the
trunk test suite. Are you happy doing merges as and when or ???
Are we talking here about an experimental test suite, in the sense of a
completely parallel testsuite, or an experimental change to the test suite?
2 test suites look a bit much to me. And when the separate experimental
suite is of benefit, it could be integrated making it one again.
An experimental change to the testsuite, if proven, could be
merged/patched into trunk at the same time the shared skunk (shall we
call if dev-branch or so?) is merged.
Gr. Sim
