Release Branching
This is a proposal on how to manage tagged releases, and patches to same.
A "release" is defined by a tag of a checkout package that follows the CMT tag/version convention.
We distinguish patches to existing releases (which are, confusingly, also releases) with an appended "p",
e.g. if v7r4p1 would be a patch to release v7r4.
Such a patch release will actually be a tag of a branch of the checkout package, which starts with the base release.
Procedure following a MAIN branch tag
- Apply the tag, e.g. v7r4
- Create a branch tag as well, e.g. GRv7r4
- Create such branch tag to all the included packages.