20,741
edits
Release plan: Difference between revisions
Jump to navigation
Jump to search
→2.10
(→2.10) |
(→2.10) |
||
| Line 240: | Line 240: | ||
** 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]. | ** 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]. | ||
** When releasing RC's do not limit them to Win/Mac binaries, but also create source snapshots so that distros can already work on the next package versions. | ** When releasing RC's do not limit them to Win/Mac binaries, but also create source snapshots so that distros can already work on the next package versions. | ||
** For RC's it might make sense to distribute binaries with debugging symbols included, so that people can more easily provide useful bug reports, or even backtraces. | ** For RC's it might make sense to distribute binaries with debugging symbols included and [[Built-in Profiler|profiling support enabled]], so that people can more easily provide useful bug reports, or even backtraces. | ||
** Also, many end users still prefer using the forum for making bug reports and don't use the issue tracker - it might help to add a link (button) to the issue tracker to the about dialog or maybe even directly to the help menu ("Report an issue") (same for wiki/troubleshooting/faq ?) | ** Also, many end users still prefer using the forum for making bug reports and don't use the issue tracker - it might help to add a link (button) to the issue tracker to the about dialog or maybe even directly to the help menu ("Report an issue") (same for wiki/troubleshooting/faq ?) | ||
** it might make sense to give wider exposure to our RCs, i.e. via the newsletter - possibly by adjusting the release schedule | ** it might make sense to give wider exposure to our RCs, i.e. via the newsletter - possibly by adjusting the release schedule | ||