Release plan: Difference between revisions

Line 229: Line 229:


* '''Better bug reports and troubleshooting''':
* '''Better bug reports and troubleshooting''':
** show HLA/OpenRTI availability {{done}} [https://gitorious.org/fg/flightgear/commit/c61583de5daddaa901ff52562645fac3f04dd225]
** show HLA/OpenRTI availability {{fixed since|release=2.11+}} [https://gitorious.org/fg/flightgear/commit/c61583de5daddaa901ff52562645fac3f04dd225]
** add a string property with list of startup arguments used by the user, for use in the about dialog
** add a string property with list of startup arguments used by the user, for use in the about dialog
** add a property specifying if the binary is 32/64 bit for use in the about dialog (to check if segfaults are related to 32bit RAM limits)
** add a property specifying if the binary is 32/64 bit for use in the about dialog (to check if segfaults are related to 32bit RAM limits)
Line 276: Line 276:


* '''FGData related (Base Package)''':
* '''FGData related (Base Package)''':
** accessibility of README files in $FG_ROOT/Docs should be improved for our Win/Mac users [http://flightgear.org/forums/viewtopic.php?f=72&t=19725] {{done}} (by Stuart)
** accessibility of README files in $FG_ROOT/Docs should be improved for our Win/Mac users [http://flightgear.org/forums/viewtopic.php?f=72&t=19725] {{fixed since|release=2.11+}} (by Stuart)
** aircraft included in the base package should not require DDS support [http://flightgear.org/forums/viewtopic.php?f=4&t=11863&p=183549#p183549]
** aircraft included in the base package should not require DDS support [http://flightgear.org/forums/viewtopic.php?f=4&t=11863&p=183549#p183549]
** a bunch of Intel GPU related issues were tracked down to be related to texture dimensions beyond 512x512 not being supported, suggested workarounds are mentioned at [http://code.google.com/p/flightgear-bugs/issues/detail?id=1100#c2]
** a bunch of Intel GPU related issues were tracked down to be related to texture dimensions beyond 512x512 not being supported, suggested workarounds are mentioned at [http://code.google.com/p/flightgear-bugs/issues/detail?id=1100#c2]