Allow `devel` in multi-base builds
Metadata
Current evaluation
Enhancement to let `devel` build bases be used in charm multi-base `build-on` entries; design agreed with lengau, implementation PR #217 approved and green but still unmerged with open review threads.
Suggested action: keep open
Reason: The issue is properly triaged (labels 'Type: Enhancement', 'Status: Triaged', opened by maintainer mr-cal) and lengau gave a concrete design steer ('only allow `devel` in the `build-on`... we should also support `ubuntu@devel`'). Work is actively in flight: PR #217 'feat: allow `devel` in multi-base charm builds' is approved by 2 reviewers with all CI green but remains open with 10 unresolved review threads, and the code at HEAD still computes a single `distro_base` per platform in `craft_platforms/charm/_build.py`, so the feature is not yet released. Not close_resolved because nothing is merged.
Evaluated by: mr-cal-bot
Issue body
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha |
Impact:
45
Quick Win:
19
Complexity:
50
Confidence:
88
Actionability:
85
|
keep open | Enhancement to let `devel` build bases be used in charm multi-base `build-on` entries; design agreed with lengau, implementation PR #217 approved and green but still unmerged with open review threads. | |
| stealth/space-bunny-alpha |
Impact:
45
Quick Win:
19
Complexity:
52
Confidence:
96
Actionability:
90
|
keep open | Triaged enhancement to support devel build bases in charm multi-base plans; implementation PR craft-platforms#217 is approved and green but remains open with unresolved review comments. | |
| stealth/space-bunny-alpha |
Impact:
55
Quick Win:
25
Complexity:
45
Confidence:
94
Actionability:
82
|
keep open | Enhancement requests devel build bases for multi-base charm platforms. Triaged, with an approved implementation PR open and review comments still unresolved. | |
| qwen3.6-35b-a3b-mtp-q6 |
Impact:
55
Quick Win:
30
Staleness:
55
Complexity:
45
Confidence:
75
Support Request:
15
|
keep open | Enhancement to allow `devel` build bases in multi-base charm builds. Triaged with maintainer discussion on implementation approach. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
45
Complexity:
40
Confidence:
85
Support Request:
10
|
keep open | Enhancement to allow devel build bases in multi-base charm builds. Currently triaged and under discussion, with maintainer input on implementation details. Last activity ~3 months ago. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
55
Complexity:
30
Confidence:
85
Support Request:
0
|
keep open | Enhancement to allow devel build bases in multi-base charm builds. Currently triaged and under discussion, with maintainers debating implementation details for build-on and build-for fields. |
Update history
No update history recorded yet.
Related work
-
Likely Fixed By:
craft-platforms#217
(confidence 90%)
Open PR implementing per-entry build base validation/planning for `devel` in multi-base charm build-ons, with unit and hypothesis-filter tests; approved but unmerged.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #217 feat: allow `devel` in multi-base charm builds | craft-platforms | open | Lets `devel` be used in multi-base charm `build-on` entries: validation and build planning now use the per-entry build base, rejecting mixed devel+stable and devel+base-less mixes. Adds unit plus hypothesis-filter tests. Approved by 2 reviewers, all CI green, but 10 review threads unresolved. | |
| #298 Mechanism to handle/promote 'devel' bases | craft-application | closed | Implemented centralized validation for mandatory upstream devel build bases in merged PR #302 (commit aeae554e), avoiding duplicated application logic. |