On Wed, 2022-02-16 at 21:43 +0100, Kevin Kofler via devel wrote: > Adam Williamson wrote: > > Since the builds have been in a compose, we can't untag them from > > Rawhide, we can only move forwards. > > Why can we not make an exception to this stubborn policy in cases like this? > We did not have this rule a few years ago and things worked out just fine. > And these days, we have distro-sync, which should make the version going > backwards a non-issue. AFAIK we've always had that rule. It's always been policy that we don't untag once a build has been in a successful compose. I don't think this changed "a few years ago", unless I'm misremembering. Anyhow, things should be all fixed up now, at least I'm writing this from the f36-gnome tag and nothing's exploded yet. -- Adam Williamson Fedora QA IRC: adamw | Twitter: adamw_ha https://www.happyassassin.net _______________________________________________ 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 on the list, report it: https://pagure.io/fedora-infrastructure
