On Tue, Oct 18, 2022 at 02:45:32AM +0200, Adam Williamson wrote: > First off, I'm actually finding the time to do the sky-castle work. The > releng critpath script now outputs critpath data by group: > https://pagure.io/releng/c/621caa542acc142d57f1247e7644846f737f8eee?branch=main > > Bodhi (git HEAD Bodhi, anyway) can now read data in that format: > https://github.com/fedora-infra/bodhi/pull/4755 > > and when this PR is merged, it will be able to mark updates as critpath > by groups: > https://github.com/fedora-infra/bodhi/pull/4759
Nice! > Second, since nobody really opposed the idea of extending the critpath > definition slightly, here's a formal proposal to implement that. I want > to edit the wiki critpath page: > https://fedoraproject.org/wiki/Critical_path_package > > and change it as follows: > > 1. Under Background, change "The packages required to sustain these > actions make up the critical path." to: > > "The packages required to sustain these actions initially made up the > critical path. Later, it was agreed that the maintainers of Editions, > spins, and labs can also declare packages that provide other key > functionality to be part of the ''critical path'' for that Edition, > spin or lab." > > 2. Under Actions, change the first two sentences to read: > > "Packages required to perform the most fundamental actions on a system > are always considered part of the ''critical path''. Those actions > include: " +1. Zbyszek _______________________________________________ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org 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@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
