Torsten wrote > > during this year's LinuxTag, Martin Spott, Mathias Fröhlich, Thorsten > Brehm > and myself developed a strategy and a concept about how to kick out new > releases of FlightGear on a regular schedule. > > Please find our first draft here: http://wiki.flightgear.org/Release_Plan > > For the impatient reader, this is the abstract: > We plan to have two releases per year, one in February, one in August. The > first scheduled release following this concept will be 2.4.0 in August > this > year, 2.6.0 is scheduled for February 2012. > > If no major objections arise, we will set the version number on the > current > development stream to 2.3.0 and will call out a "feature freeze" on June > 17th. > > Any comment and certainly any help for actually preparing the release is > welcome. >
It's as good a plan as any other. However we missed the last planned release (2.2.0). I'm unaware of the reason(s), but I assume that release is dead. So I think the question we have to ask is not "when" but "how". Until that is solved, the "when" is pretty meaningless. Nevertheless, having a plan at all is a good start. Vivian ------------------------------------------------------------------------------ What Every C/C++ and Fortran developer Should Know! Read this article and learn how Intel has extended the reach of its next-generation tools to help Windows* and Linux* C/C++ and Fortran developers boost performance applications - including clusters. http://p.sf.net/sfu/intel-dev2devmay _______________________________________________ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
