I'm noticing the only release criterion that has secure boot listed is an exception for Windows dual booting that I think is obsolete: https://fedoraproject.org/wiki/Fedora_32_Final_Release_Criteria#Windows_dual_boot The bootloader entry part of this criterion does not apply when Secure Boot is enabled (because it has not yet been made to work, and fixing it is not trivial). cases. I ran into that while trying to find a criterion for this bug being a blocker: https://bugzilla.redhat.com/show_bug.cgi?id=1782778 The inability to boot UEFI VMs seems like a blocker, but I have to infer it from the pull down: https://fedoraproject.org/wiki/Fedora_32_Beta_Release_Criteria#Virtualization_requirements "What does that mean? This rather concise criterion means effectively means that both virtual host and virtual guest functionality must work - it's implied, if you think about it. It also means that there must be no showstopper bugs in the installer when installing to a virtual machine..." But since there's no explicit statement, I could also make the case that these days we should also block on bugs related to Secure Boot in VMs, now that there's explicit support for it upstream. *shrug* -- Chris Murphy _______________________________________________ test mailing list -- test@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to test-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@xxxxxxxxxxxxxxxxxxxxxxx
