Here's how Rust is currently released:
Open a PR bumping the version number in
r+ rollup=never this
Mark it as
rollup=never, because if it lands in a rollup as not the first
PR then other pull requests in that rollup will be incorrectly associated with
the prior release.
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 origin $ git push origin origin/beta:stable -f # make sure that the release notes file is as fresh as possible $ git checkout origin/master -- RELEASES.md
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
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 https://dev-static-rust-lang-org.s3.amazonaws.com/dist/2015-09-17/index.html and our URL is then https://dev-static.rust-lang.org/dist/2015-09-17/index.html.
Test rustup with
RUSTUP_DIST_SERVER=https://dev-static.rust-lang.org rustup update stable
If something goes wrong, and we rebuild stable artifacts, you'll need to invalidate the dev-static bucket for RCS to re-release it.
- Obtain AWS credentials (i.e.,
- Run the
- (optional) login to central station, and run the following. This starts the dev-static promotion immediately, vs. waiting till the next hour.
docker exec -d -it rcs bash -c 'promote-release /tmp/stable stable /data/secrets-dev.toml 2>&1 | logger --tag release-stable'
We need to find out the parent commit in which the PR opened last Monday merged.
Go to that PR, and find the "bors merged commit $SHA into rust-lang:master at the bottom.
export BRANCH_POINT=`git rev-parse $SHA^` in the rust-lang/rust
checkout. This should be bors-authored merge into master of the PR before the
version bump merged.
Create a new branch on
rust-lang/cargo for the new beta. Here,
the remote for https://github.com/rust-lang/rust.git. Replace
YY with the
minor version of master. First determine the branch point for cargo in
rust-lang/rust, and then create a new branch:
$ cd rust $ git fetch rust-lang $ CARGO_SHA=`git rev-parse $BRANCH_POINT:src/tools/cargo` $ cd src/tools/cargo $ git branch rust-1.YY.0 $CARGO_SHA $ git push origin rust-1.YY.0
You'll need to temporarily disable branch protection on GitHub to push the new branch.
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 $BRANCH_POINT:beta -f
Re-enable branch protection on GitHub. Send a PR to the freshly created beta branch of rust-lang/rust which:
- Update src/stage0.txt
dateto "YYYY-MM-DD" where the date is the archive date the stable build was uploaded
rustcto "X.Y.Z" where that's the version of rustc you just build
cargoto "A.B.C" where it's Cargo's version. That's typically "0.(Y+1).0" wrt the rustc version.
- Update src/ci/run.sh to pass "--release-channel=beta".
Send a PR to the master branch to:
- modify src/stage0.txt to bootstrap from yesterday's beta
Decide on a time to do the release, T.
T-30m - This is on rust-central-station:
docker exec -d -it rcs bash -c 'promote-release /tmp/stable stable /data/secrets.toml 2>&1 | logger --tag release-stable-realz'
That'll, in the background, schedule the
promote-releasebinary to run on the production secrets (not the dev secrets). That'll sign everything, upload it, update the html index pages, and invalidate the CDN. Note that this takes about 30 minutes right now. Logs are in
T-10m - Locally, tag the new release and upload it. Use "x.y.z release" as the commit message.
$ git tag -u FA1BE5FE 1.3.0 $COMMIT_SHA $ git push rust-lang 1.3.0
After this Update thanks.rust-lang.org by triggering a build on Travis.
T-5m - Merge blog post.
T - Tweet and post everything!
T+5m - Tag Cargo the same way as rust-lang/rust and then run
cargo publishfor the tag you just created. You'll first need to comment out
cargo-test-macrofrom Cargo.toml, then publish
crates/crates-io) and finally publish
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.
T+1hr Send a PR to the beta branch to comment out
dev: 1again and update the date to download from (modifying
Bask in your success.
Sometimes a PR requires testing how it behaves when downloaded from rustup, for example after a manifest change. In those cases it's possible to publish a new nightly based off that PR on dev-static.rust-lang.org.
Once the try build finishes make sure the merge commit for your PR is at the
top of the
try branch, log into the rust-central-station server
and run this command:
docker exec -d -it rcs bash -c 'PROMOTE_RELEASE_OVERRIDE_BRANCH=try promote-release /tmp/nightly-tmp nightly /data/secrets-dev.toml 2>&1 | logger --tag release-nightly-tmp'
try branch doesn't contain the merge commit (because a new build
started in the meantime) you can create a new branch pointing to the merge
commit and run (replacing
BRANCH_NAME with the name of the branch):
docker exec -d -it rcs bash -c 'PROMOTE_RELEASE_OVERRIDE_BRANCH=BRANCH_NAME promote-release /tmp/nightly-tmp nightly /data/secrets-dev.toml 2>&1 | logger --tag release-nightly-tmp'
You can follow the build progress with:
sudo tail -n 1000 -f /var/log/syslog | grep release-nightly-tmp
Once the build ends it's possible to install the new nightly with:
RUSTUP_DIST_SERVER=https://dev-static.rust-lang.org rustup toolchain install nightly