FinalBlocker -1

@frantisekz You should always provide some justification for your decision. Please provide one, thanks.

@frantisekz You should always provide some justification for your decision. Please provide one, thanks.

That isn't necessary as "doesn't violate any/mentioned release criteria" can be implied (and I'd comment in bugzilla if it was "can't reproduce" problem).

If you think this doesn't violate any criteria, please tell us next time. I can't see into your head, it wasn't clear to me. Thanks.

I guess it can be interpreted both ways, but I'd say it can be seen as violating the "Default panel functionality" ( https://fedoraproject.org/wiki/Fedora_38_Final_Release_Criteria#Default_panel_functionality ). If you want to spin this another way, since the bug is timing sensitive it also could be interpreted of violating the "Update notification" ( https://fedoraproject.org/wiki/Fedora_38_Final_Release_Criteria#Update_notification ), because the notification would not get shown.

To be fair, I do understand that it is not possible to fix everything and that it is hard to decide whether something is really critical or not.

AGREED RejectedFinalBlocker

Discussed during the 2023-04-03 blocker review meeting: [0]

The decision to classify this bug as a "RejectedBlocker (Final)" was made as it was agreed this is just too much of a corner case to constitute a violation of the panel or update notification criteria.

[0] https://meetbot.fedoraproject.org/fedora-blocker-review/2023-04-03/f38-blocker-review.2023-04-03-16.01.txt

The following votes have been closed:

• Rejected FinalBlocker (+0, 0, -1)
  • -1 by frantisekz

Release F38 is no longer tracked by BlockerBugs, closing this ticket.