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

Windows support schedule 2024 #651

Closed
1 of 3 tasks
ChrisDenton opened this issue Jul 8, 2023 · 10 comments
Closed
1 of 3 tasks

Windows support schedule 2024 #651

ChrisDenton opened this issue Jul 8, 2023 · 10 comments
Labels
major-change A proposal to make a major change to rustc major-change-accepted A major change proposal that was accepted T-compiler Add this label so rfcbot knows to poll the compiler team

Comments

@ChrisDenton
Copy link

ChrisDenton commented Jul 8, 2023

Currently Windows 7 and 8 are listed as Tier 1 supported platforms. However, this has not been true for a long long time. We simply do not have the testing infrastructure. And with so much software now abandoning Windows 7 and 8 (everything from Git to Go to every major browser), continuing to provide the little support that we do is only getting more difficult. There is also a lack of vendor support for these targets.

This proposal aims to raise the minimum supported Windows version of current targets to Windows 10 (first released in 2015) during 2024. But it also leaves open the door for new targets that can commit to broader support, By having a separate target we can ensure there are people specifically tasked with supporting legacy versions of Windows.

Proposal

Rust 1.75 will be the last to officially support Windows 7, 8 and 8.1. Support for Windows versions before 10 will end in February 2024 with Rust 1.76.

Support for Windows 7 and 8 may continue beyond these dates through the creation of new "legacy" targets for older Windows versions. Individuals or organisation(s) who can commit to providing some level of legacy testing and support should go through the normal process for creating new targets.

Process

The main points of the Major Change Process are as follows:

  • File an issue describing the proposal.
  • A compiler team member or contributor who is knowledgeable in the area can second by writing @rustbot second.
    • Finding a "second" suffices for internal changes. If however, you are proposing a new public-facing feature, such as a -C flag, then full team check-off is required.
    • Compiler team members can initiate a check-off via @rfcbot fcp merge on either the MCP or the PR.
  • Once an MCP is seconded, the Final Comment Period begins. If no objections are raised after 10 days, the MCP is considered approved.

You can read more about Major Change Proposals on forge.

Comments

This issue is not meant to be used for technical discussion. There is a Zulip stream for that. Use this issue to leave procedural comments, such as volunteering to review, indicating that you second the proposal (or third, etc), or raising a concern that you would like to be addressed.

@ChrisDenton ChrisDenton added major-change A proposal to make a major change to rustc T-compiler Add this label so rfcbot knows to poll the compiler team labels Jul 8, 2023
@rustbot
Copy link
Collaborator

rustbot commented Jul 8, 2023

This issue is not meant to be used for technical discussion. There is a Zulip stream for that. Use this issue to leave procedural comments, such as volunteering to review, indicating that you second the proposal (or third, etc), or raising a concern that you would like to be addressed.

cc @rust-lang/compiler @rust-lang/compiler-contributors

@rustbot rustbot added the to-announce Announce this issue on triage meeting label Jul 8, 2023
@kennykerr
Copy link

For what it's worth, this is good news for Rust.

@wesleywiser
Copy link
Member

@rustbot second

@apiraino
Copy link
Contributor

@rustbot label -final-comment-period +major-change-accepted

@rustbot rustbot added major-change-accepted A major change proposal that was accepted to-announce Announce this issue on triage meeting and removed final-comment-period The FCP has started, most (if not all) team members are in agreement labels Aug 10, 2023
@apiraino apiraino removed the to-announce Announce this issue on triage meeting label Aug 10, 2023
@enp6
Copy link

enp6 commented Aug 25, 2023

I didn't understand why Windows 7 and 8 are not supported, only heard that X86 is not supported...

@workingjubilee
Copy link
Contributor

32-bit x86 Windows is supported as a tier 1 platform for Rust.

It is simple, and already stated in Chris Denton's post: We do not have access to test environments for Windows 7 anymore. This is because the OS images we would use for our test suite for Windows 7 have effectively disappeared, along with Microsoft's official support for those images. So we are not testing it. We are testing on Windows 10. As we are not testing Windows 7, we are not giving it tier 1 support, which is defined as passing our test suite for every merge.

If you want working software, then you should probably want us to actually say what Windows version we support.

@zhuxiujia
Copy link

zhuxiujia commented Feb 4, 2024

The existing devices have a lot of in Win7 and Win8,As far as I know, Windows server devices based on Win7 and Win8 are even larger。

If Rust 1.76 no longer supports Win7, there may be a large number of people staying at version 1.75,。
Perhaps Rust will lose more people 。
who are more willing to write C++code, at least for better compatibility

@the8472
Copy link
Member

the8472 commented Feb 4, 2024

This issue is not meant to be used for technical discussion. There is a Zulip stream for that. Use this issue to leave procedural comments, such as volunteering to review, indicating that you second the proposal (or third, etc), or raising a concern that you would like to be addressed.

☝️

@han1548772930
Copy link

It would be very bad if Rust lost users of Windows 7 and 8

@RalfJung
Copy link
Member

RalfJung commented Feb 4, 2024

Cc rust-lang/rust#118150 since it is relevant for this thread: there are tier 3 targets for Windows 7. It remains supported, but as a "best effort, not tested" target rather than a tier 1 "fully supported" target.

@rust-lang rust-lang locked as resolved and limited conversation to collaborators Feb 4, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
major-change A proposal to make a major change to rustc major-change-accepted A major change proposal that was accepted T-compiler Add this label so rfcbot knows to poll the compiler team
Projects
None yet
Development

No branches or pull requests