Bug details: https://bugzilla.redhat.com/show_bug.cgi?id=2057184 Information from BlockerBugs App: <img alt="2057184" src="https://qa.fedoraproject.org/blockerbugs/api/v0/bugimg/2057184" />
Commented but haven't voted yet: coremodule
The votes have been last counted at 2022-03-07 22:33 UTC and the last processed comment was #comment-784836
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 don't understand what the user impact is here. Just the log messages?
BetaFE 0
for now. The fix seems safe enough, but it also seems like the sort of thing that could just land in updates?
Discussed during the 2022-02-28 blocker review meeting: [0]
The decision to delay the classification of this as a blocker bug was made as we're not entirely sure how serious of a problem this is, and hence whether it's worth a freeze exception. We'll ask the maintainer for his opinion in the bug report and discuss this again next week or in the ticket.
[0] https://meetbot.fedoraproject.org/fedora-blocker-review/2022-02-28/f36-blocker-review.2022-02-28-17.00.txt
AGREED RejectedBetaFE
Discussed during the 2022-03-07 blocker review meeting: [0]
The decision to classify this bug as a "RejectedFreezeException (Beta)" was made as per feedback from the maintainer, this is not a major bug and it's fine to fix it with an update.
[0] https://meetbot.fedoraproject.org/fedora-blocker-review/2022-03-07/f36-blocker-review.2022-03-07-17.01.txt
The following votes have been closed:
Metadata Update from @blockerbot: - Issue status updated to: Closed (was: Open)
Release F36 is no longer tracked by BlockerBugs, closing this ticket.
Log in to comment on this ticket.