Bug details: https://bugzilla.redhat.com/show_bug.cgi?id=1880499
Commented but haven't voted yet: chrismurphy, kparal, coremodule
The votes have been last counted at 2020-09-24 19:29 UTC and the last processed comment was #comment-688238
To learn how to vote, see: https://pagure.io/fedora-qa/blocker-review
BetaBlocker +1
This will affect some devices heavily
BetaBlocker +1 😢😢😢
I faced the same...
Playing devil's advocate. The bug is with Fedora 32, so this would be a PreviousRelease blocker, correct? If IoT isn't blocking for Fedora 32, and is newly blocking for Fedora 33 going forward, then I'd say it's not a blocker bug. If upgrades from 32 are release blocking, what about from 31?
PreviousRelease
The bug is with Fedora 32, so this would be a PreviousRelease blocker, correct?
If the fix needs to happen in F32 (it seems so), then it is a PreviousRelease blocker, yes. So the proper vote here is to cast PreviousRelease +1/0/-1.
PreviousRelease +1/0/-1
If IoT isn't blocking for Fedora 32, and is newly blocking for Fedora 33 going forward, then I'd say it's not a blocker bug. If upgrades from 32 are release blocking, what about from 31?
Well played :smirk: Yes, since IoT is release blocking only from F33, I don't think we should block on issues affecting earlier releases. F33 should be the starting line from where we guarantee functionality, and we should be very clear about this in our release notes. Fortunately IoT uses ostree, so the upgraded system should be the same as a freshly installed system, which makes our position here easier - we won't need to deal with some F33 systems behaving a different way just because they were upgraded.
Therefore my current opinion leans towards rejecting this a PreviousRelease blocker. But I'll wait for more opinions on this general approach before I cast my vote.
AGREED RejectedBetaBlocker
Discussed during the 2020-09-24 Fedora 33 Go/No-Go meeting: [0]
The decision to classify this bug as a "RejectedBlocker (Beta)" was made as it affects a small group of users, is in a beta, is an edge case, and we expect it to be fixed soon.
[0] https://meetbot-raw.fedoraproject.org/fedora-meeting-1/2020-09-24/f33-beta-go_no_go-meeting.2020-09-24-17.00.txt
The following votes have been closed:
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.