Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update release notes for 1.82.0 to include the tier 2 status for the wasm32-wasip2 target #129997

Open
alexcrichton opened this issue Sep 5, 2024 · 0 comments
Labels
I-release-nominated Nominated for the release team. relnotes Marks issues that should be documented in the release notes of the next release. T-release Relevant to the release subteam, which will review and decide on the PR/issue.
Milestone

Comments

@alexcrichton
Copy link
Member

The Rust 1.81.0 release notes originally had a note that the wasm32-wasip2 target was moved to tier 2. This was because #126967 made it into Rust 1.81 and claims that wasm32-wasip2 is tier 2. Alas there was a bug in that PR which ended up being fixed in #127867 which did not make Rust 1.81. This means that Rust 1.81 did not actually include tier 2 status for wasm32-wasip2 in the sense that you could rustup target add the target.

The blog post release notes have been updated to no longer mention this feature of 1.81 and the release notes on the master branch additionally have been updated as well.

In talking with @pietroalbini he recommended I open an issue to track the release notes for 1.82 and I'm told there are mythical and mysterious labels he'll apply to track everything accordingly. I'll also be here to help answer questions if any arise too!

@rustbot rustbot added the needs-triage This issue may need triage. Remove it if it has been sufficiently triaged. label Sep 5, 2024
@pietroalbini pietroalbini added T-release Relevant to the release subteam, which will review and decide on the PR/issue. relnotes Marks issues that should be documented in the release notes of the next release. I-release-nominated Nominated for the release team. and removed needs-triage This issue may need triage. Remove it if it has been sufficiently triaged. labels Sep 5, 2024
@Mark-Simulacrum Mark-Simulacrum added this to the 1.82.0 milestone Sep 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
I-release-nominated Nominated for the release team. relnotes Marks issues that should be documented in the release notes of the next release. T-release Relevant to the release subteam, which will review and decide on the PR/issue.
Projects
None yet
Development

No branches or pull requests

4 participants