Git Branching Strategy

From Gcube Wiki
Revision as of 01:52, 25 May 2019 by Manuele.simi (Talk | contribs)

Jump to: navigation, search
  • The master branch is the stable branch. Must be always in a releasable state.
  • Feature (named feature/issue) branches are created from master (issue is the tracker issue number that describes the feature).
  • Occasionally, feature branches can be created from other feature branches, although this is a discouraged practice.
  • Features may be experimental. If not pursued, branches are discarded without corrupting the stability of the master branch.
  • When a feature is complete, the corresponding feature branch is merged into the master branch.
  • When master has enough stable features, it is released
  • If an issue (typically a bug requiring immediate attention) in master is detected, a hotfix/issue branch is created from master (issue is the tracker issue number that reports the problem)
  • Once the hotfix is complete it is merged to master and any open feature branch (if needed)

Git Branching strategy.v5.png

Back to the CI guide.