On Wed, 2023-05-03 at 15:08 +0200, Kamil Paral wrote: > > > and must keep > > being updated like for branchpoints, beta and final. Missing images or > > broken images, will be blocking the release. > > > > I think this is just assumed, as described above, for each release-blocking > artifact. Honestly, I thought we have some criterion saying "all > release-blocking artifacts must exist" or something along those lines, but > I haven't found it :-) > > Adam, am I looking wrong? I pretty much consider it to be implied: an image that doesn't exist doesn't meet *any* of the criteria that apply to it, so we can cite just about any criterion. It *is* more explicitly mentioned in the automatic blockers bit, too: "Bugs which entirely prevent the composition of one or more of the release-blocking images required to be built for a currently-pending (pre-)release" https://fedoraproject.org/wiki/QA:SOP_blocker_bug_process#Automatic_blockers So I would say it's not necessary to specify this explicitly in the new criteria. We may want to adjust the "Release-blocking images must boot" and "Expected image boot behavior" blocks at https://fedoraproject.org/wiki/Basic_Release_Criteria#Release-blocking_images_must_boot , though. -- Adam Williamson (he/him/his) Fedora QA Fedora Chat: @adamwill:fedora.im | Mastodon: @adamw@xxxxxxxxxxxxx https://www.happyassassin.net _______________________________________________ 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, report it: https://pagure.io/fedora-infrastructure/new_issue
