On Wed, Feb 10, 2021 at 12:47:25PM -0500, Ben Cotton wrote: > == Contingency Plan == > * Contingency mechanism: moving this change to Fedora 36, if not > successfully finished until Fedora 35 branching from Rawhide > * Contingency deadline: Fedora 35 branching from Rawhide (2021-08-10) > * Blocks release? No What is the final decision wrt. to compat package creation? With 190 packages failing to build, I think it's very likely that at least some of those will still fail to build 5 months from now. The contingency mechanism, as described, would be to postpone the update to F36 at that point. I think this is not desirable, not least because it doesn't guarantee that we will not have a very similar situation *12* months from now. So instead, I'd very much propose to plan that a compat package will be created, and that *some* packages will require autoconf-2.69, and if they do, switch them over to use the compat package. *If* it turns out early enough that the compat package is not needed, we can skip it. Overall, I think things would go much smoother this way. With the current plan, by creating a flag day, we're actually making it harder to develop against 2.71, because it'll not be available in Fedora until *everything* has been switched over. Zbyszek _______________________________________________ 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
