On Tue, Jun 29, 2021 at 2:07 PM Ben Cotton <bcotton@xxxxxxxxxx> wrote: > > == Contingency Plan == > * Contingency mechanism: If glibc 2.34 provides too disruptive to > compiling the distribution we could revert to 2.33, but given that > Rawhide has started tracking glibc 2.34, no show-stopper problems are > expected. At this point, we can still revert to upstream version 2.33 > if insurmountable problems appear, but to do so may require a mass > rebuild to remove new symbols from the ABI/API. > * Contingency deadline: Upstream glibc ABI freeze deadline of 2021-07-01. > I notice that the listed contingency deadline is two days from now, so it will have passed before this even makes it to FESCo for vote. Is that date correct? -- 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 on the list, report it: https://pagure.io/fedora-infrastructure
