We are presumably following the `git-flow` release process, of loosely. That
process specifies that there is a branch which is the latest main (not
supporting) release. If you want to call is `release` then fine. A rose by any
other name, and all that. But having that reference is useful for the
@Robert, would you care to elaborate on the case for keeping a branch (by any
name) that this discussion thread overwhelmingly felt:
* "isn’t really in use for anything vital"
* "always a source of confusion"
* "don't see the need for it"
* "no good reason to keep it"
* "always a little unclear...
