At Monday 2005-03-07 22:05, you wrote:
Victor A. Wagner Jr. writes:
AND can we talk about HOW we're going to manage the cvs this time (with the testers also?) or are we gonna do it the way we've been muddling through on the past releases? I submit that having the regression testers do ANYTHING other than let the automated stuff run is essentially unacceptable.
You'd _have_ to switch between branches at some point (unless we branch for release immediately once the timeframe has been decided on),
I'm suggesting that the work continue on the mainline towards release and that anyone working on something OTHER than the release, work on a branch. That way as long as we're playing with CVS the testers don't have to do ANYTHING to their already functioning scripts. The only people who will need to worry about weird labels will be those working on stuff unrelated to the release.
and regardless of everything else the tarballs still need to be tested as we come close to the finish line because that's what actually gets released. But I guess the latter can be automated, and on the whole, I agree.
For tarballs testing, how about we modify 'regression.py' to check some specific location for new tarballs and give preference to them over the branch testing for one round?
-- Aleksey Gurtovoy MetaCommunications Engineering _______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
Victor A. Wagner Jr. http://rudbek.com The five most dangerous words in the English language: "There oughta be a law"