The Rust Release Process

Here’s how Rust is currently released:

Update books (T-6 days, Friday)

From within the repo:

$ cd src/doc/book
$ git fetch origin
$ git reset --hard origin/master
$ cd ../rust-by-example
$ git fetch origin
$ git reset --hard origin/master
$ cd ../reference
$ git fetch origin
$ git reset --hard origin/master
$ cd ../nomicon
$ git fetch origin
$ git reset --hard origin/master
$ cd ../../..
$ git add .
$ git commit -m "update books for next release"

This can be done a day earlier too, if you’d like: the books are only tested fully once they’re in this repo, and so updating them may cause tests to fail. If they do, you need to send in a PR to the right book, ping @steveklabnik to get a quick merge, and then update that particular book again to fix it. This should be relatively rare.

Promote beta to stable (T-3 days, Monday)

Promote beta to stable. Temporarily turn off GitHub branch protection for the stable branch in rust-lang/rust repo. In your local Rust repo:

$ git fetch rust-lang
$ git push rust-lang rust-lang/beta:stable -f

Re-enable branch protection for the stable branch. Send a PR to rust-lang/rust on the stable branch making the following changes:

Once the PR is sent, r+ it and give it a high p=1000.

The stable build will not deploy automatically to prod. The rust-central-station repository is configured to upload to dev every hour if it detects a change. You should be able to browse changes in dev.

As soon as this build is done post a message to irlo asking for testing. The index is and our URL is then

Test rustup with

RUSTUP_DIST_SERVER= rustup update stable

Promote master to beta (T-2 days, Tuesday)

Branch a rust-lang/cargo commit for the new beta:

$ cd cargo
$ git fetch rust-lang
$ git push rust-lang rust-lang/master:rust-1.14.0

You’ll need to temporarily disable branch protection on GitHub to push the new branch. Make sure the commit in the new branch is the latest one on rust-lang/rust, and not an earlier one.

In theory one day we’ll do the same for rust-lang/rls, but for now we haven’t done this yet.

Temporarily disable banch protection on GitHub for the beta branch of the Rust repo. Promote rust-lang/rust’s master branch to beta as with yesterday:

$ git fetch rust-lang
$ git push rust-lang rust-lang/master:beta -f

Re-enable branch protection on GitHub. Send a PR to the freshly created beta branch of rust-lang/rust which:

Note that you probably don’t want to update the RLS if it’s working, but if it’s not working beta won’t land and it’ll need to get updated. After this PR merges (through @bors) the beta should be automatically released.

Master bootstrap update (T-1 day, Wednesday)

Write a new blog post, update rust-www, and update rust-forge. Submit PRs for tomorrow.

Send a PR to the master branch to:

In theory update the RLS submodule as well, but it’s pretty susceptible to breakage so I’d probably avoid that for now.

Release day (Thursday)

Decide on a time to do the release, T.

Bask in your success.

Update dependencies (T+1 day, Friday)

In the repo:

$ cd src
$ cargo update

The very ambitious can use and update through breaking changes.