Hey Clement, On Tue, 2023-05-09 at 09:45 +0200, Clement Verna wrote: > > > On Mon, 8 May 2023 at 22:11, Kevin Fenzi <kevin@xxxxxxxxx> wrote: > > On Mon, May 08, 2023 at 07:57:30PM +0000, Zbigniew Jędrzejewski- > > Szmek wrote: > > > > > > I think we need some clarity wrt. to the dependency order here. > > > Let's say we: > > > > In order to do this at branch point, we will need to move > > > > building this > > > > image into the compose process and mark it blocking. > > > OK, so we build things, but then we need to publish to > > > registry.fp.o, > > > which is asynchrounous (?). When we test the newly built ISOs, do > > > > No, it happens at the end of the compose (if no blocking > > deliverables failed causing the compose to fail) > > If we do this, we should also make the container base images release > blocking since AFAIK they are currently not release blocking. Yes, that's a good point. The OCI base images aren't currently listed as release-blocking deliverables: https://docs.fedoraproject.org/en-US/releases/f39/blocking/ ... but if this Change goes through, then they will implicitly become release-blocking deliverables because the fedora-toolbox images are based on them. Should we explicitly mention this in the Change? Or, something else? Or, is it fine as it is? Thanks, Rishi _______________________________________________ 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
