Tracking Issue for promoting aarch64-pc-windows-msvc to a Tier 1 target
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 119k
- Forks
- 16.1k
- PR merge metrics
- PR metrics pending
Description
This is a tracking issue for the RFC "Tier 1 aarch64-pc-windows-msvc" (rust-lang/rfcs#3817).
About tracking issues
Tracking issues are used to record the overall progress of implementation.
They are also used as hubs connecting to other relevant issues, e.g., bugs or open design questions.
A tracking issue is however not meant for large scale discussion, questions, or bug reports about a feature.
Instead, open a dedicated issue for the specific matter and add the relevant feature gate label.
Discussion comments will get marked as off-topic or deleted.
Repeated discussions on the tracking issue may lead to the tracking issue getting locked.
Steps
- Adjust the target documentation https://github.com/rust-lang/rust/pull/145682
-
Ensure an entry in the release blog postEDIT: seems like relnotes is sufficient
Implementation history
- Add tests to rust-lang/rust CI: https://github.com/rust-lang/rust/pull/140136
- Add tests to Cargo CI: https://github.com/rust-lang/cargo/pull/15790
- Adjust documentation https://github.com/rust-lang/rust/pull/145682
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Review RFC 3817 and the tracking checklist first. Start with the target documentation change in rust-lang/rust#145682, using the existing Rust CI and Cargo CI pull requests as context. Done means the documentation step is completed and the checklist accurately reflects the target's promotion progress.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- build-system, ci-cd, operating-systems
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100