On Wed, Apr 14, 2021 at 1:13 PM Brandon Nielsen <nielsenb@xxxxxxxxxxx> wrote: > > On 4/13/21 9:39 AM, Ben Cotton wrote: > [Snip] > > > >> There must be no SELinux denial notifications or crash notifications on boot of or during installation from a release-blocking live image, or at first login after a default install of a release-blocking desktop. > > > > Of course, we can always adjust this criterion in the future. > > > [Snip] > > Does that make this[0] a blocker candidate? Probably more likely this final release criterion: All system services present after installation with one of the release-blocking package sets must start properly, unless they require hardware which is not present. https://fedoraproject.org/wiki/Fedora_34_Final_Release_Criteria#System_services > Somewhat related, is there some mapping of compose test cases to release > criterion? Or the inverse? Something like "Failures of test case foo, > bar, and baz may constitute a violation of release criterion qux"? I'm pretty sure it's all contained to the Basic, Beta, and Final release criteria pages. -- 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 Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
