Skip to content

Commit 38e0234

Browse files
committed
Update DRAFT_TEMPLATE for RFC, MCP, FCP and CFT
1 parent 4269405 commit 38e0234

File tree

1 file changed

+32
-9
lines changed

1 file changed

+32
-9
lines changed

draft/DRAFT_TEMPLATE

Lines changed: 32 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -57,19 +57,42 @@ and just ask the editors to select the category.
5757
[submit_crate]: https://users.rust-lang.org/t/crate-of-the-week/2704
5858

5959
## Calls for Testing
60+
An important step for feature implementation is for people to experiment with the
61+
implementation and give feedback, especially before stabilization.
6062

61-
An important step for RFC implementation is for people to experiment with the
62-
implementation and give feedback, especially before stabilization. The following
63-
RFCs would benefit from user testing before moving forward:
63+
If you are a feature implementer and would like your feature to appear in this list, add a
64+
`call-for-testing` label to your RFC along with a comment providing testing instructions and/or
65+
guidance on which aspect(s) of the feature need testing.
6466

65-
<!-- Calls for Testing go here, use this format:
66-
* [<RFC Topic>](<RFC URL>)
67-
* [Tracking Issue](<Tracking Issue URL>)
67+
<!-- If there are new CfT items this week, use: -->
68+
<!--
69+
[Repo Name](Repo URL)
70+
* [<Feature name>](<Feature URL>)
6871
* [Testing steps](<Testing Steps URL>)
6972
-->
70-
<!-- or if there are no new or updated RFCs this week, use: -->
71-
<!-- * *No New or Updated RFCs were created this week.* -->
72-
<!-- Remember to remove the `call-for-testing` label from the RFC so that the maintainer can signal for testers again, if desired. -->
73+
<!-- where `Repo Name` and `Repo URL` are one of:
74+
[Rust](https://github.com/rust-lang/rust/labels/call-for-testing),
75+
[Rust language RFCs](https://github.com/rust-lang/rfcs/issues?q=label%3Acall-for-testing),
76+
[Cargo](https://github.com/rust-lang/cargo/labels/call-for-testing) or
77+
[Rustup](https://github.com/rust-lang/rustup/labels/call-for-testing)
78+
-->
79+
80+
<!-- For all `Repo Names` with no new CfT items this week: use (removing the repos for which new
81+
CfT items did appear, of course) -->
82+
<!--
83+
* *No calls for testing were issued this week by
84+
[Rust](https://github.com/rust-lang/rust/labels/call-for-testing),
85+
[Rust language RFCs](https://github.com/rust-lang/rfcs/issues?q=label%3Acall-for-testing),
86+
[Cargo](https://github.com/rust-lang/cargo/labels/call-for-testing) or
87+
[Rustup](https://github.com/rust-lang/rustup/labels/call-for-testing).*
88+
-->
89+
* *No calls for testing were issued this week by [Rust](https://github.com/rust-lang/rust/labels/call-for-testing),
90+
[Rust language RFCs](https://github.com/rust-lang/rfcs/issues?q=label%3Acall-for-testing),
91+
[Cargo](https://github.com/rust-lang/cargo/labels/call-for-testing) or
92+
[Rustup](https://github.com/rust-lang/rustup/labels/call-for-testing).*
93+
94+
[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.
95+
-->
7396

7497
### [RFCs](https://github.com/rust-lang/rfcs/issues?q=label%3Acall-for-testing)
7598

0 commit comments

Comments
 (0)