On lundi 12 janvier 2009, Stefan Seifert wrote: > > I think this is a very good example of why regular releases are good. > > When the next release is already in sight, the pressure to push "huge > updates" into maintenance releases lowers considerably. So, yes, it would > be nice to have a much better c172 now, but it's still ok, to see it fly in > a few months, perhaps even still better. > > And related: having release branches would be at least equally nice. As of > now CVS head does not even represent the current development version > anymore, because people are holding back patches not fit for a maintenance > release. As branching in CVS is very expensive, we now have another reason > to migrate to _any_ other VCS. > > So, is there anything I could do to help speeding up this migration? > > Stefan
I agree, we want branches , with at least one which represents the real current development. We don't have free time any time. We are able to contribute only when that free time is there. On my "poor" side, for instance, i cannot wait for updates which will come "a day" (sync with JSBSim cvs) , i do have my own FG updated, and i do work with that local version, deciding to update within FG the models that i am working on, when i have some free time. In addition to it, doing so, spare time (time is money :) ). I may hope that a day these models will be sync with FG. I am not expert, but i feel it is missing a real coordinator to manage both branches => current devel, and => maintenance release. Cheers -- Gérard http://pagesperso-orange.fr/GRTux/ J'ai décidé d'être heureux parce que c'est bon pour la santé. Voltaire ------------------------------------------------------------------------------ This SF.net email is sponsored by: SourcForge Community SourceForge wants to tell your story. http://p.sf.net/sfu/sf-spreadtheword _______________________________________________ Flightgear-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/flightgear-devel
