From Fedora Project Wiki
(System-wide change proposal for glibc.)
 
(Removed IBM ppc64le float128 mention.)
 
(6 intermediate revisions by 2 users not shown)
Line 38: Line 38:


== Current status ==
== Current status ==
* Targeted release: [[Releases/28 | Fedora 28]]  
* Targeted release: [[Releases/29 | Fedora 29]]  
* Last updated: 2018-04-30
* Last updated: 2018-04-30
<!-- After the change proposal is accepted by FESCo, tracking bug is created in Bugzilla and linked to this page  
<!-- After the change proposal is accepted by FESCo, tracking bug is created in Bugzilla and linked to this page  
Line 48: Line 48:
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:
* Tracker bug: [https://bugzilla.redhat.com/show_bug.cgi?id=1598403 #1598403]
* Release Notes tracking: [https://pagure.io/fedora-docs/release-notes/issue/191 #191]


== Detailed Description ==
== Detailed Description ==
<!-- Expand on the summary, if appropriate.  A couple sentences suffices to explain the goal, but the more details you can provide the better. -->
<!-- Expand on the summary, if appropriate.  A couple sentences suffices to explain the goal, but the more details you can provide the better. -->
The GNU C Library version 2.28 will be released at the beginning of August 2018; we have started closely tracking the glibc 2.28 development code in Fedora Rawhide and are addressing any issues as they arise. Given the present schedule Fedora 29 will branch after the GLIBC 2.28 upstream release. However, the mass rebuild schedule means Fedora 29 will mass rebuild (if required) just after GLIBC 2.28 upstream freezes ABI for release, so careful attention must be paid to any last minute ABI changes.
The GNU C Library version 2.28 will be released at the beginning of August 2018; we have started closely tracking the glibc 2.28 development code in Fedora Rawhide and are addressing any issues as they arise. Given the present schedule Fedora 29 will branch after the GLIBC 2.28 upstream release. However, the mass rebuild schedule means Fedora 29 will mass rebuild (if required) just after GLIBC 2.28 upstream freezes ABI for release, so careful attention must be paid to any last minute ABI changes.
This change also includes the following changes:
* [[Changes/PPC64LE_Float128_Transition | IBM POWER LE transition to Float128 for long double. ]]


== Benefit to Fedora ==
== Benefit to Fedora ==
Line 66: Line 64:
<!-- What work do the feature owners 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 the feature owners 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?-->


* Other developers: Developers need to ensure that rawhide is stable and ready for the Fedora 28 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.<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
* Other developers: Developers need to ensure that rawhide is stable and ready for the Fedora 29 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.<!-- REQUIRED FOR SYSTEM WIDE 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?-->
<!-- 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?-->


Line 134: Line 132:
Release Notes are not required for initial draft of the Change Proposal but has to be completed by the Change Freeze.  
Release Notes are not required for initial draft of the Change Proposal but has to be completed by the Change Freeze.  
-->
-->
* Release Notes tracking: [https://pagure.io/fedora-docs/release-notes/issue/191 #191]
The GNU C Library version 2.28 will be released at the beginning of August 2018. 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.28 will be released at the beginning of August 2018. 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


[[Category:ChangeAcceptedF28]]
[[Category:ChangeAcceptedF29]]
<!-- 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 -->

Latest revision as of 15:23, 5 July 2018


The GNU C Library version 2.28

Summary

Switch glibc in Fedora 29 to glibc version 2.28.

Owner

  • Name: Carlos O'Donell
  • Email: carlos@redhat.com
  • Release notes owner: carlos@redhat.com
  • Release notes ticket:

Current status

Detailed Description

The GNU C Library version 2.28 will be released at the beginning of August 2018; we have started closely tracking the glibc 2.28 development code in Fedora Rawhide and are addressing any issues as they arise. Given the present schedule Fedora 29 will branch after the GLIBC 2.28 upstream release. However, the mass rebuild schedule means Fedora 29 will mass rebuild (if required) just after GLIBC 2.28 upstream freezes ABI for release, so careful attention must be paid to any last minute ABI changes.

Benefit to Fedora

Stays up to date with latests security and bug fixes from glibc upstream.

Scope

  • Proposal owners: Update glibc to 2.28 from tested upstream release.
  • Other developers: Developers need to ensure that rawhide is stable and ready for the Fedora 29 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.
  • Release engineering: #7475 : The Fedora Toolchain team is responsible for ensuring that Fedora Rawhide stabilizes ABI before a Fedora release, or that after the branch that the Fedora release is rebased (a very small rebase) to the final released version. This is a requirement for Fedora to inherit the ABI and API guarantees provided by upstream. If a mass rebuild is required by glibc or other components, the Fedora Toolcahin team will ensure coordination with release engineering such that a mass rebuild uses the released version of glibc to fix any last minute ABI changes. A mass rebuild is not required and this is communicated to release engineering.
  • Policies and guidelines: The policies and guidelines do not need to be updated.
  • Trademark approval: Not needed for this change

Upgrade/compatibility impact

The library is backwards compatible with the version of glibc that was shipped in Fedora 27.

Some packaging changes required, see: https://sourceware.org/glibc/wiki/Release/2.28#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.28.

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 2500+ tests that run to verify the correct operation of the library. In the future we'll also be running the microbenchmark to look for performance regressions as well as behavioural ones.

User Experience

Users will see improved performance, many bugfixes and improvements to POSIX compliance, additional locales, etc. The glibc 2.28 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.28, no show-stopper problems are expected. At this point, we can still revert to upstream version 2.27 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 2018-08-01.
  • Blocks release? 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

  • Release Notes tracking: #191

The GNU C Library version 2.28 will be released at the beginning of August 2018. 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