> That's right, it is different, and I think that should be enough to skip the > rest of your argument. Given everyone's commitments, especially Curt's (with > the new baby), I am no less than amazed that we have any sort of > release now.
Like I said - I'm in that boat, too (X2!) and very sensitive to that concern, with the past two months filled with sickness rotating amongst the six of us and an additional and separate open source project under heavy development. My "suggestions" and comments are made with all due respect to our various participants' pressing needs and responsibilities, and with special consideration of Curt, who has to put the release together. Perhaps we ought to come to an agreement on what releases are for. My feeling is that when we release something it ought to be held to a higher standard than what is generally in CVS, it ought to go through testing from as many people as possible, and that once a pre-release is let out, no NEW features should be allowed in - only bug fixes. The second pre-release should be effectively what is released, unless something glaring is found. Both pre-releases ideally ought to encompass a full weekend, and last at least four or five days, with the first one perhaps longer. These are just suggestions off the top of my head. > I think you've ignored Curt's response to this the first time, why are you > repeating the same point? I'm not sure what you are talking about. I don't think I am ignoring Curt's comments - I read them all. The idea is that we ought to come to an agreement on what is expected when a release is impending: 1) Changes are halted at a specified time. 2) Pre-release 3) Bug fixes only 4) Final Pre-release 5) Release 6) back to normal ... My biggest gripe (and I am not angry about this, or perturbed) is that the second pre-release came about pretty quickly (and I wasn't the only one who was a little surprised). It would have been nice to allow some others to test on the weekend. If that means an opportunity for Curt passes by for another week, then we have to accept that a few times a year we are going to have to hold off on CVS commits for a few days - no big sacrifice, I think. IMHO, this doesn't add to Curt's workload - only stretches out the schedule. The big caveats here are that I have never had to do a FlightGear release, and I don't live in Curt's shoes. > Let's see what happens then. Can you still do some testing now > anyway? It is never too late to contribute a bug fix. I will begin the update and build process immediately. I'm simply trying to make some suggestions for process improvement. :-) Jon _______________________________________________ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
