After tests starts for the the release branch (jewel, hammer etc.), no backport should be merged to it because the release process can only run on the tip of the branch. To workaround that limitation and keep merging backports while the tests happen (which may last from one week to three weeks), the backports are merged into the release-next branch instead (i.e. jewel-next, hammer-next etc.).
- For all pull request targeting the frozen branch, using the web interface, edit the label and using the menu to switch from release to release-next (i.e. jewel to jewel-next etc.)
- After the release is published, rebase release-next on top of release and push release-next to release. The rebase should only be necessary in case a backported was needed after the freeze (which can happen if testing reveals a problem).