Inconsistent parameter syntax
Metadata
Current evaluation
snapcraft release accepts comma-separated channels but snapcraft close does not, requiring space-separated args. 8+ years old, zero comments, no labels, project since completely rewritten.
Suggested action: close stale
Reason: The issue is 3028 days old with zero comments, no labels, and no maintainer interaction. The repo layout shows a modern craft-application-based snapcraft architecture, indicating the project has been completely rewritten since this issue was filed. The old snapcraft 1.x store commands (release, close) referenced here are almost certainly no longer present in the same form, making the reported inconsistency no longer applicable.
Impact:
15
Quick Win:
12.75
Staleness:
95
Complexity:
15
Confidence:
60
Support Request:
10
Issue body
Snapcraft release uses commas:-
snapcraft release foo 1 candidate,beta
Snapcraft close does not:-
root@snapcrafters:~# snapcraft close warzone2100 beta,candidate
Could not close channel: Not a valid channel: beta,candidate
root@snapcrafters:~# snapcraft close warzone2100 beta candidate
Track Arch Channel Version Revision
latest amd64 stable 3.2.3 12
candidate ^ ^
beta ^ ^
edge 3.2.3 14
armhf stable 3.2.3 10
candidate ^ ^
beta ^ ^
edge 3.2.3 13
i386 stable 3.2.3 11
candidate ^ ^
beta ^ ^
edge 3.2.3 15
The beta and candidate channels are now closed.
This feels inconsistent.
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen/qwen3.8-27b |
Impact:
15
Quick Win:
12.75
Staleness:
95
Complexity:
15
Confidence:
60
Support Request:
10
|
close stale | snapcraft release accepts comma-separated channels but snapcraft close does not, requiring space-separated args. 8+ years old, zero comments, no labels, project since completely rewritten. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
95
Complexity:
30
Confidence:
90
Support Request:
10
|
close stale | Reports inconsistent CLI syntax between snapcraft release and close commands regarding channel parameter separators. Issue is over 8 years old with no maintainer response or activity. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
98
Complexity:
25
Confidence:
85
Support Request:
10
|
close stale | Reports CLI inconsistency between snapcraft release and close regarding channel parameter syntax. Unaddressed for over 8 years with no maintainer interaction. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
95
Complexity:
10
Confidence:
80
Support Request:
5
|
close stale | Reports CLI inconsistency where snapcraft release uses comma-separated channels but snapcraft close expects space-separated channels. Untriaged, inactive for over 8 years. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
100
Complexity:
15
Confidence:
90
Support Request:
5
|
close stale | Reports inconsistent CLI syntax between snapcraft release (comma-separated) and snapcraft close (space-separated) for channel arguments. Issue has been completely inactive for over 8 years with no maintainer response. |
Update history
No update history recorded yet.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #1767197 Inconsistent quoting of risk level when releasing and closing channels | snapcraft (launchpad) | open | Cosmetic CLI output inconsistency in snapcraft 2.41: release command wraps channel name in single quotes ('candidate') while close command does not (edge). Filed 8+ years ago with zero comments, no labels, and no maintainer interaction. |