On Mon, Apr 01, 2024 at 05:47:10PM +0000, Gary Buhrmaster wrote: > It does bring up a potential point that perhaps > Fedora should have an additional repo (let's > call it "emergency fixes") that is not community > mirrored (so any mirrors for load sharing > would be fully controlled by the project), with > a short refresh time, and containing only > packages that need to get out immediately. > If a critical fix needs to get out to the > community it could be (almost) immediately > available. After a few days (when public > mirrors would be expected to have updated) > those packages could be removed (reducing > the load on this repo). For the next time, of > course (and there will be a next time, there > is always a next time).
https://pagure.io/releng/issue/5886 (This was after Heartbleed, FWIW.) > -- > _______________________________________________ > devel mailing list -- devel@lists.fedoraproject.org > To unsubscribe send an email to devel-le...@lists.fedoraproject.org > 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@lists.fedoraproject.org > Do not reply to spam, report it: > https://pagure.io/fedora-infrastructure/new_issue -- Matthew Miller <mat...@fedoraproject.org> Fedora Project Leader -- _______________________________________________ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org 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@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
