-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Closed
Description
There are several unstable Cargo features without an RFC that we would like help in testing. As there is no documented process without an RFC, I figured I'd create an issue here
rust-lang/cargo#11123: cargo install --dry-run
- Instructions: cargo install --dry-run cargo#11123 (comment)
rust-lang/cargo#14520: native completions for cargo
Metadata
Metadata
Assignees
Labels
No labels
Type
Projects
Milestone
Relationships
Development
Select code repository
Activity
bennyvasquez commentedon Dec 12, 2024
Hi there! Thanks for creating the issue. As you said, there's no good place for this to live right now. Is this something that you could phrase into a request for contributions?
epage commentedon Dec 12, 2024
Is there a reason that the Call for Testing section wouldn't work for this? Is there a reason to limit it to just RFCs? Many teams have adopted different processes (ACP, MCP, etc) where an RFC may never be involved yet it can still be useful to test.
bennyvasquez commentedon Dec 13, 2024
I'm honestly not sure it fits there, but that section is managed by another editor. @U007D what do you think about potentially adding these sorts of things to the calls for testing? I think I remember you were considering expanding it, but I don't remember if you ever did.
epage commentedon Dec 13, 2024
Ah, looks like this came up in #5222. I've added a label for the Cargo repo: https://github.com/rust-lang/cargo/labels/call-for-testing
If Cargo could be added to the query, that'd be great!
epage commentedon Apr 14, 2025
@U007D could you track
call-for-testing
for cargo. Looks like we now have 5 features being tested.weihanglo commentedon Jun 2, 2025
I have opened #6701, and also went ahead and created a PR for one specific call-for-testing #6702.
U007D commentedon Jun 3, 2025
I can't think of any valid reason why only RFC's should be tracked.
I do run a query against the
cargo
repo each week--I'll check and will update the query to pick up anything flagged withcall-for-testing
, if it's not already, starting in TWiR Issue 602.weihanglo commentedon Jun 3, 2025
Thanks @U007D!
Let us know how we can collaborate better. I guess when labelling with
call-for-testing
, we always include one-line summary for you to scrape. That should help.U007D commentedon Jun 4, 2025
@epage @weihanglo First of all, sorry for the delay on this! I too think a combination of not checking the open issues list closely enough and remembering that Issue #5222 was taken care of (that's when
rustup
got added to the weekly rotation) caused me to miss realizing this was still an open issue.The good news is that
cargo
is in the weekly rotation now and any issues picked up by this query provided by @epage will appear in TWiR. (Note: I still do this by hand and I look at each item before publishing.)