Andy Ross wrote: > Martin Spott wrote: >> Another example (among others) is the altimeter-dialogue that was >> recently introduced by DaveM. [...] I have to familiarize myself with >> that feature. How should this be done with such a short pre-release >> cycle ?
> I don't follow. Are you trying to say that the feature should never > have gone out in the release, or that there is no use in providing > feedback and/or improving features once they have been released? [...] > Especially in this case, I can't see Curt holding this release back > due to a minor i18n issue with the altimeter dialog even if you had > been given a month to air your grievances. I have the impression that you're talking about something completely different. I'm took as an example that David added a new feature on March 23rd (tuesday) and Curtis did the release 3 days later on friday. How should anyone with a full-time job get the chance to explore and test a new feature in a sufficient manner. Please don't misunderstand me: I don't request _anyone_ to make a compromise in order to deal with the way _I_ can afford giving spare time to the FlightGear project. I just ask you (or whom it may belong to) to acknowledge that such a tight release process makes it _extremely_ difficult for part-time contributors (like me) to follow the track, Martin. -- Unix _IS_ user friendly - it's just selective about who its friends are ! -------------------------------------------------------------------------- _______________________________________________ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
