Change Details

I'm not sure if this was intentional. In other projects one typically keeps release branches to tag new releases from, and then at some point the release is EOL and the branch can be removed (except for `master`). These clobber the branch views in different places and are just annoying to deal with in CI. It'd be a lot easier and saner to work with if they aren't open to changes (technically) and would also enforce our social policies at a technical level. Anything in these branches (all non-LTS, non-legacy branches: REL1_1 - REL1_18, REL1_20 - REL1_22) that is not released in a tag will never be released. And if for some extraordinary circumstances we decide to do another release, the branch is trivially re-created using the last tag from any release cycle.