On Mon, Nov 11, 2019 at 4:01 AM Miro Hrončok <mhroncok@xxxxxxxxxx> wrote: > > Before you do this, can we figure out the details? > > 1. Do we use bodhi to handle the freeze? > > Previously, this would not be possible, as bodhi was not yet "activated" at > branching, however with rawhide gating (and hopefully "branched gating" soon), > we could. > I'd defer to releng to determine what the best way to handle this is. > 2. Who handles freeze exceptions, is it releng, QA? > That's a great question. The point of this freeze isn't testing, it's getting a successful compose, so I would leave it in releng's hands. I don't see that it needs the freeze exception process that we use for releases. Of course QA and everyone else can help in determining what packages need to be updated to fix the compose. > 3. How are the freeeze exceptions handled, via bugzilla? What are the tracker > bugz? Or manually in https://pagure.io/releng/failed-composes/issues ? > There or in the main releng tracker. Whatever makes Mohan and Kevin happiest. (Or the least unhappy). None of this is to throw the problem over the wall and say "it's releng's problem now!" It's more of "I trust them to come up with the best solution since they're the ones closest to the problem." -- Ben Cotton He / Him / His Fedora Program Manager Red Hat TZ=America/Indiana/Indianapolis _______________________________________________ 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
