(Autoconf 2.69 -> 2.71 upgrade) |
No edit summary |
||
Line 22: | Line 22: | ||
== Current status == | == Current status == | ||
[[Category: | [[Category:ChangeReadyForWrangler]] | ||
<!-- When your change proposal page is completed and ready for review and announcement --> | <!-- When your change proposal page is completed and ready for review and announcement --> | ||
<!-- remove Category:ChangePageIncomplete and change it to Category:ChangeReadyForWrangler --> | <!-- remove Category:ChangePageIncomplete and change it to Category:ChangeReadyForWrangler --> |
Revision as of 10:29, 5 February 2021
Change Proposal Name
Autoconf 2.69 -> 2.71 upgrade
Summary
Upgrading autoconf from version 2.69 to the last upstream version 2.71.
Owner
- Name: Ondrej Dubaj
- Email: odubaj@redhat.com
Current status
- Targeted release: f35 or f36
- Last updated: 2021-02-05
- FESCo issue: <will be assigned by the Wrangler>
- Tracker bug: <will be assigned by the Wrangler>
- Release notes tracker: <will be assigned by the Wrangler>
Detailed Description
Upgrading autoconf from version 2.69 to version 2.71 according to new upstream release. Version 2.70 is skipped due to multiple ABI incompatibilities, where some of them were fixed in version 2.71. Years of development differ these two releases, so problems are expected.
Feedback
Benefit to Fedora
Brings a stable and up-to-date version of autoconf according to upsteam release. It is expected, that in the future many upstream development teams will use autoconf-2.71 as their default builder, so we should be prepared for such a step.
Scope
- Proposal owners:
- Other developers:
- Release engineering: #Releng issue number
- Policies and guidelines: N/A (not needed for this Change)
- Trademark approval: N/A (not needed for this Change)
- Alignment with Objectives:
Affects hundreds of packages.
Upgrade/compatibility impact
How To Test
Rebuilding your packages with autoconf-2.71 dependency. For testing, copr can be used https://copr.fedorainfracloud.org/coprs/odubaj/autoconf-2.70/packages/
User Experience
Dependencies
Contingency Plan
- Contingency mechanism: (What to do? Who will do it?) N/A (not a System Wide Change)
- Contingency deadline: N/A (not a System Wide Change)
- Blocks release? N/A (not a System Wide Change), Yes/No
Documentation
N/A (not a System Wide Change)