At my current workplace there are some projects that when preparing a release will
- backup the current RELEASE branch by making a branch from it with the current date (this isnt technically required, so this is optional. It does happen more often but its not 100% of the time)
- delete the current RELEASE branch
- take the latest DEV branch (DEV is the same as master, where developer topic/feature branches are PR/CI'd into) and make a new RELEASE branch from it
- build the artifacts for release from the RELEASE branch
The release branch is short lived as it is deleted after a branch is made from it as a copy. It ceases to exist. At some point in time later, the DEV branch is branched into a branch called RELEASE, but this is a new release branch. Call it a rename if you think thats what it always equates to, but the topic was not about if it was a rename or not.
Are there any well known (and explained) branching and releasing strategies that fit this kind of pattern? I havent been able to locate any that are close, but perhaps I'm not searching for them correctly.