Consider adding flag to extensions to list experimental extensions
Metadata
Current evaluation
Feature request to add an --all flag to the extensions listing command and surface the SNAPCRAFT_ENABLE_EXPERIMENTAL_EXTENSIONS hint, so users can identify experimental extensions. The target command has since been renamed from list-extensions to extensions; the gap still exists. Untriaged.
Suggested action: needs triage
Reason: The issue has no labels, no assignee, and its only comment is an autogenerated bot message (CRAFT-3269) with no maintainer response, so it has never been triaged. The underlying gap is real and unfixed: ExtensionsCommand.run() in snapcraft/commands/extensions.py emits only 'Extension name' and 'Supported bases' columns and never calls is_experimental(), and docs/how-to/extensions/list-extensions.rst confirms the output includes experimental extensions 'without differentiating them'. Impact is modest (discoverability/UX rather than broken functionality) but actionable, since is_experimental() is already defined on every extension class and the fill_parser flag pattern is established. Confidence is slightly reduced because the request targets 'list-extensions', which has since been renamed to 'extensions' (commits 39d42857d, 23c327e82 merged PR #3678) and is now a hidden alias raising errors.RemovedCommand, so the proposal needs re-scoping against the current command name.
Evaluated by: mr-cal-bot
Issue body
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha |
Impact:
32
Quick Win:
12
Complexity:
18
Confidence:
82
Actionability:
45
|
needs triage | Feature request to add an --all flag to the extensions listing command and surface the SNAPCRAFT_ENABLE_EXPERIMENTAL_EXTENSIONS hint, so users can identify experimental extensions. The target command has since been renamed from list-extensions to extensions; the gap still exists. Untriaged. | |
| qwen/qwen3.6-35b-a3b |
Impact:
30
Quick Win:
13
Complexity:
30
Confidence:
70
Actionability:
60
|
needs triage | Feature request to add --all flag to snapcraft extensions command and display experimental extension enablement instructions. Command renamed from list-extensions to extensions. No maintainer response. | |
| qwen/qwen3.8-27b |
Impact:
20
Quick Win:
17
Staleness:
75
Complexity:
15
Confidence:
72
Support Request:
10
|
close stale | Feature request to add --all flag to list-extensions to show experimental extensions and display env var hint. The extensions command (renamed from list-extensions) already lists all extensions including experimental ones, as confirmed by docs. Only the env var hint in output remains unimplemented. No maintainer engagement in ~2 years. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
85
Complexity:
30
Confidence:
75
Support Request:
10
|
needs triage | Feature request to add an --all flag to list-extensions to show experimental extensions and enable instructions. The issue is unlabelled, unassigned, and has seen no maintainer engagement in nearly two years. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
90
Complexity:
20
Confidence:
85
Support Request:
10
|
needs triage | Feature request to add an --all flag to list-extensions to display experimental extensions and usage instructions. Currently unlabelled with no maintainer assessment beyond an automated Jira sync comment. |
Update history
No update history recorded yet.
Related work
-
Related To:
canonical/snapcraft#3266
(confidence 72%)
Merged PR 'cli: add --enable-experimental-extensions option for expand-extensions' is a directly analogous change: a flag exposing experimental extensions to the CLI. Demonstrates maintainer acceptance of this pattern, though the flag no longer appears in the current codebase.
-
Related To:
canonical/rockcraft#1178
(confidence 62%)
Rockcraft's open request for an experimental column in list-extensions is the sibling ask; the maintainer response there will likely inform the decision on this one.
Related issues
No related issues found above the similarity threshold.