fork/rust
git clone https://git.julia.blue/fork/rust
f3e1a954d2e
1.41.1
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: 2019-12-19 16rustc: 1.40.0 17cargo: 0.41.0 18 19# When making a stable release the process currently looks like: 20# 21# 1. Produce stable build, upload it to dev-static 22# 2. Produce a beta build from the previous stable build, upload to static 23# 3. Produce a nightly build from previous beta, upload to static 24# 4. Upload stable build to static, publish full release 25# 26# This means that there's a small window of time (a few days) where artifacts 27# are downloaded from dev-static.rust-lang.org instead of static.rust-lang.org. 28# In order to ease this transition we have an extra key which is in the 29# configuration file below. When uncommented this will instruct the bootstrap.py 30# script to download from dev-static.rust-lang.org. 31# 32# This key is typically commented out at all times. If you're looking at a 33# stable release tarball it should *definitely* be commented out. If you're 34# looking at a beta source tarball and it's uncommented we'll shortly comment it 35# out. 36 37#dev: 1