I did a thorough update of the predictions, bumped lots of stuff, added lots of stuff.
AFAIK all of the changes required for XZ compression have landed. Is there a release schedule for rustup?
Bumped RLS to 1.20
@ranma42 Oh awesome. The release schedule is just whenever I circle back to it. I will try to get a build out soon.
Moved “Macro use and re-export” to horizon, as this comment indicates that the change is postponed until Macros 2.0 are readier as a whole.
I also bumped android host builds, up-to-date reference, cargo 1.0, and AVR to horizon.
I also bumped incremental to horizon.
When are “slice_patterns” going to be stable?
@leonardo I don’t see any indication on the tracker that they are approaching stability, but there is still activity. I did at it to ‘horizon’ since it is at least still moving. If you are motivated you might harass people there to get it moving.
Well, it’s already time again that we start preparing release notes for 1.19. @XAMPPRocky are you interested in doing it again? I know it was a bit of a slog last time…
We also need to reevaluate the predictions. I think after doing a thorough review of the predictions I want to post some kind of “What’s coming up in Rust” update to urlo, and in it give recommendations about how people can help move their favorite features forward. Sometimes it just takes someone to pester the right people to get a feature moving.
Yes I am. I actually enjoyed doing it!
I’ve done up a preliminary version.
I updated the op to move 1.18 to “past”, and linked in the 1.19 relnotes.
I did a pass over everything and updated them. I’m losing motivation to continue doing so and I encourage others to add items to the op as they become aware of their status.
The PR linked for Android host builds has been merged. Does it belong to a specific release now?
Since it’s not yet the 31st, I believe that makes 1.21 the expected version for it to land in.
Can an estimate for stablizing https://github.com/rust-lang/rust/pull/43574 be made?
If I understand the process correctly, everything in nightly is always expected to make it into the next beta release, and from there to the next stable release after that.
That is the process, but the trickle-down doesn’t start until it’s marked
#[stable] in nightly.
(i.e. it will currently make its way to release as
#[unstable], effectively internal-only.)
Update on the reference stuff – I’ve been stopped entirely for months, because whatever side project time I’ve had has gone 100% into either the podcast or trying to get TypeScript off the ground in the Ember.js ecosystem. And I’m teetering on the edge of burnout at times. So I don’t know when that will be finished by me. People should not see me as a blocker to it; I intend to post publicly that others can take it on (and would welcome someone on the docs team shepherding it through).