Bug details: ** https://bugzilla.redhat.com/show_bug.cgi?id=1931345 ** Information from BlockerBugs App:
Commented but haven't voted yet: kparal, coremodule
The votes have been last counted at 2021-03-01 21:15 UTC and the last processed comment was #comment-718445
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
I believe we rejected this as a blocker in the last cycle. IIRC we said that at least one option for backtrace generation must work - either remotely or locally. Can somebody find records?
BetaBlocker -1 BetaFE +1
AGREED RejectedBetaBlocker
Discussed during the 2021-03-01 blocker review meeting: [0]
The decision to classify this bug as a "RejectedBlocker (Beta)" and delay the classification of this bug as a Final Blocker was made as per precedent from last cycle, we only require at least one backtrace generation method (local or remote) to work per the criteria, however it's a close call whether remote retrace not working should block final, and we don't have a lot of people around to make it, so we agreed to delay the decision until it's more pressing / more folks are around to consider it.
[0] https://meetbot.fedoraproject.org/fedora-blocker-review/2021-03-01/f34-blocker-review.2021-03-01-17.01.txt
The following votes have been closed:
Metadata Update from @blockerbot: - Issue status updated to: Closed (was: Open)
Release F34 is no longer tracked by BlockerBugs, closing this ticket.
Log in to comment on this ticket.