Bug details: ** https://bugzilla.redhat.com/show_bug.cgi?id=2186117 ** Information from BlockerBugs App:
Commented but haven't voted yet: kparal, frantisekz
The votes have been last counted at 2023-04-12 15:39 UTC and the last processed comment was #comment-851291
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
As I already described in the bug report, this has been the case in all past releases at least for a few years back. So unless this time it's somehow different, I don't see a reason to block on this. (Also, I don't see a release criterion for this).
But some improvement in this process would certainly be welcome.
FinalBlocker -1
Works as designed
As I already described in the bug report, this has been the case in all past releases at least for a few years back. So unless this time it's somehow different, I don't see a reason to block on this.
Yeah, I probably didn't try that pre-release in the past releases, but it makes sense.
(Also, I don't see a release criterion for this).
I guess that would the basic functionality when one of the two buttons don't work.
FinalBlocker -1 AGREED RejectedFinalBlocker
The following votes have been closed:
Metadata Update from @blockerbot: - Issue status updated to: Closed (was: Open)
Release F38 is no longer tracked by BlockerBugs, closing this ticket.
Log in to comment on this ticket.