Le 29 juil. 2014 à 20:21, Erich Titl <erich.t...@think.ch> a écrit :
> Hi Yves > > at 29.07.2014 18:17, Yves Blusseau wrote: >> Hi all, >> >> i think you are misusing the next branch. >> The next branch is not use to be the next branch for the next release. As >> the git workflow guide said (http://goo.gl/BOzkap) the next branch is >> intended as a testing branch for topics being tested for stability for >> master. >> So the next branch is used to test topic/features branch for the next >> release. > > Why not just commit new stuff to master and branch away every major > release instead? Is that against some GIT convention? It's our convention (that is in our git workflow guide). It's not good to commit directly to master for big changes that can add a regression. The master branch must be stable. So to add new features, fork a topic branch from master (or maint, …) and develop in it. Then to test merge your branch into next to see if it work with all other topic branches. The next branch is an unstable branch (like pu branch). Regards, Yves ------------------------------------------------------------------------------ Infragistics Professional Build stunning WinForms apps today! Reboot your WinForms applications with our WinForms controls. Build a bridge from your legacy apps to the future. http://pubads.g.doubleclick.net/gampad/clk?id=153845071&iu=/4140/ostg.clktrk _______________________________________________ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
