Create release branch
Having master lag behind beta is a problem. Create a branch just for releases instead, so when we want to make a release, we merge onto the release branch. Or we could have a branch per release. Whatever works.
- Create a new branch "release" (or not).
- Move all current CI/CD jobs on master to release (or just disable them for now).
- Move all current CI/CD jobs on beta to master.
- Fix all places in build.sh and update-version.py etc that reference beta branch to reference master branch (keep beta in names).
- Merge beta into master.
- Remove the beta branch.
- Fix protection etc on master.
An alternative to a release branch could be one branch per release that is automatically created when we tag a release on master. Then CI/CD on that branch could actually build an publish the release.
