Might I resurrect a suggestion from Benoit from a long time ago?
When the code is frozen, how about branching? That is, branch the
trunk to a 4.2 branch, where all stabilization can occur -- effect the
freeze by creating a branch.
We have been doing this with Open MPI with great success, for example
(merging is still a bit of an effort, but *significantly* easier than
with CVS, and quite manageable once you get the zen of it).
This also allows the trunk to stay open -- there are several things
that didn't make it into 4.2 that need continued work, etc. This way,
that work doesn't need to wait (if people have the cycles, of course).
Just an idea...
--
{+} Jeff Squyres
{+} [EMAIL PROTECTED]
{+} http://www.lam-mpi.org/
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
Oscar-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/oscar-devel
