Bug details: ** https://bugzilla.redhat.com/show_bug.cgi?id=2008537 ** Information from BlockerBugs App:
Commented but haven't voted yet: frantisekz, pbrobinson
The votes have been last counted at 2021-10-06 19:41 UTC and the last processed comment was #comment-756736
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
FinalBlocker +1 FinalFE +1
Updating my blocker vote based on a comment from pbrobinson
FinalBlocker -1 FinalFE +1
It looks like there is a patch already, so blocker status seems irrelevant here.
5.14.10 will release on Oct 6th, and should be pushed to updates-testing by the 7th, though that is after freeze.
AGREED AcceptedFinalFE
See https://meetbot-raw.fedoraproject.org/fedora-blocker-review/2021-10-04/f35-blocker-review.2021-10-04-16.02.html .
The following votes have been closed:
So the reason I feel this is a blocker is that it affects the install media and can't fixed with an update. It can change how the HW looks so and in some cases what HW actually works and we're changing that experience and when run from the installer stuff may not work at all.
It is purely academic, as 5.14.10 will be pushed this week with the revert included. Since we have an FE, it doesn't matter that much
Yes, and no, I've had FE's dropped with kernels in the past because of other implications, and 5.14.10 is looking big, so until it's in the f35 tag it's really not purely academic. I've had things drop that affect arm in the past that were FE so unless there's another kernel blocker, which I don't see currently, I don't agree with that sentiment.
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.