Git branch strategy for small dev team

Posted by Bilal Aslam on Stack Overflow See other posts from Stack Overflow or by Bilal Aslam
Published on 2010-03-11T21:13:15Z Indexed on 2010/03/11 21:39 UTC
Read the original article Hit count: 284

Filed under:
|
|

We have a web app that we update and release almost daily. We use git as our VCS, and our current branching strategy is very simple and broken: we have a master branch and we check changes that we 'feel good about' into it. This works, but only until we check in a breaking change.

Does anyone have a favorite git branch strategy for small teams which meets the following requirements:

  1. Works well for teams of 2 to 3 developers
  2. Lightweight, and not too much process
  3. Allows devs to isolate work on bug fixes and larger features with ease
  4. Allows us to keep a stable branch (for those 'oh crap' moments when we have to get our production servers working)

Ideally, I'd love to see your step-by-step process for a dev working on a new bug

© Stack Overflow or respective owner

Related posts about git

Related posts about git-branching