On Mon, Aug 29, 2022 at 03:50:02PM -0700, Adam Williamson wrote: ...snip... > > I can think of I guess four options: > > 1. Broaden the definition of the "critical path" somehow. We could just > write in that it includes FreeIPA functionality, I guess, though that > seems special purpose. We could broaden it to include any functionality > covered by the release criteria, which would be quite a big increase > but seems like a reasonable and concise definition. Or we could write > in that it includes any functionality that is exercised by the gating > openQA tests, though that seems a bit arbitrary - there's no > particularly great organizing principle to the openQA tests we choose > to run on updates, if I'm honest, it's a sort of grab bag I came up > with. I think this one is best... perhaps we could add something like 'and such package groups as working groups decide are critical to their edition' ? kevin
Attachment:
signature.asc
Description: PGP signature
_______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-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/devel@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
