Hi Justin, I'm not saying nothing against nvie (I give the same link in several emails here), we use that model at work and we already do things like the ones I describe.
Yo can make whatever experimental things you want and work with other people in *feature* branches but in the end main flows are dictated by nvie model...so when you master, develop, release, hotfixes and features are integrated in that nvie model. 2013/3/12 Justin Mclean <jus...@classsoftware.com> > Hi, > > > Now that we are at few hours to fully work on GIT, I'm sure you will love > > it. For example, you could work with Mike much better making your own > > branches and taking control over your commits and what you want to share > in > > the remote repository. The problems you both face the previous week where > > one can step changes over the other are gone thanks to branching feature. > > You only have to take patience to master this feature and you will see > that > > is very powerful and get lots of control. In SVN the main problem is that > > all happens in one single place since branches are not usable and this > > causes that kind problems while working with other people. > > Just a reminder that we voted on using the gitflow model. [1] This is not > quite the free for all model you describe above and at same point you still > have to merge everything into the develop branch. > > Justin > > 1. http://nvie.com/posts/a-successful-git-branching-model/ > > -- Carlos Rovira Director de Tecnología M: +34 607 22 60 05 F: +34 912 94 80 80 http://www.codeoscopic.com http://www.directwriter.es http://www.avant2.es
