Le 26/11/2013 08:43, Benedikt Ritter a écrit : > I propose [1] as branching model. It looks very complicated at first, but > I've found it very useful to always have a release ready version of the > code in master. > > [1] http://nvie.com/posts/a-successful-git-branching-model/
It looks complicated indeed. I prefer having the current developments on the master branch and create topic branches to experiment with more involved changes. I don't think we have enough active developers per component to require a more sophisticated model. Emmanuel Bourg --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
