Report whether critical path packages (and other comps groups?) are impacted #13
Labels
No labels
Priority
High
Priority
Low
Priority
Medium
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
packaging/orphansv2#13
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This is not implemented in v1, but I'd like to add it to the report for v2.
I think rather than "critical path" - which is rather arbitrarily defined and is kinda meant to be only packages whose breakage would be immediately obvious and visible to users - it'd make sense to flag impact on "compose critical" packages - packages which are used in the building of the non-failable images in the compose process. I wrote a thing for this, working out where to publish it ATM.