Rust 1.18 release status


#1

The 1.18 release is scheduled for 6/8. That is a little over two weeks from now.

And the state of the release is super not good.

Here are the outstanding bugs: https://github.com/rust-lang/rust/issues?q=is%3Aopen+is%3Aissue+label%3Aregression-from-stable-to-beta

There are 10 of them.

And cargobomb against 1.18.0-beta.2: http://cargobomb-reports.s3-website-us-west-1.amazonaws.com/beta-2017-05-12/index.html

The vast majority of regressions are these three:

These all are thought to have fixes, but not landed.

We can’t release in this state, so please if you have the ability and capacity to tackle these problems, do so.

cc @compiler_subteam @core_team


#2

This PR intends to backport some fixes: https://github.com/rust-lang/rust/pull/42053


#3

Oh there are a bunch of nominated backports too: https://github.com/rust-lang/rust/pulls?q=is%3Apr+label%3Abeta-nominated+is%3Aclosed

Those with the ability to accept them should have a look.


#4

I did a couple of backports, and bumped the beta: https://github.com/rust-lang/rust/pull/42161


#5

As of now there’s one more beta patch in the queue, and that looks like it’ll be the last:

https://github.com/rust-lang/rust/pull/42197

Here are the remaining known beta regressions:

This one won’t be resolved for beta but is minor:

https://github.com/rust-lang/rust/issues/42019

There are two mingw-related regressions that came out of the LLVM upgrade and won’t be reverted.

There’s a PR to bump the prerelease version and get out a new beta. Then we’ll run that through cargobomb.

Seems like we’re doing ok. Thanks all.


#6

I think https://github.com/rust-lang/rust/issues/41270 is sorted by landing a doc-fix (though, imo the fix is … exculpatory more than it is helpful). So that one should be all good to go.