fork/rust

git clone https://git.julia.blue/fork/rust

borsAuto merge of #69854 - pietroalbini:stable-next, r=Centrilb8cedc00407

1.42.0
2.0 KiB42 linesraw
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.
4#
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
8# release.
9#
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.0` for Cargo where they were released on `date`.
14
15date: 2020-02-27
16rustc: 1.41.1
17cargo: 0.42.0
18
19# We use a nightly rustfmt to format the source because it solves some bootstrapping
20# issues with use of new syntax in this repo. If you're looking at the beta/stable branch, this key should be omitted,
21# as we don't want to depend on rustfmt from nightly there.
22#rustfmt: nightly-2019-12-18
23
24# When making a stable release the process currently looks like:
25#
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
30#
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.
36#
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
40# out.
41
42#dev: 1