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 F20 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 TC/RC 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, current Alpha blocker / FE fixes with sufficient karma to be pushed:
Please reopen for the next set. Thanks.
Reopening for these updates:
If you haven't started with pushing yet, please add this one too:
Looks like these are now ready to go:
and of course:
the last two for Alpha, I think.
Done. They should go out in tomorrow's compose, then we will do a normal stable push tomorrow that will land monday morning.
Re-opening for some Beta pushes:
Thanks! Also, [https://admin.fedoraproject.org/updates/kernel-3.11.6-300.fc20 kernel-3.11.6-300.fc20] could go with just one more +1, if you feel like giving it one (for [https://bugzilla.redhat.com/show_bug.cgi?id=1017683 #1017683] and [https://bugzilla.redhat.com/show_bug.cgi?id=1011714 #1011714]).
kernel now has sufficient karma to go.
Re-opening for some more:
Done. Will appear in tomorrow's branched compose.
Re-opening for some builds that was missed from RC2 as they weren't pushed stable:
pushed stable. additionally i added [https://admin.fedoraproject.org/updates/FEDORA-2013-20033/pykickstart-1.99.44-1.fc20,python-blivet-0.23.2-1.fc20,anaconda-20.25.4-1.fc20 pykickstart-1.99.44-1.fc20,python-blivet-0.23.2-1.fc20,anaconda-20.25.4-1.fc20] for multiple blockers, and mostkly to make sure that the pykickstart missed in RC2 is pulled in
It would also be good if you could kill the older anaconda and python-blivet updates so they do not squelch the newer ones: https://admin.fedoraproject.org/updates/python-blivet-0.23.3-1.fc20 and https://admin.fedoraproject.org/updates/anaconda-20.25.5-1.fc20,python-blivet-0.23.3-1.fc20 .
Re-opening for more! Of the updates that went into RC5 (which we're shipping), these two have sufficient karma to go:
These do not, but they were in RC5, so we should probably force push them stable anyhow:
I think that's everything.
Re-opening for a bunch of blocker/FE fixes with sufficient karma:
all pushed thanks
Here's some more ready to go:
Add [https://admin.fedoraproject.org/updates/FEDORA-2013-22654 NetworkManager-0.9.9.0-20.git20131003.fc20] for [https://bugzilla.redhat.com/show_bug.cgi?id=1018317 #1018317] to the list.
Couple more to go:
Also [https://admin.fedoraproject.org/updates/uboot-tools-2013.10-3.fc20 uboot-tools-2013.10-3.fc20] for [https://bugzilla.redhat.com/show_bug.cgi?id=1035926 #1035926] .
pushed stable, thanks.
Some more are ready:
Pushed stable thanks
Re-opening for the last set of updates. Whatever we have to hack in terms of karma to push these, let's just do it: they're what we're shipping, so even if they eat babies, they have to go to the release repo. If it's not too much trouble, do just eyeball check no-one edited the versions in any of the updates vs. what we put in the RC1.1 build...
I think after those, the repos are consistent with RC1.1 as shipped.
Metadata Update from @pschindl:
- Issue set to the milestone: Fedora 20 Beta
to comment on this ticket.