> Well, I object. How could I tell others to postpone their contribution > until after the release of FlightGear 1.0 if you are allowed to add this > rather comprehensive peace of code? >
What about labelling the fg tree with your own 1.0 pre-release label? And branching off it, only merging in the trunk changes that you see fit? I have no problem creating a second devel. env. to test both versions, and I think others can do the same, for the benefit of better quality of the upcoming 1.0 release. V. _______________________________________________ Flightgear-devel mailing list [email protected] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
