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
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).
Copy file name to clipboardExpand all lines: src/release/process.md
+5-3Lines changed: 5 additions & 3 deletions
Original file line number
Diff line number
Diff line change
@@ -8,8 +8,10 @@ Promote beta to stable. Temporarily turn off GitHub branch protection for the
8
8
`stable` branch in rust-lang/rust repo. In your local Rust repo:
9
9
10
10
```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
13
15
```
14
16
15
17
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.
148
150
`cargo publish` for the tag you just created. You'll first need to comment
149
151
out `cargo-test-macro` from Cargo.toml, then publish `crates-io` (in
150
152
`crates/crates-io`) and finally publish `cargo` itself.
151
-
153
+
152
154
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.
153
155
154
156
-**T+1hr** Send a PR to the beta branch to comment out `dev: 1` again and
0 commit comments