...
Who: Only integrators can create tags of these branches. Users should never tag their development permanent (master, maint) branches.
What: ACME will not tag every single merge into the ACME master. ACME will use tags on master to mark significant development steps, and may coincide with versions where the Coupled Model and/or Performance teams devote significant resources to evaluate climate or code performance.
...
Archival Tag Names on Feature branches
Who: Only integrators can create tags. Users should never can tag their development branches.
What: Tags can also be used to archive versions of the code. This is the case where
...
(See /wiki/spaces/SE/pages/4718815 for discussion that articulated this use case.
Archival branches are similar to maintenance branches in that we want to keep them around to run again or to look through code modifications. However, maintenance branches are code releases that we actively maintain, which archival branches are not that formal will not be kept current.
Naming:
archive/<UserName>/<description>
Note that once a commit has been tagged, it will be preserved even if the branch it's on gets deleted. We recommend that unused branches be deleted and we can rely on the tag to keep these commits alive. Branch clutter is a more serious problem than tag clutter.