on Wed Jul 13 2011, "Robert Ramey" <ramey-AT-rrsd.com> wrote:
Beman Dawes wrote:
Also, I'm (again) offering the suggestion that the periodic testing be altered so that a library X on the trunk is tested againts the current state of the libraries on the release branch (that is the NEXT release). I believe this would have a number of benefits - including the streamlining of the release process. It would also speed up the testing itself since the release branch changes less frequently so there would be fewer dependencies for each test. This would require a change in the testing scripts - but not a huge one. FWIW, this is the testing that I do on my own machine so that it isolates my errors from any changes do to unknown/unexpected changes in other libaries. So I know from personal experience that this is an improvement.
Robert, I'm with you on this. It's one of the things we're doing with Ryppl. -- Dave Abrahams BoostPro Computing http://www.boostpro.com