update the doc in toolchain.toml describing the update plan (#10453)

The *toolchain.toml* doc incorrectly stated how many releases behind
stable we will be...

It said we would be 1 release behind when actually we want to be 2
releases behind stable.
This commit is contained in:
Michael Angerman 2023-09-20 20:34:25 -07:00 committed by GitHub
parent 7cfd4d2cfa
commit addf8ca942
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23

View File

@ -9,8 +9,8 @@
# The default profile includes rustc, rust-std, cargo, rust-docs, rustfmt and clippy. # The default profile includes rustc, rust-std, cargo, rust-docs, rustfmt and clippy.
# https://rust-lang.github.io/rustup/concepts/profiles.html # https://rust-lang.github.io/rustup/concepts/profiles.html
profile = "default" profile = "default"
# The current plan is to be 1 release behind the latest stable release. So, if the # The current plan is to be 2 releases behind the latest stable release. So, if the
# latest stable release is 1.62.0, the channel should be 1.61.0. We want to do this # latest stable release is 1.72.0, the channel should be 1.70.0. We want to do this
# so that we give repo maintainers and package managers a chance to update to a more # so that we give repo maintainers and package managers a chance to update to a more
# recent version of rust. However, if there is a "cool new feature" that we want to # recent version of rust. However, if there is a "cool new feature" that we want to
# use in nushell, we may opt to use the bleeding edge stable version of rust. # use in nushell, we may opt to use the bleeding edge stable version of rust.