New upstream version 1.53.0+dfsg1

[rustc.git] / src / stage0.txt

diff --git a/src/stage0.txt b/src/stage0.txt
index 34fbc4eacd6e45b991216fbe311e7941887c1b0f..231e66719d00a35f4566f9ca600166499c529af7 100644 (file)
--- a/src/stage0.txt
+++ b/src/stage0.txt
@@ -1,6 +1,5 @@
 # This file describes the stage0 compiler that's used to then bootstrap the Rust
-# compiler itself. For the rustbuild build system, this also describes the
-# relevant Cargo revision that we're using.
+# compiler itself.
 #
 # Currently Rust always bootstraps from the previous stable release, and in our
 # train model this means that the master branch bootstraps from beta, beta
@@ -8,13 +7,19 @@
 # release.
 #
 # If you're looking at this file on the master branch, you'll likely see that
-# rustc and cargo are configured to `beta`, whereas if you're looking at a
-# source tarball for a stable release you'll likely see `1.x.0` for rustc and
-# `0.x.0` for Cargo where they were released on `date`.
+# rustc is configured to `beta`, whereas if you're looking at a source tarball
+# for a stable release you'll likely see `1.x.0` for rustc, with the previous
+# stable release's version number. `date` is the date where the release we're
+# bootstrapping off was released.
 
-date: 2019-11-07
-rustc: 1.39.0
-cargo: 0.40.0
+date: 2021-05-06
+rustc: 1.52.0
+
+# We use a nightly rustfmt to format the source because it solves some
+# bootstrapping issues with use of new syntax in this repo. If you're looking at
+# the beta/stable branch, this key should be omitted, as we don't want to depend
+# on rustfmt from nightly there.
+#rustfmt: nightly-2021-03-25
 
 # When making a stable release the process currently looks like:
 #