2013/11/26 Gary Gregory <garydgreg...@gmail.com> > On Tue, Nov 26, 2013 at 3:52 AM, Emmanuel Bourg <ebo...@apache.org> wrote: > > > 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. > > > > I agree with Emmanuel. Let's keep it simple by not mixing a change in VCS > and process at the same time. Let's do Git and see how that goes. >
What's the point of using git then? > > Gary > > > > Emmanuel Bourg > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > > For additional commands, e-mail: dev-h...@commons.apache.org > > > > > > > -- > E-Mail: garydgreg...@gmail.com | ggreg...@apache.org > Java Persistence with Hibernate, Second Edition< > http://www.manning.com/bauer3/> > JUnit in Action, Second Edition <http://www.manning.com/tahchiev/> > Spring Batch in Action <http://www.manning.com/templier/> > Blog: http://garygregory.wordpress.com > Home: http://garygregory.com/ > Tweet! http://twitter.com/GaryGregory > -- http://people.apache.org/~britter/ http://www.systemoutprintln.de/ http://twitter.com/BenediktRitter http://github.com/britter
