Branching and Tagging

Jump to bottom Edit New page

dchandekstark edited this page Nov 6, 2014 · 4 revisions

See also: Versioning-Practices.

Branching

We generally follow the model described at http://nvie.com/posts/a-successful-git-branching-model/. In particular, this means:

develop is the current development branch
master is the current production branch

Tagging

Production releases must be tagged.
Pre- and post-releases should not normally be tagged.
Release candidates should be tagged.