Create new default branch

Projects with releases can profit from following the "Git flow" model more closely. In this model, continuous development happens on a development branch, e.g., branch dev, which is protected and set as the default branch. The master branch (also protected) is only used for new releases. When a new release is desired, intermittent changes from the development branch are pushed onto the master branch for the new release. If one desires to cherry-pick commits for a new release (e.g., to wait with commits that would break the API and therefore require a major version bump, see semantic versioning), it is also possible to add another layer with having protected release branches. But for our purpose that probably goes too far, at least for now.

Here is a schematic representation of the "Git flow" model: Git flow

To do

  • set feature freeze when nearing completion of milestone %v0.1.0 release
  • create branch dev off branch master
  • protect branch dev and set as default branch
Edited by Alex Kanitz