You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: src/release/backporting.md
+9-7Lines changed: 9 additions & 7 deletions
Original file line number
Diff line number
Diff line change
@@ -27,18 +27,20 @@ Getting a PR backported to the beta branch involves the following process:
27
27
4. Open a PR **against the beta branch** with a title that starts with `[beta]` (so reviewers can see its specialness).
28
28
5. List all of the PRs being backported in the PR description.
29
29
[Here's an example](https://github.com/rust-lang/rust/pull/64097).
30
+
6. Go through all of the PRs being backported and:
31
+
32
+
* Change the milestone to the correct value for the beta release.
33
+
* Remove the `beta-nominated` label.
34
+
This indicates that the backport has been completed.
35
+
36
+
If there are a lot of PRs, this can be done quickly by opening the [nominated + accepted][nominated-plus-accepted] query, check all the PRs being backported, and use the "Milestones" and "Label" drop-downs to modify multiple PRs in bulk.
37
+
38
+
This last step can be done before or after the beta PR has been merged, though it can be easy to forget if you wait for it to be merged.
30
39
31
40
4. A reviewer (typically from the release team) needs to verify that the backport looks correct and that it's submitted to the beta branch.
32
41
They will then approve with `@bors r+ rollup=never` (to avoid it being rolled up on accident).
33
42
If the author of the PR has r+ rights, and has not made significant changes while backporting, they can also self-approve the PR.
34
43
35
-
5. Go through all of the PRs being backported and:
36
-
37
-
* Change the milestone to the correct value for the beta release.
38
-
* Remove the `beta-nominated` label.
39
-
This indicates that the backport has been completed.
40
-
41
-
If there are a lot of PRs, this can be done quickly by opening the [nominated + accepted][nominated-plus-accepted] query, check all the PRs being backported, and use the "Milestones" and "Label" drop-downs to modify multiple PRs in bulk.
42
44
43
45
In summary, there are three states that a PR can go through:
0 commit comments