You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi,
So I noticed it in nightly 2018-04-12 but I'm sure this apply to other nightlys.
I install toolchain rustup override set nightly-2018-04-12-x86_64-unknown-linux-gnu
But the rustc version is different rustc 1.27.0-nightly (ad610bed8 2018-04-11).
On the IRC people told me the reason is because the CI starts deployment at 11:00PM and it doesn't end until after the next day starts, this seems solvable pretty easy.
Don't you think it's better to have a consistent release date?
The text was updated successfully, but these errors were encountered:
Note that the date in (ad610bed8 2018-04-11) is not a version, it's the timestamp of the last commit (from the last merged PR) before the nightly, i.e. ad610be. If no PRs get merged, it doesn't change.
Hi,
So I noticed it in nightly
2018-04-12
but I'm sure this apply to other nightlys.I install toolchain
rustup override set nightly-2018-04-12-x86_64-unknown-linux-gnu
But the rustc version is different
rustc 1.27.0-nightly (ad610bed8 2018-04-11)
.On the IRC people told me the reason is because the CI starts deployment at 11:00PM and it doesn't end until after the next day starts, this seems solvable pretty easy.
Don't you think it's better to have a consistent release date?
The text was updated successfully, but these errors were encountered: