Hmmm. Maybe I should stay out of this (there hasn't been a release of
Cricket for over a year), but might I recommend a compromise between
Releasing Early And Often and Releasing Only Stable Code?
I still like the middle ground of announcing a code freeze for (say) a
week, asking volunteers to test that snapshot, and then release if no
major issues have been found. If the volunteers didn't get round to
testing, tough luck, but at least you might avoid the situation where a
gazillion of broken copies of FlightGear get shipped with, say, the next
release of FooBSD.
Just be very resolute in announcing the time, timezone and date when,
barring motivated Nays, the release will take place.
Cheers,
-- Bert
--
Bert Driehuis -- [EMAIL PROTECTED] -- +31-20-3116119
If the only tool you've got is an axe, every problem looks like fun!
_______________________________________________
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
