Curt and others, Just a quick question: Does this mean, we're entering a feature-freeze period now? The reason I'm asking is that I have some upates for the traffic manager that I was planning to clean-up a bit and submit by the end of the weekend. This new code, while humble in size, is going to be a big step forward because it eliminates the dependency on predefined flightplans, and thus allows for much more flexibility in creating Traffic files.
I'm also in the process of creating some sample traffic patterns for the 737, going in and out of KSFO, based on the current United Airlines time table. I'd also like to see these included in the new version (and they depend on the new code), because it would liven up the dynamic scenery around KSFO quite a bit. As an aside, just after the release of 0.9.4, I reported two segfaults occurring randomly after prolonged FlightGear use (approx 8-10 hours of run time). One of those I managed to track down, but the other one never really got much attention. Would people downloading and testing the prereleases be willing to run FlightGear for extended periods of time (preferably from within gdb, so that we can try to find some evidence whether or not this bug is still there and find some evidence about it's nature? Any thoughts? Cheers, Durk On Friday 16 July 2004 17:34, Curtis L. Olson wrote: > I've started doing some of the pre-release work for FlightGear-0.9.5 > (which is the next release.) That means I'd like to do our "official" > next release in the next week or two. Please take a few minutes to > download the tar balls and test this pre1 release. Please! This is our > quality control so if no one tests the pre releases and reports > problems, they will end up in the final release. > > Regards, > > Curt. _______________________________________________ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
