20,741
edits
Release plan: Difference between revisions
Jump to navigation
Jump to search
m
→2.10
m (→2.10: http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg40179.html) |
m (→2.10) |
||
| Line 226: | Line 226: | ||
* '''Better bug reports and troubleshooting''': | * '''Better bug reports and troubleshooting''': | ||
** 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 | ** 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 the CMAKE_BUILD_TYPE variable used during compilation, for use in the about dialog (debug, release, RelWithDbgInfo) | ** add a property specifying the CMAKE_BUILD_TYPE variable used during compilation, for use in the about dialog (debug, release, RelWithDbgInfo) | ||
** show the threading mode in use in the about dialog | ** show the threading mode in use in the about dialog | ||
** show average frame rate and frame spacing in about dialog | ** show average frame rate and frame spacing in about dialog | ||
** add a property specifying how much physical RAM is detected | ** add a property specifying how much physical RAM is detected (to see if people are running out of RAM) [http://flightgear.org/forums/viewtopic.php?f=5&t=16083&p=164936&hilit=swapping#p164936] | ||
** is there a portable ARB/WGL extension to determine the amount of dedicated VRAM available ? | ** is there a portable ARB/WGL extension to determine the amount of dedicated VRAM available ? | ||
** try to detect Intel GPUs and Mesa drivers ? (some of the more common issues were related to Intel/Mesa) | ** try to detect Intel GPUs and Mesa drivers ? (some of the more common issues were related to Intel/Mesa) | ||
| Line 300: | Line 300: | ||
** a number of users reported crashes, for better debugging support, consider linking in Google BreakPad (cross platform stack traces) [http://flightgear.org/forums/viewtopic.php?f=68&t=18942&p=176669#p176669] | ** a number of users reported crashes, for better debugging support, consider linking in Google BreakPad (cross platform stack traces) [http://flightgear.org/forums/viewtopic.php?f=68&t=18942&p=176669#p176669] | ||
** Release Candidates should probably have a higher default logging level while writing everything to a log file that can be easily shared via the issue tracker/forums, so that end users can provide better bug reports. | ** Release Candidates should probably have a higher default logging level while writing everything to a log file that can be easily shared via the issue tracker/forums, so that end users can provide better bug reports. | ||
** some users reported "OpenGL out of memory" and "out of space" errors when testing the RCs, we may want to link in a leak detector library or simply add BoehmGC - which is used by Mozilla to track leaking subsystems (a runtime log is created and dumped at process termination), that way non-developers could provide better leak reports. | ** some users reported "OpenGL out of memory" and "out of space" errors when testing the RCs, we may want to link in a leak detector library or simply add BoehmGC - which is used by Mozilla to track leaking subsystems (a runtime log is created and dumped at process termination), that way non-developers could provide better leak reports. [http://flightgear.org/forums/viewtopic.php?f=68&t=17114&] [http://www.flightgear.org/forums/viewtopic.php?f=68&t=17114#p163132] [http://flightgear.org/forums/viewtopic.php?f=37&p=171427#p171329] | ||
** How about having a test run a week or two in advance, just to make sure we can indeed produce release installers for Win+Mac - and then release the first RC on December 17th/18th or 19th [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg38765.html] | ** How about having a test run a week or two in advance, just to make sure we can indeed produce release installers for Win+Mac - and then release the first RC on December 17th/18th or 19th [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg38765.html] | ||
** We've already got a fairly extensive lead-in time for the release. More testers on more platforms would seem to be the answer. Perhaps we should advertize for testers of those platforms that aren't adequately covered by developers running git? Making a complete package available, not just the binaries would help, as testers wouldn't need to be git-aware. [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg38764.html] | ** We've already got a fairly extensive lead-in time for the release. More testers on more platforms would seem to be the answer. Perhaps we should advertize for testers of those platforms that aren't adequately covered by developers running git? Making a complete package available, not just the binaries would help, as testers wouldn't need to be git-aware. [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg38764.html] | ||