(Create release glibc 2.32 in August 2020) |
(Restructure based on new template.) |
||
| Line 43: | Line 43: | ||
== Current status == | == Current status == | ||
[[Category:ChangePageIncomplete]] | |||
<!-- When your change proposal page is completed and ready for review and announcement --> | |||
<!-- remove Category:ChangePageIncomplete and change it to Category:ChangeReadyForWrangler --> | |||
<!-- The Wrangler announces the Change to the devel-announce list and changes the category to Category:ChangeAnnounced (no action required) --> | |||
<!-- After review, the Wrangler will move your page to Category:ChangeReadyForFesco... if it still needs more work it will move back to Category:ChangePageIncomplete--> | |||
<!-- Select proper category, default is Self Contained Change --> | |||
<!-- [[Category:SelfContainedChange]] --> | |||
[[Category:SystemWideChange]] | |||
* Targeted release: [[Releases/32 | Fedora 32]] | * Targeted release: [[Releases/32 | Fedora 32]] | ||
* Last updated: <!-- this is an automatic macro — you don't need to change this line --> {{REVISIONYEAR}}-{{REVISIONMONTH}}-{{REVISIONDAY2}} | * Last updated: <!-- this is an automatic macro — you don't need to change this line --> {{REVISIONYEAR}}-{{REVISIONMONTH}}-{{REVISIONDAY2}} | ||
| Line 52: | Line 62: | ||
CLOSED as NEXTRELEASE -> change is completed and verified and will be delivered in next release under development | CLOSED as NEXTRELEASE -> change is completed and verified and will be delivered in next release under development | ||
--> | --> | ||
* Tracker bug: | * FESCo issue: <will be assigned by the Wrangler> | ||
* Release notes tracker: | * Tracker bug: <will be assigned by the Wrangler> | ||
* Release notes tracker: <will be assigned by the Wrangler> | |||
== Detailed Description == | == Detailed Description == | ||
| Line 98: | Line 109: | ||
<!-- What work do other developers have to accomplish to complete the feature in time for release? Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?--> | <!-- What work do other developers have to accomplish to complete the feature in time for release? Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?--> | ||
* Release engineering: [https://pagure.io/releng/ | <!-- See Toolchain example: https://pagure.io/releng/issue/9040 --> | ||
* Release engineering: [https://pagure.io/releng/issues #] <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | |||
<!-- Does this feature require coordination with release engineering (e.g. changes to installer image generation or update package delivery)? Is a mass rebuild required? include a link to the releng issue. | <!-- Does this feature require coordination with release engineering (e.g. changes to installer image generation or update package delivery)? Is a mass rebuild required? include a link to the releng issue. | ||
The issue is required to be filed prior to feature submission, to ensure that someone is on board to do any process development work and testing, and that all changes make it into the pipeline; a bullet point in a change is not sufficient communication --> | The issue is required to be filed prior to feature submission, to ensure that someone is on board to do any process development work and testing, and that all changes make it into the pipeline; a bullet point in a change is not sufficient communication --> | ||
| Line 175: | Line 187: | ||
The GNU C Library version 2.32 will be released at the beginning of August 2020. The current NEWS notes can be seen here as they are added: https://sourceware.org/git/?p=glibc.git;a=blob;f=NEWS;hb=HEAD | The GNU C Library version 2.32 will be released at the beginning of August 2020. The current NEWS notes can be seen here as they are added: https://sourceware.org/git/?p=glibc.git;a=blob;f=NEWS;hb=HEAD | ||
Revision as of 19:31, 29 May 2020
The GNU C Library version 2.32
Summary
Switch glibc in Fedora 33 to glibc version 2.32.
Owner
- Name: Carlos O'Donell
- Email: carlos@redhat.com
Current status
- Targeted release: Fedora 32
- Last updated: 2020-05-29
- 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
The GNU C Library version 2.32 will be released at the beginning of August 2020; we have started closely tracking the glibc 2.32 development code in Fedora Rawhide and are addressing any issues as they arise. Given the present schedule Fedora 33 will branch after the glibc 2.32 upstream release. However, the mass rebuild schedule means Fedora 33 will mass rebuild (if required) after glibc 2.31 upstream freezes ABI for release, but before the actual release, so careful attention must be paid to any last minute ABI changes.
Benefit to Fedora
Stays up to date with latest security and bug fixes from glibc upstream.
Scope
- Proposal owners: Update glibc to 2.32.
- Other developers: Developers need to ensure that rawhide is stable and ready for the Fedora 32 branch. Given that glibc is backwards compatible and we have been testing the new glibc in rawhide it should make very little impact when updated, except for the occasional deprecation warnings and removal of legacy interfaces from public header files.
- Release engineering: #
- Policies and guidelines: The policies and guidelines do not need to be updated.
- Trademark approval: N/A (not needed for this Change)
Upgrade/compatibility impact
The library is backwards compatible with the version of glibc that was shipped in Fedora 32.
Some packaging changes required, see: https://sourceware.org/glibc/wiki/Release/2.32#Packaging_Changes
We fully expect to fix all packaging changes in Fedora Rawhide given that glibc in Rawhide is tracking what will become glibc 2.32.
How To Test
The GNU C Library has its own testsuite, which is run during the package build and examined by the glibc developers before being uploaded. This test suite has over 6200 tests that run to verify the correct operation of the library. In the future may also run the microbenchmark to look for performance regressions.
User Experience
Users will see improved performance, many bugfixes and improvements to POSIX compliance, additional locales, etc. The glibc 2.32 NEWS update will include more details.
Dependencies
All packages do not need to be rebuilt.
Contingency Plan
- Contingency mechanism: Given that Rawhide has started tracking glibc 2.32, no show-stopper problems are expected. At this point, we can still revert to upstream version 2.31 if insurmountable problems appear, but to do so may require a mass rebuild to remove new symbols from the ABI/API.
- Contingency deadline: Upstream ABI freeze deadline of 2020-07-01.
- Blocks release? Yes, upgrading glibc does block the release. We should not ship without a newer glibc, there will be gcc and language features that depend on glibc being upgraded. Thus without the upgrade some features will be disabled or fall back to less optimal implementations.
Documentation
The glibc manual contains the documentation for the release and doesn't need any more additional work.
Release Notes
The GNU C Library version 2.32 will be released at the beginning of August 2020. The current NEWS notes can be seen here as they are added: https://sourceware.org/git/?p=glibc.git;a=blob;f=NEWS;hb=HEAD