Hi Erwin,

Finding the right branching/deployment model in Git is pretty much up to 
your imagination :)

However, if you're not the creative type, there's a de-facto "best practice" 
model here: http://nvie.com/posts/a-successful-git-branching-model/

Maybe you'll find this model inspiring. Note that he uses "master" as his 
production branch though (but it's all just naming). The way he does release 
branching and tagging is the interesting part for you, I think.

-- 
You received this message because you are subscribed to the Google Groups "Git 
for human beings" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/git-users/-/ww35P_8APlwJ.
To post to this group, send email to git-users@googlegroups.com.
To unsubscribe from this group, send email to 
git-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/git-users?hl=en.

Reply via email to