Bug details: https://bugzilla.redhat.com/show_bug.cgi?id=2045875 Information from BlockerBugs App: <img alt="2045875" src="https://qa.fedoraproject.org/blockerbugs/api/v0/bugimg/2045875" />
The votes have been last counted at 2022-03-19 16:14 UTC and the last processed comment was #comment-786695
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
BetaBlocker -1
The person who nominated this bug said the issues are solved in anaconda now, so I'm not sure what basis there is for making this a blocker.
I think the request here was "please pull the Change into Beta, it's ready now". Which should be an FE, if anything, not a blocker.
I wouldn't want to pull this in as an FE if we try an RC today, if we slip a week it maaaaay be okay to pull it in.
No violated release criterion was identified here.
AGREED RejectedBetaBlocker
if there's more to this, we can always revote.
The following votes have been closed:
BetaFE +1
Nervously. This seems like it could be a little risky, but it would be good to have this on Beta media to maximize testing.
I'd like to see this go through, but I hear AdamW's concerns. I want to see it in testing and that needs to include the Vagrant images. BetaFE +1
AGREED AcceptedBetaFE
Metadata Update from @blockerbot: - Issue status updated to: Closed (was: Open)
Release F36 is no longer tracked by BlockerBugs, closing this ticket.
Login to comment on this ticket.