Collaboration Workflow

Objectives

• stable master branch so developers can always have a good starting point
• code review so that code is understandable and of high quality
• someone other than original developer verifying test plan passes
• as simple a a process as could possibly work (with the understanding that it can be made more complicated as needed)

Prior Drafts

• initial diagram, more complicated than current draft, with stable master but named release branch for a dedicated testing phase:

References

• http://scottchacon.com/2011/08/31/github-flow.html
• https://github.com/blog/1557-github-flow-in-the-browser
• http://nvie.com/posts/a-successful-git-branching-model/
• Version Control with Git