I recently mailed the test list for this exact discussion. As @adamwill mentioned, in this email, it would take an edition/lab/spin to declare Toolbx as it's own crit-path and that's how Quality will consider it as one. As Toolbx is a release blocker now and Podman recent changes , went unnoticed and potentially can break toolbx's functionality in F37 and F38. I believe Toolbx should be marked as crit-path.
WDY'allT?
+1 from me.
This seems uncontroversial and I'd be quite surprised if the WG would not support this. Let's say it's approved if nobody objects by the end of the week.
This is approved. (Of course, somebody would still have to implement it.)
Metadata Update from @catanzaro: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.