Jim Wilson writes: > > Jon Berndt said: > > > > David Megginson wrote: > > > > I agree with Curt. There are two basic strategies for releasing: > > > > 2. Release often, testing every release only lightly. > > > > I think that #2 works better for most cases > > > > > > One way of looking at it is this: The goal isn't to produce individual > > > releases with the greatest quality, it's to produce the best software > > > we can with the resources available. > > > > My current task (daytime) involves leading the development of prototype > > space shuttle flight software, which includes testing the releases and > > writing the release reports. If I took the above approach I'd be out of a > > job in two minutes. Obviously, it's different for volunteer efforts. I would > > That's right, it is different, and I think that should be enough to skip the > rest of your argument.
There is no reason we can't have our cake and eat it too. The way to be able todo this is to use more of CVS features. i.e. USE BRANCHES for all commits. Believe it or not this, lberally using branches within the CVS, leads to less rather then more work as is often percieved. http://dev.zope.org/CVS/ZopeCVSFAQ > I am no less than amazed that we have any sort of release now. Indeed I am always amazed at how any OpenSource project with *multiple* developers manages to get a release out at all :-) Norman _______________________________________________ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
