On Mon, Oct 04, 2021 at 10:57:42AM +0200, Vít Ondruch wrote: > Thoughts?
I like the idea! We can block such a package from ever appearing in a compose in pungi. So, perhaps we seperate it into: <pre packager> open a bug, submit a pr, do a scratch build, look at ci <sponsored into packager> get added as commit to onboarding package create pr, merge pr, do official build, submit update, etc Another possible way we could do this is have this setup in our staging env. ie, they do the same things, but it's in staging (which we never compose anyhow). That has the danger of something being broken in stg without us realizing it, or them diverging. Great idea tho, I like it. kevin
signature.asc
Description: PGP signature
_______________________________________________ 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 on the list, report it: https://pagure.io/fedora-infrastructure
