Unified up-to-date spread file
Metadata
Current evaluation
Request for a unified, up-to-date base spread file in rockcraft, filed by a maintainer to save time in charmcraft builds; only an auto-generated Jira sync comment, no labels or discussion for ~16 months.
Suggested action: needs triage
Reason: The issue has no labels, no assignee, and no human maintainer response — the sole comment is the autogenerated Jira sync bot (CRAFT-3003), so it shows no sign of being categorised or prioritised. It is an internal infrastructure task (not a bug or support question), and while it has been inactive ~16 months, there is no evidence it was implemented or is obsolete, so closing as stale would be premature.
Issue body
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen/qwen3.8-27b |
Impact:
30
Quick Win:
18.0
Staleness:
75
Complexity:
40
Confidence:
55
Support Request:
10
|
needs triage | Request for a unified, up-to-date base spread file in rockcraft, filed by a maintainer to save time in charmcraft builds; only an auto-generated Jira sync comment, no labels or discussion for ~16 months. | |
| qwen/qwen3.8-27b |
Impact:
25
Quick Win:
12.5
Staleness:
75
Complexity:
50
Confidence:
55
Support Request:
10
|
needs triage | Feature request for a unified, up-to-date base spread file in rockcraft, motivated by time saved in charmcraft PR #1641. No labels, no maintainer response beyond an auto-generated Jira sync; inactive for about 16 months. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
95
Complexity:
20
Confidence:
85
Support Request:
10
|
close stale | Request for a unified, up-to-date base spread file to improve rockcraft and charmcraft workflows. Unlabelled and inactive for over a year. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
95
Complexity:
30
Confidence:
85
Support Request:
10
|
close stale | Request for a unified base spread file to streamline testing across charmcraft and rockcraft. Currently inactive for over a year with no maintainer labels or responses. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
85
Complexity:
60
Confidence:
70
Support Request:
65
|
close stale | Proposes a unified, up-to-date base spread file to streamline rockcraft and charmcraft logic. Stale for over a year with an internal Jira ticket created. Requires triage and assignment. |
Update history
No update history recorded yet.
Related work
-
Related To:
canonical/charmcraft#1641
(confidence 70%)
Issue body cites a comment on this merged PR as motivation: having rockcraft logic there 'would have saved us time in charmcraft'.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #1643 Add debugging logic to spread file | charmcraft | open | Feature request to copy debugging logic from rockcraft's spread file into charmcraft's spread.yaml. No maintainer response, no labels, no assignee; only an auto-generated Jira sync bot comment. Untriaged and stale. |