Release plan: Difference between revisions

Release plan (view source)

698 bytes added , 14 August 2013

m

→‎August 2013: copy/paste from newsletter

20,741

edits

@@ Line 202: / Line 202: @@
 This is a list of lessons learned from the previous releases, things that turned out well and should be kept for the next release as well as thing that didn't turn out so well and should be changed for future releases. Ideally, the release plan should be updated and augmented so that the lessons learned are incorporated accordingly.
-==== August 2013 ====
+==== 2.12 ====
+'''Release postponed''':
+Due to real life constraints and the low number of active core developers, we've hit a fluctuation where pretty much everyone is occupied with
+something else at the moment. As everybody seems to be caught in some real life trouble, we can't see a better way to get the release out than delaying it for a while.
+Also, it seems that it will take longer than usual to address any issues found in the RCs. Thus, we have agreed to postpone the upcoming FlightGear 2.12 release by a month, to provide sufficient time to handle release candidates and process end-user feedback. <ref>http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg40568.html</ref>
+<references/>
 '''RCs:'''
 * we should try to get out release candidates earlier to give testers a chance to actually run the RCs [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg40522.html]