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/ 2013/11/24 Benedikt Ritter <brit...@apache.org> > Let's give it a try. No objections from my side. > > > 2013/11/24 Emmanuel Bourg <ebo...@apache.org> > >> What about experimenting the migration to Git with cli? >> >> Emmanuel Bourg >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org >> For additional commands, e-mail: dev-h...@commons.apache.org >> >> > > > -- > http://people.apache.org/~britter/ > http://www.systemoutprintln.de/ > http://twitter.com/BenediktRitter > http://github.com/britter > -- http://people.apache.org/~britter/ http://www.systemoutprintln.de/ http://twitter.com/BenediktRitter http://github.com/britter
