On Fri, Dec 2, 2022 at 11:13 PM Richard Shaw <hobbes1069@xxxxxxxxx> wrote: > > On Fri, Dec 2, 2022 at 3:30 PM Adam Williamson <adamwill@xxxxxxxxxxxxxxxxx> wrote: >> >> >> What does everyone else think? Has the time come? Or is there more we >> need to do to make side tags usable for all cases before getting rid of >> overrides? > > > I wasn't aware of the CI issues so that seems like the last nail in the coffin. The only time I've used one recently is because I forgot about a package dependency and it was easier to create a buildroot override than look up how to re-tag the build into a side tag. That has been my experience as well: Use on-demand side-tags for everything, and use buildroot overrides only when using a side-tag would be very inconvenient (i.e. tagging in builds that were already submitted as another update into another side tag). But I don't think buildroot overrides are really *necessary* for any workflows anymore, either ... Not sure if we should turn them off entirely, but we could restrict their use somewhat? For example, only allow people in "releng" or "qa" groups to file them. Fabio _______________________________________________ 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
