Release plan: Difference between revisions

Release plan (view source)

148 bytes added , 19 February 2013

20,741

edits

@@ Line 211: / Line 211: @@
 ** {{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)?
-** for the web-based release announcement, it would be helpful to have screen shots or even youtube videos to demonstrate new features
+** 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].
+** 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]
 ** 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]