Hi, one week to go, before we create the release-branch for 2.4.0. We still have some 80 bugs in out bug tracker at http://code.google.com/p/flightgear-bugs/issues/list
I'd really love to get this number significantly down before we branch. Please browse to http://code.google.com/p/flightgear-bugs/issues/list (ignore the 500 error message and hit reload - google is buggy here) and scroll down to any bug that hits an area of your interest. The easiest way to help is by picking one of the "Stalled" bugs and simply verify if the reported malfunction still exist. Those, who can log into Google's services are welcome to place a comment and change the status to "Accepted" again or even close the issue with "Fixed". If you can't log on or don't want to mess with the tracker, any feedback referring to a bug-id on this list is welcome. We can accept a mouse in our cockpit, but we certainly don't want any bugs! Thanks for reading, Torsten ------------------------------------------------------------------------------ All of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-d2d-c2 _______________________________________________ Flightgear-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/flightgear-devel
