← Back to issue list

Specify a project's lifecycle

View original Github issue

Metadata

Project
craft-application
Number
#222
Type
issue
State
open
Author
lengau
Labels
—
Created
Updated
Closed
—

Current evaluation

Design task to define and document Project lifecycle in craft-application: creation, mutation (adopt-info), and command/service interaction. Unlabelled, no maintainer response, inactive 465 days.

Suggested action: needs triage

Reason: The issue has no labels, no assignee, and the only comment is the Jira-sync bot (2024-02-21) — no maintainer has assessed, categorised, or responded to it in 465 days. It is a maintainer-authored architectural design task (project creation, mutation via LifecycleService/adopt-info, access rules) that requires a maintainer to decide whether the questions remain open or have been addressed by subsequent PRs.

Impact: 45 Quick Win: 11.25 Staleness: 80 Complexity: 75 Confidence: 60 Support Request: 5

Issue body

### What needs to get done Define and document: 1. When (and if) a Project gets created 2. How project mutation works (difficult case: `LifecycleService` writing `adopt-info`. See: https://github.com/canonical/craft-application/pull/217/files#r1496586665) 3. How commands and services should interact with Projects Some questions to consider: - Should a Project be frozen? (Pros/cons) - What should/should not have access to a project? - How do we handle commands where project access is optional? (e.g. remote-build) ### Why it needs to get done This is loosely defined currently and has worked fine so far, but we're reaching edge cases that make us need a

Evaluation history

Date Model Scores Action Summary
qwen/qwen3.8-27b
Impact: 45
Quick Win: 11.25
Staleness: 80
Complexity: 75
Confidence: 60
Support Request: 5
needs triage Design task to define and document Project lifecycle in craft-application: creation, mutation (adopt-info), and command/service interaction. Unlabelled, no maintainer response, inactive 465 days.
qwen/qwen3.6-35b-a3b
Staleness: 85
Complexity: 60
Confidence: 85
Support Request: 5
needs triage Define and document project lifecycle rules for creation, mutation, and command/service interactions. Currently unlabelled and inactive for over a year, awaiting maintainer assessment.
qwen3.6-35b-a3b-mtp-q6
Staleness: 85
Complexity: 75
Confidence: 80
Support Request: 5
needs triage Request to define and document the Project lifecycle, including creation, mutation, and service interactions. Currently unlabelled and inactive for over a year.
qwen3.6-35b-a3b-mtp-q6
Staleness: 85
Complexity: 75
Confidence: 70
Support Request: 5
needs triage Define and document project lifecycle rules covering creation, mutation, access control, and service interaction. Currently loosely defined but encountering edge cases. Open, unlabelled, inactive for over a year, and awaiting specification or triage.

Update history

No update history recorded yet.

Related work

  • Related To: canonical/craft-application#217 (confidence 70%)

    Issue body explicitly references PR #217 review comment (r1496586665) as the difficult case for project mutation via LifecycleService writing adopt-info.

Related issues

No related issues found above the similarity threshold.