...
Most changes to named releases should also be represented on the master branches. When a change is needed in a named release, the standard process it to make the change to master first, and then port the change back to the named release (hence the term backport).
When opening a PR to a named release branch, tag for review the Release Manager from Build-Test-Release Working Group, which can be determine from the working group’s README. Although not required, getting an first PR review from one of your team members will show the Release Manager that someone else’s eyes have already been on your PR, which makes their job easier.
The exact mechanics of backporting depend on whether you’re merging to a:
...