Bug details: ** https://bugzilla.redhat.com/show_bug.cgi?id=1995439 ** Information from BlockerBugs App:
Commented but haven't voted yet: lruzicka, coremodule, adamwill
The votes have been last counted at 2021-10-25 19:41 UTC and the last processed comment was #comment-759034
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
The only container-related criterion I see is this for IoT:
The Podman container runtime must be present on all images and installed by default when using the ISO installer. It must be possible to deploy a container image. https://fedoraproject.org/wiki/Fedora_35_Beta_Release_Criteria#Podman_container_runtime
Unless this is a general podman issue (and not just toolbox one), and we can demonstrate it on IoT, I think we don't have a criterion to block on it. I asked in the bug.
podman
toolbox
AGREED AcceptedFinalFE
The following votes have been closed:
I asked in the bug
The issue affects only toolbox. I think we don't have a reason to block F35 on this.
FinalBlocker -1
AGREED RejectedFinalBlocker
Discussed during the 2021-09-20 blocker review meeting: [0]
The decision to classify this bug as a "RejectedBlocker (Final)" was made as this does not violate any criteria. It's significant primarily for user-facing ostree builds, and none of those are prelease-blocking yet.
[0] https://meetbot.fedoraproject.org/fedora-blocker-review/2021-09-20/f35-blocker-review.2021-09-20-16.00.txt
FinalFE +1
@lruzicka marked this as accepted final FE, but for no clear reason and with no votes, so:
REVOTE FinalFE
Metadata Update from @blockerbot: - Issue status updated to: Closed (was: Open)
Release F35 is no longer tracked by BlockerBugs, closing this ticket.
Log in to comment on this ticket.