June 2025 program management update #1668
Conversation
|
I'd like this to merge after #1667 is published so I can link it from here. cc @ojeda: If you have time to check the Rust for Linux section, I'd be really grateful. I want to make sure it's not misrepresenting anything. cc @walterhpearce: same for the |
Co-authored-by: Miguel Ojeda <ojeda@users.noreply.github.com>
|
@ojeda thank you for your suggestion! I've added more context to Rust for Linux so I'd appreciate one more look if you don't mind. Tried to explain why we're doing this too. I also want to do a similar things for the crates.io verification/mirroring |
|
|
||
| There's been an ongoing collaboration with the Rust Project to get the language, compiler and tooling to a point where it can be completely compiled on stable Rust. | ||
|
|
||
| [This was one of the Flagship goals in the first half of 2025][rflh1]. |
There was a problem hiding this comment.
Since you mention this, I would suggest also mentioning it was a flagship goal in 2024H2 too (i.e. since the beginning of the goals), since it reinforces the notion that it has been an important goal of upstream Rust: https://rust-lang.github.io/rust-project-goals/2024h2/rfl_stable.html
There was a problem hiding this comment.
The latest update should have that covered, thanks for the suggestion!
Co-authored-by: Miguel Ojeda <ojeda@users.noreply.github.com>
Co-authored-by: Miguel Ojeda <ojeda@users.noreply.github.com>
Co-authored-by: Miguel Ojeda <ojeda@users.noreply.github.com>
|
@joshtriplett I'm significantly reworked the crates.io signing & verification section here. I'd appreciate if you or @walterhpearce could check it's all accurate. |
|
Lgtm. It's all factually accurate and covers the state of things. |
Rendered