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

Tracking issue for release notes of #137951: Blog post entry for i586-pc-windows-msvc removal #137952

Open
rustbot opened this issue Mar 3, 2025 · 2 comments
Labels
release-blog-post Marks issues tracking what text to put in the release blog post. relnotes Marks issues that should be documented in the release notes of the next release. relnotes-tracking-issue Marks issues tracking what text to put in release notes.
Milestone

Comments

@rustbot
Copy link
Collaborator

rustbot commented Mar 3, 2025

This issue tracks the release notes text for #137951.

cc @Noratrieb -- original issue/PR authors and assignees for drafting text

See the forge.rust-lang.org chapter about release notes for an overview of how the release team makes use of these tracking issues.

Release notes text

This section should be edited to specify the correct category(s) for the change, with succinct description(s) of what changed. Some things worth considering:

  • Does this need an additional compat notes section?
  • Was this a libs stabilization that should have additional headers to list new APIs under Stabilized APIs and Const Stabilized APIs?
nothing: REMOVE THIS!!

Tip

Use the previous releases for inspiration on how to write the release notes text and which categories to pick.

Release blog section

If this change is notable enough for inclusion in the blog post then this section should be edited to contain a draft for the blog post. Otherwise leave it empty.

## Target deprecation warning for 1.87.0

The target `i586-pc-windows-msvc` will be removed in the next version of Rust, 1.87.0.
This is because this target is effectively useless.
Its difference to the much more popular `i686-pc-windows-msvc` is that it does not require SSE2 instruction support, but Windows 10,
the minimum required OS version of all `windows` targets (except the `win7` targets), requires SSE2 instructions itself, so this target does not fulfill a purpose.
You can check the [Major Change Proposal](https://github.com/rust-lang/compiler-team/issues/840) for more information.

Note

If a blog post section is required the release-blog-post label should be added (@rustbot label +release-blog-post) to this issue as otherwise it may be missed by the release team.

@rustbot rustbot added relnotes Marks issues that should be documented in the release notes of the next release. relnotes-tracking-issue Marks issues tracking what text to put in release notes. needs-triage This issue may need triage. Remove it if it has been sufficiently triaged. labels Mar 3, 2025
@rustbot rustbot added this to the 1.86.0 milestone Mar 3, 2025
@Noratrieb Noratrieb removed the needs-triage This issue may need triage. Remove it if it has been sufficiently triaged. label Mar 3, 2025
@BoxyUwU BoxyUwU added the release-blog-post Marks issues tracking what text to put in the release blog post. label Mar 3, 2025
@Mark-Simulacrum
Copy link
Member

I think we can probably have the compat notes section too? Just noting something is coming, but seems reasonable to include in both places.

@programmerjake
Copy link
Member

the title should be i586, not i686

@wesleywiser wesleywiser changed the title Tracking issue for release notes of #137951: Blog post entry for i686-pc-windows-msvc removal Tracking issue for release notes of #137951: Blog post entry for i586-pc-windows-msvc removal Mar 4, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
release-blog-post Marks issues tracking what text to put in the release blog post. relnotes Marks issues that should be documented in the release notes of the next release. relnotes-tracking-issue Marks issues tracking what text to put in release notes.
Projects
None yet
Development

No branches or pull requests

5 participants