Bug details: https://bugzilla.redhat.com/show_bug.cgi?id=1879127 Information from BlockerBugs App: <img alt="1879127" src="https://qa.fedoraproject.org/blockerbugs/api/v0/bugimg/1879127" />
The votes have been last counted at 2021-01-19 13:13 UTC and the last processed comment was #comment-710474
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
Unless I'm doing something wrong, I believe the FinalBlocker is clear: FinalBlocker +1
I'm not sure about a BetaBlocker, I'll like to hear your thoughts: https://bugzilla.redhat.com/show_bug.cgi?id=1879127#c8
FinalBlocker +1
I'm less confident about BetaBlocker (leaning toward -1, especially given where we are in the schedule). I asked two questions in the bug that will help inform my decision there.
I'm at least:
BetaFE +1 FinalBlocker +1
If you're not sure you're +1 beta blocker, you can at least vote on BetaFE...
BetaFE +1
AGREED AcceptedBetaFE
The following votes have been closed:
So, Adam claims that the Beta criterion only covers direct repository URLs and not metalinks or mirrorlists. I proposed a clarification in my thread on test list, so that we're not confused in the future. Anyway, it seems we currently have no reason to block Beta on this.
BetaBlocker -1
This will cause issues later FinalBlocker +1
Metadata Update from @blockerbot: - Issue status updated to: Closed (was: Open)
Release F33 is no longer tracked by BlockerBugs, closing this ticket.
Login to comment on this ticket.