...
- Assignment of the PR should be for the person that created the PR
- Set the labels to the appropriate ones
- Set the milestone to the next major release (e.g. 10.0.0)
- Set the project to the current release if you would like to have it backported (e.g. 9.0.x)
- Create another separate PR for each earlier release branch (e.g. 7.1.x or 8.0.x)
- Reviews should be done by so
- When merging a commit make sure there is only 1 commit (squash and merge if necessary).
- Commit messages should follow the standard formatting described on the CommitPolicies page.
- If the PR has documentation add a comment with: [approve ci docs]
Cherry-Pick (only for release managers)
...