Bug details: https://bugzilla.redhat.com/show_bug.cgi?id=2017043 Information from BlockerBugs App: <img alt="2017043" src="https://qa.fedoraproject.org/blockerbugs/api/v0/bugimg/2017043" />
Commented but haven't voted yet: coremodule
The votes have been last counted at 2021-10-25 18:17 UTC and the last processed comment was #comment-759010
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
FinalFreezeException +1
I think we need to work on it
AGREED RejectedFinalBlocker AGREED AcceptedFinalFE
Discussed during the 2021-10-25 blocker review meeting: [0]
The decision to classify this bug as a "RejectedBlocker (Final)" and an "AcceptedFreezeException (Final)" was made as there doesn't seem to a be blocking scenario (hardware plus input device plus environment) which is affected, but accepted as an FE issue as it cannot be fixed with an update and would be good to fix for the non-blocking RPi4 case if possible.
[0] https://meetbot.fedoraproject.org/fedora-blocker-review/2021-10-25/f35-blocker-review.2021-10-25-16.02.txt
The following votes have been closed:
Metadata Update from @blockerbot: - Issue status updated to: Closed (was: Open)
Release F35 is no longer tracked by BlockerBugs, closing this ticket.
Login to comment on this ticket.