A successful Git branching model(nvie.com)
nvie.com
A successful Git branching model
http://nvie.com/posts/a-successful-git-branching-model#
3 comments
Github found git-flow wasn't suitable given that they do CI and developed their own method of using git, Github Flow:
http://scottchacon.com/2011/08/31/github-flow.html
A different article on a CI-based approach, with comparison to git-flow: http://nxvl.blogspot.com/2012/07/a-continous-delivery-git-br...
A different article on a CI-based approach, with comparison to git-flow: http://nxvl.blogspot.com/2012/07/a-continous-delivery-git-br...
This is an older article from 2010. The author later created the git extension named git-flow based on this model - https://github.com/nvie/gitflow
I've been asked many times by units (big corporation) if this would be a good branching model for them when they are migrating to Git. I always tell them it's probably too complicated for their situation. Most of the units are trying to implement some form of Continuous Integration. Obfuscating that with complex branching models would only confuse them. Only when they encounter a real problem, that could be solved with this branching model, I suggest they try this out. I haven't still seen it happen.
However I must say, that the situation might be different in different types of projects. I've seen only these kind of CI-projects with a couple of hundreds developers with long lead times.