Skip to content

feat: call-for-testing Cargo -Zrustdoc-depinfo #6702

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.

Sign up for GitHub

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

Closed
wants to merge 1 commit into from
Closed

feat: call-for-testing Cargo -Zrustdoc-depinfo #6702

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 6 additions & 0 deletions draft/2025-06-04-this-week-in-rust.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -77,6 +77,12 @@ RFCs would benefit from user testing before moving forward:

### [Rustup](https://github.com/rust-lang/rustup/labels/call-for-testing)

### [Cargo](https://github.com/rust-lang/cargo/labels/call-for-testing)

* `cargo doc` doc regeneration detection is now more precise and performant.
* [Tracking Issue](https://github.com/rust-lang/cargo/issues/15370)
* [Testing steps](https://github.com/rust-lang/cargo/issues/15370#issuecomment-2932749085)

If you are a feature implementer and would like your RFC to appear on the above list, add the new `call-for-testing`
label to your RFC along with a comment providing testing instructions and/or guidance on which aspect(s) of the feature
need testing.
Expand Down