From: Hamza A. <ham...@li...> - 2015-07-28 13:06:21
|
________________________________ > From: to...@t3... > Date: Mon, 27 Jul 2015 20:07:24 +0000 > To: fli...@li... > Subject: [Flightgear-devel] Next is 3.7.0, release/3.6.0 is alive > > Hi all, > > I have just created release/3.6.0 branches for > - fgmeta > - fgrun > - simgear > - flightgear > - fgdata > > and increased the version number to 3.7.0 for those, except fgmeta > (doesn't have a version file) > > and also created the release-3.6.0 branch on fgaddon. > > You may now hack new features in the next branch while the release > branches should only receive bug fixes. Make sure to backport those by > cherry-picking into next. > Avoid merges unless you know _exactly_ what you are doing! > Please read the previous sentence again :-) > > James, could you introduce the new branches to the Jenkins release > build configs? > > Torsten > > ------------------------------------------------------------------------------ > _______________________________________________ Flightgear-devel > mailing list Fli...@li... > https://lists.sourceforge.net/lists/listinfo/flightgear-devel Hi Torsten, Congrats on reaching the release/3.6.0 milestone! for FGMETA, it might be appropriate to change the stable version from release/3.4.0 to release/3.6.0, for users of the "-s" switch to the d&c script. pull request proposed, Thank you Have a good day Hamza |