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