I think our current criteria are not that extensive as Neal suggests:
https://fedoraproject.org/wiki/Basic_Release_Criteria#Guest_on_current_stable_release
https://fedoraproject.org/wiki/Fedora_36_Beta_Release_Criteria#Self_hosting_virtualization

For example, we don't block on clipboard sharing, and that's enabled by default. So I'd say that file sharing (not enabled by default) is not covered either. However, I'm not clear on how important the mentioned developer use cases are. (Of course, if the dev use cases are very important, we can specify virtio file sharing explicitly in the criterion and block on this).

I use Virtiofs pretty frequently in a developer context, but I don't see a criteria covering it.

FinalBlocker -1

I agree with @kparal here. If we totally think that this is so much important to block a release on it, then let's dicuss it and possibly create a criterion to handle this.

Until then, I am

FinalBlocker -1

I agree with my learnèd colleagues:

FinalBlocker -1

Although I'd support an F37 criterion that covers this.

FinalFE +1

because we should fix it if we can

FinalBlocker -1
FinalFE +1

FinalBlocker -1

AGREED RejectedFinalBlocker We don't have release criterion that covers this issue.

The following votes have been closed:

• Rejected FinalBlocker (+0, 0, -5)
  • -1 by nielsenb, lruzicka, bcotton, frantisekz, kparal

FinalFE +1

AGREED AcceptedFinalFE

Discussed using the asynchronous bug tracking platform: [0]

The decision to classify this bug as an "AcceptedFreezeException (Final)" was made as it is a noticeable issue that cannot be fixed with an update.

[0] https://qa.fedoraproject.org/blockerbugs/

The following votes have been closed:

• Accepted FinalFreezeException (+3, 0, -0)
  • +1 by bcotton, frantisekz, ngompa

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