20,741
edits
Release plan: Difference between revisions
Jump to navigation
Jump to search
→2.10
(→2.10) |
(→2.10) |
||
| Line 225: | Line 225: | ||
** according to Windows users, the installer created by jenkins could use some optimizations [http://flightgear.org/forums/viewtopic.php?f=18&t=19745] | ** according to Windows users, the installer created by jenkins could use some optimizations [http://flightgear.org/forums/viewtopic.php?f=18&t=19745] | ||
** a number of Windows7/Windows8 users reported issues that needed a "force 32/64 bit" workaround during startup [http://flightgear.org/forums/viewtopic.php?f=17&p=182923#p182923][http://flightgear.org/forums/viewtopic.php?f=17&t=19872&p=182759&hilit=#p182759][http://flightgear.org/forums/viewtopic.php?f=22&t=19869&p=182724&hilit=#p182724] | ** a number of Windows7/Windows8 users reported issues that needed a "force 32/64 bit" workaround during startup [http://flightgear.org/forums/viewtopic.php?f=17&p=182923#p182923][http://flightgear.org/forums/viewtopic.php?f=17&t=19872&p=182759&hilit=#p182759][http://flightgear.org/forums/viewtopic.php?f=22&t=19869&p=182724&hilit=#p182724] | ||
** new GUI widgets, new fgcommands and new Nasal APIs should ideally be documented prior the release, at least through updated README files, preferably also through the wiki | ** {{Improve Release Plan|new GUI widgets, new fgcommands and new Nasal APIs should ideally be documented prior the release, at least through updated README files, preferably also through the wiki}} | ||
| Line 242: | Line 242: | ||
* '''Changelog / Release Announcement''': | * '''Changelog / Release Announcement''': | ||
** {{Thumbs up}} Walking through the list of "lessons learned" as part of the "Upcoming release" announcement was useful [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg38749.html] | ** {{Thumbs up}} Walking through the list of "lessons learned" as part of the "Upcoming release" announcement was useful [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg38749.html] | ||
** Probably it would be even better to directly process all "lessons learned" items and improve the release plan after each release accordingly | ** {{Improve Release Plan|Probably it would be even better to directly process all "lessons learned" items and improve the release plan after each release accordingly}} | ||
** To get to the 3.0 goal sometime in the near future, it's probably a good idea to [[FlightGear 3.0 backlog|create a backlog of open items in the wiki and link the release plan document to that]]. As usual, we don't have to be perfect for a new major release number. But the new features being the reason for the new major number should work reasonably correct. [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg38888.html] (also see [[:Category:Developer Plans]]) | ** To get to the 3.0 goal sometime in the near future, it's probably a good idea to [[FlightGear 3.0 backlog|create a backlog of open items in the wiki and link the release plan document to that]]. As usual, we don't have to be perfect for a new major release number. But the new features being the reason for the new major number should work reasonably correct. [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg38888.html] (also see [[:Category:Developer Plans]]) | ||
** {{Thumbs up}} Posting the link to the changelog for the upcoming release helped writing the changelog early, this should also be done for the [[Hardware Recommendations]] and [[Notebooks known to run FlightGear]] pages probably? | ** {{Thumbs up}} Posting the link to the changelog for the upcoming release helped writing the changelog early, this should also be done for the [[Hardware Recommendations]] and [[Notebooks known to run FlightGear]] pages probably? | ||
** {{Thumbs up}} The changelog can be easily written by using "git log", searching the issue tracker and by going through the last 6 newsletters published since the previous release. It might make sense to explicitly add a "ChangeLog" message to important commits, so that the Changelog can be compiled more easily ? | ** {{Thumbs up}} The changelog can be easily written by using "git log", searching the issue tracker and by going through the last 6 newsletters published since the previous release. It might make sense to explicitly add a "ChangeLog" message to important commits, so that the Changelog can be compiled more easily ? | ||
** Alternatively, request developers to add major changes also to $FG_SRC/ChangeLog again (last updated in 2001)? | ** Alternatively, request developers to add major changes also to $FG_SRC/ChangeLog again (last updated in 2001)? | ||
** for the web-based release announcement, it would be helpful to have screen shots or even youtube videos to demonstrate new features - get the community involved EARLY | ** {{Improve Release Plan|for the web-based release announcement, it would be helpful to have screen shots or even youtube videos to demonstrate new features - get the community involved EARLY}} | ||
** it may make sense to also allow artwork contributors to contribute new splash screen images for use in the upcoming release. The screen shot contest should provide plenty of options [http://www.flightgear.org/forums/viewtopic.php?f=28&t=16795]. | ** {{Improve Release Plan|it may make sense to also allow artwork contributors to contribute new splash screen images for use in the upcoming release. The screen shot contest should provide plenty of options}} [http://www.flightgear.org/forums/viewtopic.php?f=28&t=16795]. | ||
** a screenshot/banner contest should be held early on, so that we can use the images for our promo work-NOT after the release [http://flightgear.org/forums/viewtopic.php?f=19&t=19220] | ** {{Improve Release Plan|a screenshot/banner contest should be held early on, so that we can use the images for our promo work-NOT after the release}} [http://flightgear.org/forums/viewtopic.php?f=19&t=19220] | ||
** for the changelog we should early on invite volunteers to help translate it, useful for the release promotion | ** {{Improve Release Plan|for the changelog we should early on invite volunteers to help translate it, useful for the release promotion}} | ||
** having dedicated promo videos sounds like a good idea, see [http://flightgear.org/forums/viewtopic.php?f=19&t=19158] [[Howto:Creating FlightGear Promo Videos]] | ** {{Improve Release Plan|having dedicated promo videos sounds like a good idea}}, see [http://flightgear.org/forums/viewtopic.php?f=19&t=19158] [[Howto:Creating FlightGear Promo Videos]] | ||
** The RC announcement should also contain links to 1) the issue tracker and 2) the RC subforum [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg39222.html] | ** The RC announcement should also contain links to 1) the issue tracker and 2) the RC subforum [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg39222.html] | ||
** Using wiki tagging, we could ensure that we can also tag our wiki documentation after each release, so that we can provide older versions of our docs for old FG versions [http://flightgear.org/forums/viewtopic.php?f=3&t=18240&p=170735&hilit=wiki+tagging#p170735] | ** Using wiki tagging, we could ensure that we can also tag our wiki documentation after each release, so that we can provide older versions of our docs for old FG versions [http://flightgear.org/forums/viewtopic.php?f=3&t=18240&p=170735&hilit=wiki+tagging#p170735] | ||