...
douglasjacobsen/clm/4.5.72
Archival Tag Names on Feature branches
Who: Users can tag their development branches.
What: Tags can be used to archive versions of the code. This is the case where
- exploratory runs were made (for climate or performance)
- where speculative code development was performed, not merged into master, but needs to be retained
(See /wiki/spaces/SE/pages/4718815 for discussion that articulated this use case.
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.
Permanent Branch Names: master, next, maint-x.y
...
Every circle represents a commit of some code.
Archival Tag Names on Feature branches
...
...
...
- exploratory runs were made (for climate or performance)
- where speculative code development was performed, not merged into master, but needs to be retained
(See /wiki/spaces/SE/pages/4718815 for discussion that articulated this use case.
Naming:
archive/<UserName>/<description>
...