rust plugin: Support `disable-parallel` parameter
Metadata
Current evaluation
Feature request to add the disable-parallel part property to the rust plugin. Labeled 'Needs information' — maintainer awaits a real-world use case before implementing. No activity for 363 days; rust plugin still lacks the property.
Suggested action: close stale
Reason: The issue is labeled 'Status: Needs information' and the body explicitly requests a real-world use case ('extremely low priority until someone shows us a real-world use case'), but 363 days have passed with zero comments and no use case provided — far beyond the 6-month threshold. The rust plugin still lacks disable_parallel (only autotools has it, per PR #1167), so it is not fixed, but the requested information never arrived and the maintainer has deprioritized it.
Issue body
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen/qwen3.8-27b |
Impact:
15
Quick Win:
12.75
Staleness:
82
Complexity:
15
Confidence:
78
Support Request:
10
|
close stale | Feature request to add the disable-parallel part property to the rust plugin. Labeled 'Needs information' — maintainer awaits a real-world use case before implementing. No activity for 363 days; rust plugin still lacks the property. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
90
Complexity:
35
Confidence:
85
Support Request:
10
|
close stale | Request to add disable-parallel property support to the rust plugin. Marked as low-priority enhancement awaiting a real-world use case, with no maintainer activity or updates for over 10 months. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
80
Complexity:
30
Confidence:
75
Support Request:
10
|
close stale | Enhancement to add disable-parallel property to the rust plugin. Open for 309 days with no activity or use case provided, awaiting maintainer decision on backlog status. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
85
Complexity:
40
Confidence:
75
Support Request:
10
|
close stale | Add disable-parallel property support to the Rust plugin. Currently an enhancement needing a real-world use case to proceed. Low priority until a concrete parallel build failure scenario is provided for testing. |
Update history
No update history recorded yet.
Related work
-
Related To:
craft-parts#1167
(confidence 90%)
Autotools plugin PR that added disable-parallel support, cited in the issue body as the reference implementation.
-
Related To:
craft-parts#1237
(confidence 75%)
Sibling issue requesting the same disable-parallel support for the go plugin, part of the same batch of per-plugin enhancement requests.
-
Related To:
craft-parts#1240
(confidence 75%)
Sibling issue requesting the same disable-parallel support for the java plugin.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #1232 ant plugin: Support `disable-parallel` parameter | craft-parts | open | Feature request to add the disable-parallel part property to the ant plugin. Labeled 'Needs information' and waiting ~1 year for a real-world use case; maintainer explicitly called it extremely low priority until one is provided. | |
| #1233 cargo-use plugin: Support `disable-parallel` parameter | craft-parts | open | Feature request to add disable-parallel to the cargo-use plugin. Labeled Needs information; maintainer awaits a real-world use case, none provided in ~12 months. Plugin still lacks the property; its build step is a file copy, so the property would be a no-op. | |
| #1238 go-use plugin: Support `disable-parallel` parameter | craft-parts | open | Feature request to add the disable-parallel part property to the go-use plugin. Labeled Needs information; maintainer awaits a real-world use case, none provided in ~12 months. Plugin still lacks the property. | |
| #1235 dotnet plugin: Support `disable-parallel` parameter | craft-parts | open | Request to add the disable-parallel part property to the dotnet plugin. Labeled Needs information; the maintainer marked it extremely low priority pending a real-world use case, which has not been provided in 363 days. | |
| #1246 npm plugin: Support `disable-parallel` parameter | craft-parts | open | Feature request to add the disable-parallel part property to the npm plugin. Labeled Needs information; maintainers await a real-world use case before implementing. No activity for ~12 months; part of a family of similar open issues for other plugins. | |
| #1243 maven plugin: Support `disable-parallel` parameter | craft-parts | open | Feature request to add the disable-parallel part property to the maven plugin. Labeled 'Needs information' - maintainer awaits a real-world use case. No activity for ~12 months; the maven plugin still lacks the property. | |
| #1237 go plugin: Support `disable-parallel` parameter | craft-parts | open | Go plugin lacks disable-parallel support. Filed by maintainer as low-priority enhancement, labeled Needs information, explicitly awaiting a real-world use case that never arrived in 363 days of zero activity. | |
| #1239 gradle plugin: Support `disable-parallel` parameter | craft-parts | open | Gradle plugin lacks disable-parallel part property support. Labeled Needs information; maintainer proposed a 3-state (None/False/True) design but is waiting for a real-world use case. No implementation in code after 363 days. | |
| #1240 java plugin: Support `disable-parallel` parameter | craft-parts | open | Enhancement request to add the disable-parallel part property to the Java base plugin (shared by ant, gradle, maven, maven-use). Labeled Needs information; maintainer awaits a real-world use case, no activity for 363 days. | |
| #1241 jlink plugin: Support `disable-parallel` parameter | craft-parts | open | Request to support the disable-parallel part property in the jlink plugin. Maintainer labeled it 'Needs information' and called it extremely low priority without a real-world use case; no activity for ~12 months, still unimplemented. |