Skip to content

Commit 3c94949

Browse files
committed
Update RFC, MCP, FCP and CFT sections for TWiR-594
1 parent c867ff9 commit 3c94949

File tree

1 file changed

+8
-19
lines changed

1 file changed

+8
-19
lines changed

draft/2025-04-09-this-week-in-rust.md

Lines changed: 8 additions & 19 deletions
Original file line numberDiff line numberDiff line change
@@ -54,29 +54,18 @@ and just ask the editors to select the category.
5454
[submit_crate]: https://users.rust-lang.org/t/crate-of-the-week/2704
5555

5656
## Calls for Testing
57-
5857
An important step for RFC implementation is for people to experiment with the
59-
implementation and give feedback, especially before stabilization. The following
60-
RFCs would benefit from user testing before moving forward:
61-
62-
<!-- Calls for Testing go here, use this format:
63-
* [<RFC Topic>](<RFC URL>)
64-
* [Tracking Issue](<Tracking Issue URL>)
65-
* [Testing steps](<Testing Steps URL>)
66-
-->
67-
<!-- or if there are no new or updated RFCs this week, use: -->
68-
<!-- * *No New or Updated RFCs were created this week.* -->
69-
<!-- Remember to remove the `call-for-testing` label from the RFC so that the maintainer can signal for testers again, if desired. -->
70-
71-
### [RFCs](https://github.com/rust-lang/rfcs/issues?q=label%3Acall-for-testing)
58+
implementation and give feedback, especially before stabilization.
7259

73-
### [Rust](https://github.com/rust-lang/rust/labels/call-for-testing)
60+
If you are a feature implementer and would like your RFC to appear in this list, add a
61+
`call-for-testing` label to your RFC along with a comment providing testing instructions and/or
62+
guidance on which aspect(s) of the feature need testing.
7463

75-
### [Rustup](https://github.com/rust-lang/rustup/labels/call-for-testing)
64+
* No calls for testing were issued this week by [Rust](https://github.com/rust-lang/rust/labels/call-for-testing),
65+
[Rust language RFCs](https://github.com/rust-lang/rfcs/issues?q=label%3Acall-for-testing) or
66+
[Rustup](https://github.com/rust-lang/rustup/labels/call-for-testing).*
7667

77-
If you are a feature implementer and would like your RFC to appear on the above list, add the new `call-for-testing`
78-
label to your RFC along with a comment providing testing instructions and/or guidance on which aspect(s) of the feature
79-
need testing.
68+
[Let us know](https://github.com/rust-lang/this-week-in-rust/issues) if you would like your feature to be tracked as a part of this list.
8069

8170
## Call for Participation; projects and speakers
8271

0 commit comments

Comments
 (0)