Not quite.

What I was asking for was for when the "freeze" occurs, just branch immediately. The trunk stays open. The branch is frozen and is what is stabilized for release.

Fixes that go on the branch typically also go on the trunk; new stuff that goes on the trunk likely won't go on the branch. And so on.

And I was reminded by a mob with torches and pitchforks that this is what we have done before. ;-)



On Aug 11, 2005, at 3:22 PM, John Mugler wrote:


Well yeah, but we were frozen for quite a while before we got all the bugs out and new beta's were repeated copies off the corrected trunk.

What Jeff asked (or what i thought he was suggesting), is that we limit the freeze time on the trunk and make a branch to fix up for the release. Thus, bugfixes and patches and what not will have to go into (possibly) both places. And new beta's will not be trunk copies at some point, they'll be copies of the branch, i would guess.

--   John

On Thu, 11 Aug 2005, Lombard, David N wrote:

From: John Mugler on Thursday, August 11, 2005 11:20 AM

I'd be ameniable to this. I think it'll work if we are smart about
when we
do the branch.

On Thu, 11 Aug 2005, Jeff Squyres wrote:

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.

I don't mean to be denser than normal, but isn't this what we did with
4.0, 4.1, et al?




--
{+} 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

Reply via email to