On Mon, Nov 11, 2019 at 09:51:33AM -0500, Ben Cotton wrote:
On Mon, Nov 11, 2019 at 4:01 AM Miro Hrončok
> 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"
> branching, however with rawhide gating (and hopefully "branched gating"
> we could.
I'd defer to releng to determine what the best way to handle this is.
When we do branching we adjust koji targets and tags. My thought was to
do the adjustments, but disable some part of the workflow. Either
collect packages in the tag to be signed, or collect them in the tag to
be autosubmitted to gating by bodhi. Then, once a compose is done,
restart that process and process the backlog. If a package is needed for
a fix, it can manually be tagged in.
> 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.
I think this should be completely up to releng. They should only land
things they need to get the compose working.
> 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).
releng tracker... but users should not make exceptions normally, it
should only be things needed to make the compose work.
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."
Yep. I agree...