← Back to issue list

Mechanism to handle/promote 'devel' bases

View original Github issue

Metadata

Project
craft-application
Number
#298
Type
issue
State
closed
Author
tigarmo
Labels
Created
Updated
Closed

Current evaluation

Closed without implementation. The proposal to centralize devel base validation in craft-application and update dependent projects was not addressed. Synced to Jira as CRAFT-2675, but no fix or follow-up pull request was created.

Suggested action:

No scores available.

Issue body

### What needs to get done The current task that we have is to update all applications so that the 24.04 base no longer requires the `devel` build-base. The specifics of base description in each project is different but we should keep the core logic in craft-application. Like, a function that tells whether a given craft-provider's `Base` is mandatory "devel" or not. Of course, we then need to update the applications to make use of this new code. ### Why it needs to get done To avoid having to do the same work N times

Evaluation history

Date Model Scores Action Summary
qwen/qwen3.6-35b-a3b Closed without implementation. The proposal to centralize devel base validation in craft-application and update dependent projects was not addressed. Synced to Jira as CRAFT-2675, but no fix or follow-up pull request was created.
qwen/qwen3.6-35b-a3b Closed and synced to internal Jira ticket CRAFT-2675 without a technical resolution. The request to centralize devel base logic was abandoned, leaving the task unresolved.
qwen3.6-35b-a3b-mtp-q6 Closed without implementation or merge. The request to centralize devel base handling in craft-application was not addressed. Only a Jira sync comment exists, indicating the issue was abandoned with no code changes applied.

Update history

No update history recorded yet.

Related issues

Issue Project State Summary Similarity
#4721 feat: validate devel bases with craft-application snapcraft closed Superseded by pull request #4796. The changes to validate devel bases with craft-application and remove the build-base: devel requirement for core24 snaps were closed in favor of the newer implementation.
72%
#880 Devel base info is outdated craft-application closed Reporting outdated devel base info in craft_application was closed without a fix or resolution. No code changes or merges were applied, indicating the bug was likely abandoned or superseded.
71%