Skip to content

Commit 16d0f84

Browse files
Add note to backport release notes
We've historically forgotten to do this a few times, so let's include it in the documentation so that we don't forget in the future. This also adjusts the remote we use to `origin` as that's what I have locally (and is more common than rust-lang I suspect, given that it is the git default).
1 parent 952dd86 commit 16d0f84

File tree

1 file changed

+5
-3
lines changed

1 file changed

+5
-3
lines changed

src/release/process.md

Lines changed: 5 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -8,8 +8,10 @@ Promote beta to stable. Temporarily turn off GitHub branch protection for the
88
`stable` branch in rust-lang/rust repo. In your local Rust repo:
99

1010
```sh
11-
$ git fetch rust-lang
12-
$ git push rust-lang rust-lang/beta:stable -f
11+
$ git fetch origin
12+
$ git push origin origin/beta:stable -f
13+
# make sure that the release notes file is as fresh as possible
14+
$ git checkout origin/master -- RELEASES.md
1315
```
1416

1517
Re-enable branch protection for the `stable` branch. Send a PR to rust-lang/rust
@@ -148,7 +150,7 @@ Decide on a time to do the release, T.
148150
`cargo publish` for the tag you just created. You'll first need to comment
149151
out `cargo-test-macro` from Cargo.toml, then publish `crates-io` (in
150152
`crates/crates-io`) and finally publish `cargo` itself.
151-
153+
152154
To publish Cargo you may have to bump the version numbers for the crates-io and Cargo crates; there's no need to do that in a formal commit though, so your tag and the published code may differentiate in that way.
153155

154156
- **T+1hr** Send a PR to the beta branch to comment out `dev: 1` again and

0 commit comments

Comments
 (0)