Release plan: Difference between revisions

Line 162: Line 162:


==== 2.8 ====
==== 2.8 ====
* [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg38113.html Broken OSX downloads]
* {{Thumbs up}} [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg38113.html Broken OSX downloads]
* [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg38089.html The changelog should be written as early as possible]
* {{Thumbs up}} [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg38089.html The changelog should be written as early as possible]
* A number of users reported severe memory growth issues (with fgfs consuming as much as 14gb of RAM), many directly related to new features, such as random buildings:[http://flightgear.org/forums/viewtopic.php?f=17&t=17249] [http://flightgear.org/forums/viewtopic.php?f=68&t=17114&start=15#p163829] [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg38007.html]
* {{Thumbs up}} A number of users reported severe memory growth issues (with fgfs consuming as much as 14gb of RAM), many directly related to new features, such as random buildings:[http://flightgear.org/forums/viewtopic.php?f=17&t=17249] [http://flightgear.org/forums/viewtopic.php?f=68&t=17114&start=15#p163829] [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg38007.html]
* Several users with old graphics cards reported not being able to run FG 2.8 without crashing during startup, because the FG defaults didn't scale for old hardware [http://flightgear.org/forums/viewtopic.php?f=17&t=17308]
* {{Thumbs up}} Several users with old graphics cards reported not being able to run FG 2.8 without crashing during startup, because the FG defaults didn't scale for old hardware [http://flightgear.org/forums/viewtopic.php?f=17&t=17308]


This is a list of lessons learned from the previous releases, things that turned out well and should be kept for the next release as well as thing thad didn't turn out so well and should be changed for future releases.
This is a list of lessons learned from the previous releases, things that turned out well and should be kept for the next release as well as thing thad didn't turn out so well and should be changed for future releases.