← Back to issue list

list-extensions command to show experimental bases under experimental column

View original Github issue

Metadata

Project
rockcraft
Number
#1178
Type
issue
State
open
Author
f-atwi
Labels
—
Created
Updated
Closed
—

Current evaluation

Feature request to give experimental bases their own list-extensions column remains unlabelled and untriaged; current code still lists every supported base together.

Suggested action: needs triage

Reason: The issue has no labels, maintainer comments, or other evidence of maintainer assessment, so it still needs triage. The current ExtensionModel stores only bases and marshals them exclusively as "Supported bases", even though the extension API already exposes is_experimental(base) and tests include ExperimentalExtension, making this a valid, localized feature gap.

Evaluated by: mr-cal-bot

Impact: 40 Quick Win: 25 Complexity: 25 Confidence: 96 Actionability: 84

Issue body

### Check existing issues - [x] I've verified that this request isn't described by any existing issues. ### Request Rockcraft list-extensions returns a list of all extensions and their supported bases. This has no mention of any experimental bases. ```console $ rockcraft list-extensions Extension name Supported bases --------------------- ---------------------------------------------- django-framework bare, ubuntu:22.04, ubuntu@22.04, ubuntu@24.04 expressjs-framework bare, ubuntu@24.04 fastapi-framework bare, ubuntu@24.04 flask-framework bare, ubuntu:22.04, ubuntu@22.04, ubuntu@24.04 go-framework bare, ubuntu@24.04 spring-boot-framework bare, ubuntu@24.04 ``` An example of what the proposal aims for is to have a similar result like with charmcraft where using list-extensions gives the following ```console $ charmcraft list-extensions Extension name Supported bases Experimental bases --------------------- ----------------- -------------------- django-framework ubuntu@22.04 expressjs-framework ubuntu@24.04 fastapi-framework ubuntu@24.04 flask-framework ubuntu@22.04 go-framework ubuntu@24.04 spring-boot-framework ubuntu@24.04 ``` ### The problem it solves Provides a reliable way to show the user that an extension is experimental through the tool directly. Provides consistent behavior between charmcraft and rockcraft.

Evaluation history

Date Model Scores Action Summary
stealth/space-bunny-alpha
Impact: 40
Quick Win: 25
Complexity: 25
Confidence: 96
Actionability: 84
needs triage Feature request to give experimental bases their own list-extensions column remains unlabelled and untriaged; current code still lists every supported base together.
qwen/qwen3.6-35b-a3b
Impact: 35
Quick Win: 18
Complexity: 35
Confidence: 65
Actionability: 80
needs triage Feature request to add an 'Experimental bases' column to `rockcraft list-extensions` output, matching charmcraft's behavior. The issue is open, unlabelled, and has no maintainer response after 162 days.
qwen/qwen3.8-27b
Impact: 40
Quick Win: 28
Staleness: 55
Complexity: 30
Confidence: 80
Support Request: 10
needs triage Feature request to add an 'Experimental bases' column to rockcraft list-extensions, matching charmcraft's output. Not yet implemented; command still only shows supported bases. No maintainer activity or labels on the issue.
qwen/qwen3.6-35b-a3b
Staleness: 70
Complexity: 20
Confidence: 85
Support Request: 0
needs triage Feature request to add an experimental bases column to the rockcraft list-extensions command output, matching charmcraft's behavior. Currently untriaged with no maintainer activity for over 100 days.
qwen3.6-35b-a3b-mtp-q6
Staleness: 65
Complexity: 20
Confidence: 80
Support Request: 0
needs triage Feature request to add an experimental bases column to the rockcraft list-extensions command, matching charmcraft behavior. Currently unlabelled and inactive for 90 days.
qwen3.6-35b-a3b-mtp-q6
Staleness: 60
Complexity: 20
Confidence: 85
Support Request: 0
needs triage Feature request to add an experimental bases column to the rockcraft list-extensions command output, matching charmcraft behavior. Currently unlabelled and inactive for 87 days with no maintainer response.

Update history

No update history recorded yet.

Related issues

No related issues found above the similarity threshold.