Call for Testing - broadening the reach?
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 7k
- Forks
- 1.1k
- Avg merge
- 22h 40m
- Merged PRs (30d)
- 46
Description
Hello, Rustup team,
We noticed you posted a Call for Testing for rustup a week ago. If you would like to broaden the reach of that CfT, please put a call-for-testing label here: https://github.com/rust-lang/rustup/labels/call-for-testing.
We'll pick it up, add it to the current issue of This Week in Rust and will let you know we've done so.
Thanks, as always for your hard work!
-TWiR Editors
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
Start at the call-for-testing label page linked in the issue and identify the current rustup Call for Testing issue. Apply the label if appropriate, then confirm the change to the This Week in Rust editors; the issue is done when the relevant call is labeled and confirmation is sent.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- release
- Issue type
- Feature
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100