On Mon, Dec 5, 2022 at 2:58 PM Ben Cotton <bcotton@xxxxxxxxxx> wrote: > > * Release engineering: Mass rebuild required Please file a ticket with Release Engineering if you haven't already. > == Contingency Plan == > * Contingency mechanism: (What to do? Who will do it?) If too many > packages are found to be broken at runtime, the default for > fortification will be left at `_FORTIFY_SOURCE=2` for Fedora 38. > Change owner will do this in `redhat-rpm-config` > > * Contingency deadline: Beta freeze Would a full mass rebuild be required to invoke the contingency mechanism, or would we just need to rebuild affected packages? In either case (but definitely if a full mass rebuild is required), I'm concerned that this contingency deadline is too late in the schedule. Branch day (2023-02-07) seems like it would be a better fit. -- 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 Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue