otaylor added a new comment to an issue you are following:
``
Also, there are questions around Bodhi and workflow - if we decide that we need the builds
to not be garbage collected:
* Do we require packagers to do Bodhi updates for Flatpak modules after bodhi activation
to get them into the tag? Do we add something to bodhi's Flatpak support so that the
module tagging follows the container tagging?
* The flatpak-common module I'm working on adds another wrinkle to this that
makes my head hurt - as soon as you build flatpak-common, subsequent Flatpak container
builds will pull packages from that build, so if we're saving the builds for history,
that flatpak-common build needs to be tagged. This gets super-complicated!
And are there going to be other non-Flatpak modules like this - that are container-only
and we want to exclude from the modular compose? If so, it might make more sense to
exclude them at *compose* time, and not have to create separate tags, bodhi releases,
etc.
``
To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/7827