The criterion for this would be:
https://fedoraproject.org/wiki/Fedora_38_Final_Release_Criteria#Default_application_functionality

This happens if you click on a remote-calendar event before it has "refreshed" by going to the server and back. Which is something I often do, to double check I edited the event correctly.

I don't think the crash is that bad, honestly. You can start Calendar again, no data loss. But the hang is much worse. The window gets frozen and can't be closed using regular GUI means. You can't get rid of it, you can't restart it. For a regular user, the only option is to re-log.

FinalBlocker +1

FinalBlocker 0

Edited to go from +1 to 0. I'm not convinced that this isn't a blocker, but since the window for triggering this appears to be only a few seconds, I could live with it.

FinalFE +1

In case a fix doesn't come until after the freeze begins.

FinalBlocker -1

While an application crash isn't good, this is going to be encountered very rarely. It would be hard to justify blocking the release on it.

The hang thing scares me, and so will scare some unaware user.

FinalBlocker +1

FinalBlocker -1

Same feeling as @aday here.

I'm kinda with @aday , I think.
FinalBlocker -1

Hmm, we're sometimes criticized that we interpret the basic functionality criterion too broadly. This might be an example of it. While especially the window hang is quite annoying, you need to meet several conditions in order to trigger it (a remote calendar, event edit and then a fast click on it). This is probably not "basic".

FinalBlocker -1

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