All,

I'm rather new to github, so I was wondering what a good branching
strategy would be?  Right now, I cut a branch every time there's a new
release, so that I can keep working features on master, and then
emergency bug fixes on the cut branch.

However, this assumes a fixed release schedule.  Sometimes, it seems
like we want to push features/bug fixes out midweek.  My current
branching strategy fills up branch names, and makes it difficult to
deploy between release schedules.

I was told an alternative branching strategy would be to use one
branch called 'edge', and merge or cherry pick commits from edge to
master, and then deploy to production off of master.  Then tag every
deploy to production w/ its version number.

What is a known good branching strategies?  Thanks.

Wilhelm

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"GitHub" group.
To post to this group, send email to github@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/github?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to