← Back to issue list

Rewrite the development base check to use distro-support

View original Github issue

Metadata

Project
craft-application
Number
#881
Type
issue
State
open
Author
lengau
Labels
Status: Triaged Type: Enhancement
Created
Updated
Closed
—

Current evaluation

Replace the hard-coded development-base list with distro-support metadata so status is checked at runtime. The triaged enhancement remains open; maintainers are clarifying how app-level support control interacts with distro data.

Suggested action: keep open

Reason: The code still hard-codes Ubuntu's devel alias in DEVEL_BASE_INFOS and validates build-base against it; distro-support is used for EOL support ranges but not this development-base decision. Although the issue is labeled Triaged and the maintainer says Craft app developers must control official base support, that policy interaction needs reconciliation; it remains a valid, scoped enhancement.

Evaluated by: mr-cal-bot

Impact: 55 Quick Win: 18 Complexity: 48 Confidence: 88 Actionability: 62

Issue body

### What needs to get done Currently the development base uses hard-coded info about which bases are under development. Since we're including the distro-support library which has this info anyway, we should use it to check. ### Why it needs to get done This should be something that's runtime-checkable rather than requiring a new release.

Evaluation history

Date Model Scores Action Summary
stealth/space-bunny-alpha
Impact: 55
Quick Win: 18
Complexity: 48
Confidence: 88
Actionability: 62
keep open Replace the hard-coded development-base list with distro-support metadata so status is checked at runtime. The triaged enhancement remains open; maintainers are clarifying how app-level support control interacts with distro data.
qwen/qwen3.6-35b-a3b
Impact: 30
Quick Win: 15
Complexity: 30
Confidence: 70
Actionability: 70
keep open Enhancement to refactor development base check in craft-application to use distro-support library instead of hard-coded DEVEL_BASE_INFOS. Issue is triaged and open.
qwen/qwen3.8-27b
Impact: 40
Quick Win: 24
Staleness: 70
Complexity: 40
Confidence: 75
Support Request: 10
keep open Enhancement to replace hard-coded development base checks with distro-support for runtime validation. Triaged by maintainer but inactive for ~12 months; hard-coded DEVEL_BASE_INFOS still present in models/project.py.
qwen/qwen3.6-35b-a3b
Staleness: 80
Complexity: 15
Confidence: 85
Support Request: 0
keep open Enhancement to replace hard-coded development base checks with the distro-support library for runtime validation. Triaged but inactive for over 10 months with no active work or assignee.
qwen3.6-35b-a3b-mtp-q6
Staleness: 75
Complexity: 25
Confidence: 80
Support Request: 5
keep open Refactor development base check to use distro-support library instead of hardcoded values. Issue is triaged as an enhancement but has been inactive for over 10 months with no assignee or follow-up.

Update history

No update history recorded yet.

Related work

  • Related To: craft-application#882 (confidence 98%)

    Commit 04940264 updated the hard-coded devel-base information, demonstrating the manual maintenance this change would remove.

  • Related To: craft-application#955 (confidence 98%)

    Commit 73a0e4ea set Ubuntu 26.04 as the current devel base, another manual hard-coded update.

Related issues

No related issues found above the similarity threshold.