The current scap release process (as described in https://gerrit.wikimedia.org/r/plugins/gitiles/mediawiki/tools/scap/+/master/RELEASE.md) has some issues:
- It requires performing a merge from 'master' into an infrequently-updated 'release' branch. This step is very likely to require manual conflict resolution which is error-prone (e.g, resulting in problems like that identified in T277782).
- It recommends pushing to Gerrit in a way that does not generate reviewable patchsets. When trying to investigate these commits in the future, they do not show up in the Gerrit UI which can be confusing.
- Get rid of the 'release' branch. Instead, tag a commit in the master branch and supply that tag to SRE when we ask them to build the package. No merging required. Just a point-in-time reference to what we want to be packaged.
- Revise all steps that suggest pushing to Gerrit without generating patchsets. If there are problems with going through the normal Gerrit/CI workflows then we need to fix them.