init and build: a complete and sane project bootstrap but not buildable
Metadata
Current evaluation
Closed without implementing the proposed TEMPLATE-TODO build guard; discussion ended with Juju 2.9.0 using series to identify V1 charms. No fixing PR or commit was cited.
Resolution: closed stale
Reason: No resolving PR or commit is cited, and the proposed refusal to build unfinished templates was not implemented. The discussion ended with a Juju 2.9.0 decision to use series to identify V1 charms.
Evaluated by: mr-cal-bot
No scores available.
Issue body
`charmcraft init` should provide a complete and sane project: it should work in theory, and tests should pass.
At the same time, `charmcraft build` (or `pack` in the future) should not build a project which is just bootstrapped from `init` and not paid attention nor care from the developer.
To get to that situation, we will:
- fix templates left by `init`, so tests pass ok
- mark with a comment using an unusual token (e.g.: `TEMPLATE-TODO`) all those corners where the developer needs to work to get started a real project.
- check if any of those tokens are leftovers when `build`ing, and refuse to build if any of those are present (indicating which one(s))
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha | — | closed stale | Closed without implementing the proposed TEMPLATE-TODO build guard; discussion ended with Juju 2.9.0 using series to identify V1 charms. No fixing PR or commit was cited. | |
| stealth/space-bunny-alpha | — | closed not a bug | The proposed refusal to build unfinished templates was not implemented; discussion ended with Juju 2.9.0 using series to identify V1 charms. No fixing Charmcraft change is cited. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Closed without implementation. Discussion shifted to Juju metadata detection. The proposed TEMPLATE-TODO build guard was never added, indicating the feature was deferred or superseded. | |
| qwen/qwen3.6-35b-a3b | — | — | Closed without implementing the requested build failure for leftover init placeholders. Discussion shifted to Juju V1 V2 metadata detection, with maintainers agreeing to use series as the determinant. The feature was abandoned. | |
| qwen/qwen3.6-35b-a3b | — | — | Closed. The request to block builds on placeholder tokens was abandoned as discussions shifted to Juju's V1 vs V2 metadata detection. Contributors suggested using series as a reliable format determinant instead. No explicit fix was implemented. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Resolved. The team decided to use the series field to distinguish V1 from V2 metadata for Juju 2.9.0, addressing concerns that charmcraft build always generates a manifest with bases. |
Update history
No update history recorded yet.
Related issues
No related issues found above the similarity threshold.