Learn more about these different git repos.
Other Git URLs
This ticket will be used for requesting pushes of tested blocker / freeze exception fixes during F37 release freezes. See https://fedoraproject.org/wiki/QA:SOP_blocker_bug_process and https://fedoraproject.org/wiki/QA:SOP_freeze_exception_bug_process . Similar to candidate compose request tickets, this ticket can be closed by releng after each push and re-opened by QA each time a new push is needed.
First request:
== Freeze exceptions ==
Done.
Metadata Update from @kevin: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
A few more to go:
Metadata Update from @adamwill: - Issue status updated to: Open (was: Closed)
One more:
== Blockers ==
Sorry, missed one. Full request:
actually just hang fire for now, might be a couple more things soon.
And now there's one more:
Done!
Some more to go:
Couple more:
For the record, the exact set of things that was in the 1.5 candidate compose needed pushing stable after Beta:
I believe @kevin already did this, so not re-opening the ticket, just recording for posterity.
Actually @humaton did it... but yeah, should be done. ;)
(can't reopen the ticket, but...)
Metadata Update from @kparal: - Issue status updated to: Open (was: Closed)
I pushed this yesterday and forgot to close the ticket. :)
Adam is on PTO, I'd like to request to push the following updates stable:
On top of the comment above, bunch of more:
Kevin is on PTO, we need somebody else from infra/releng to handle this. Folks?
I'm back and just pushed these.
@humaton should have been able to, but he must have missed it.
Here are some more to go:
Pushed.
Metadata Update from @humaton: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Several more to go:
Done
Couple of pushes, I want to do these now so the next IoT and CoreOS builds match RC 1.2:
There are a few more to go. Please note the gnome-software update has been obsoleted, but we still need to push exactly this version of gnome-software, please do whatever is necessary to achieve this.
I pushed the rpm ones and then manually tagged the gnome-software one directly into f37 (so bodhi's state is a lie here, but it seemed the easiest way to get this done). Still can't see how to push modules stable, so I left the avacado ones out.
I then figured out you can pass --updates to bodhi to pass it update id's... so I was able to use that to push those 2 modular updates. ;)
A couple more to go. There are several other candidates, but they're in the "shiny things" bucket and we should probably strategize/test a bit more before we push those stable. This just includes the security fix stuff we definitely want to go stable ASAP.
Re-opening for a few more not-shiny-new-stuff pushes:
Few more to go. @mattdm signed off on pushing kernel 6 and Firefox 106 stable at this point.
Hmm. https://dl.fedoraproject.org/pub/fedora/linux/development/37/Everything/x86_64/os/Packages/k/ still has kernel-5.19.16-301.fc37.x86_64.rpm
yes, it won't be there until after the next nightly compose. that's how it works until we create the separate updates repo after Go.
Time for some more things to go stable, crossing fingers that they don't have any bad bugs we didn't spot. Note I haven't been able to submit the KDE mega-update for stable - I think its size might be screwing with Bodhi, every time I try I get a 504 timeout. But it does have sufficient karma to go stable, I believe.
Last one to go, this should put us level with RC-1.7 if I'm counting right:
Login to comment on this ticket.