Bug details: https://bugzilla.redhat.com/show_bug.cgi?id=2237396 Information from BlockerBugs App: <img alt="2237396" src="https://qa.fedoraproject.org/blockerbugs/api/v0/bugimg/2237396" />
Commented but haven't voted yet: coremodule
The votes have been last counted at 2023-10-06 19:13 UTC and the last processed comment was #comment-877502
To learn how to vote, see: https://pagure.io/fedora-qa/blocker-review A quick example: BetaBlocker +1 (where the tracker name is one of BetaBlocker/FinalBlocker/BetaFE/FinalFE/0Day/PreviousRelease and the vote is one of +1/0/-1)
BetaBlocker +1
BetaBlocker
FinalBlocker
BetaFE
FinalFE
0Day
PreviousRelease
+1
0
-1
Discussed during the 2023-09-25 blocker review meeting: [0]
The decision to delay the classification of this as a freeze exception was made as we would like a clearer rationale for why it would be beneficial to grant an FE to this bug, given that containerd is not used by podman and probably isn't on any media aside from CoreOS. Our question: what does an FE achieve here that a 0-day update would not?
[0] https://meetbot.fedoraproject.org/fedora-blocker-review/2023-09-25/f39-blocker-review.2023-09-25-16.02.txt
I think there's too much going on here to justify a FE. I think a 0-day update should be enough. Let's try to get this done instead.
FinalFE -1
It seems this can easily be just a 0-day update.
I agree.
FinalFE -1 AGREED RejectedFinalFE
The following votes have been closed:
Metadata Update from @blockerbot: - Issue status updated to: Closed (was: Open)
Release F39 is no longer tracked by BlockerBugs, closing this ticket.
Log in to comment on this ticket.