Changes

Jump to navigation Jump to search
151 bytes added ,  22:38, 30 January 2013
Line 194: Line 194:  
==== 2.10 ====
 
==== 2.10 ====
 
* aircraft packages should be prepared prior to the official release date: "For the 2.8 release I didn't start making aircraft download packages (or uploading them to the ftp servers) until after the official release date which was a mistake" [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg39227.html]
 
* aircraft packages should be prepared prior to the official release date: "For the 2.8 release I didn't start making aircraft download packages (or uploading them to the ftp servers) until after the official release date which was a mistake" [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg39227.html]
 +
* RC's should probably be built with [[Built-in Profiler]] support enabled [http://flightgear.org/forums/viewtopic.php?f=68&t=18839&p=175689#p175689].
 
* {{Thumbs up}} Walking through the list of "lessons learned" as part of the "Upcoming release" announcement was useful [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg38749.html]
 
* {{Thumbs up}} Walking through the list of "lessons learned" as part of the "Upcoming release" announcement was useful [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg38749.html]
 
* {{Thumbs up}} Posting the link to the changelog for the upcoming release helped writing the changelog early, this should also be done for the [[Hardware Recommendations]] and [[Notebooks known to run FlightGear]] pages probably?
 
* {{Thumbs up}} Posting the link to the changelog for the upcoming release helped writing the changelog early, this should also be done for the [[Hardware Recommendations]] and [[Notebooks known to run FlightGear]] pages probably?

Navigation menu