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.
Over time, the release-early-release-often approach leads to strong, robust software because we go through many more release cycles; in fact, I'd like to see a minor release at least four times a year, if not bimonthly.
It's an evolution thing: we get better software five years from now in exchange for the occasional bug now (think of how bacteria evolve resistence to antibiotics). We can afford to go long-term, while you necessarily have to think short-term since you have lives on the line.
All the best,
David
_______________________________________________ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
