Release plan: Difference between revisions

Line 257: Line 257:
** 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
** actually, it would even seem better to use our [[Release promotion]] checklist to send out an "Upcoming Release" announcement 4-6 weeks prior to the actual release, so that all the flightsim websites can notify their users to participate in RC beta testing.
** a number of forum users reported that the RC/release mirrors were a real bottleneck, and that downloading the 800MB RC installer would often take 2-3 hours (using torrents instead was suggested)
** so reducing the size of the installer (i.e. base package) would seem like another good idea to give our RCs wider exposure, for example by focusing only on 2-3 aircraft


* '''Build related''':
* '''Build related''':