We just turned into the final approach to our release 2.4.0! I have just created the branches release/2.4.0 for fgdata, simgear and flightgear and created tags version/2.4.0 and version/2.5.0 for the commits containing the version changes.
The master branch of fgdata and the next branches of simgear and flightgear are now open for all the fancy new features that have evolved over the last four weeks. Thank you all for your patience and your help to create a stable code base for the next version! What's next? Please commit your new features into the 'next' branches of flightgear/simgear and 'master' of fgdata. If you fix a bug, please check if this applies for 2.4.0, 2.5.0 or both and commit to the corresponding branch. Fixes for both version should be commited to to 'next' and cherry-picked into the release/2.4.0 branch. ** _PLEASE_DO_NOT_MERGE 'next' into 'release/2.4.0' or vice versa! ** (Read the previous line again) James will train Jenkins to create binaries from the new branch (release-candidates) Curt and Tat will create Windows and Mac packages (release-candidates) Everybody is requested to test the release candidates and report defects to our bugtracker at http://code.google.com/p/flightgear-bugs/issues/list Thanks, Torsten ------------------------------------------------------------------------------ AppSumo Presents a FREE Video for the SourceForge Community by Eric Ries, the creator of the Lean Startup Methodology on "Lean Startup Secrets Revealed." This video shows you how to validate your ideas, optimize your ideas and identify your business strategy. http://p.sf.net/sfu/appsumosfdev2dev _______________________________________________ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
