2,561
edits
FlightGear Newsletter February 2010: Difference between revisions
Jump to navigation
Jump to search
m
FlightGear Newsletter February 2010 (view source)
Revision as of 13:40, 18 February 2010
, 18 February 2010adding link to bug tracking system that is now being used
m (new section: "new wiki articles" -> linking to Howto: Modelling Clouds to make this howto more widely known) |
m (adding link to bug tracking system that is now being used) |
||
| Line 6: | Line 6: | ||
==What's new in CVS== | ==What's new in CVS== | ||
== Finally: Bug Tracking == | |||
As of February 2010, fellow FlightGear developers and users are encouraged [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg26333.html] [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg26380.html] to file ''bug'' reports using http://code.google.com/p/flightgear-bugs/issues/list | |||
Please note that this tracker is at the moment purely meant to be used for ''bug tracking'' purposes [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg26354.html], i.e. bugs directly related to FlightGear and not for feature requests (there are plans being discussed to eventually set up a separate tracker for these [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg26357.html]). | |||
At the moment, this tracker is being used for both, FlightGear core, as well as the base package (aircraft, scenery etc) - this may however change at a later time once the tracker is being used more widely to help developers differentiate between core coding related issues and those that are related to base package contributions such as individual aircraft [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg26342.html]. | |||
==In the hangar== | ==In the hangar== | ||