1 # This file describes the stage0 compiler that's used to then bootstrap the Rust
2 # compiler itself. For the rustbuild build system, this also describes the
3 # relevant Cargo revision that we're using.
5 # Currently Rust always bootstraps from the previous stable release, and in our
6 # train model this means that the master branch bootstraps from beta, beta
7 # bootstraps from current stable, and stable bootstraps from the previous stable
10 # If you're looking at this file on the master branch, you'll likely see that
11 # rustc and cargo are configured to `beta`, whereas if you're looking at a
12 # source tarball for a stable release you'll likely see `1.x.0` for rustc and
13 # `0.(x+1).0` for Cargo where they were released on `date`.
19 # We use a nightly rustfmt to format the source because it solves some
20 # bootstrapping issues with use of new syntax in this repo. If you're looking at
21 # the beta/stable branch, this key should be omitted, as we don't want to depend
22 # on rustfmt from nightly there.
23 rustfmt: nightly-2020-07-12
25 # When making a stable release the process currently looks like:
27 # 1. Produce stable build, upload it to dev-static
28 # 2. Produce a beta build from the previous stable build, upload to static
29 # 3. Produce a nightly build from previous beta, upload to static
30 # 4. Upload stable build to static, publish full release
32 # This means that there's a small window of time (a few days) where artifacts
33 # are downloaded from dev-static.rust-lang.org instead of static.rust-lang.org.
34 # In order to ease this transition we have an extra key which is in the
35 # configuration file below. When uncommented this will instruct the bootstrap.py
36 # script to download from dev-static.rust-lang.org.
38 # This key is typically commented out at all times. If you're looking at a
39 # stable release tarball it should *definitely* be commented out. If you're
40 # looking at a beta source tarball and it's uncommented we'll shortly comment it