From Fedora Project Wiki
(Add releng ticket, please subscribe to it)
 
(4 intermediate revisions by 2 users not shown)
Line 47: Line 47:
 
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: [https://bugzilla.redhat.com/show_bug.cgi?id=BBBBBBB #BBBBBBB]
+
* Tracker bug: [https://bugzilla.redhat.com/show_bug.cgi?id=1474902 #1474902]
  
 
== Detailed Description ==
 
== Detailed Description ==
Line 62: Line 62:
 
<!-- 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: DJ Delorie <dj@redhat.com>, Florian Weimer <fweimer@redhat.com>, Torvald Riegel <triegel@redhat.com>, Martin Sebor <msebor@redhat.com>, Patsy Franklin <pfrankli@redhat.com> and Arjun Shankar <arjun@redhat.com>, no other developers are required. These developers need to ensure that rawhide is stable and ready for the Fedora 27 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 27 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?-->
  
 
* Release engineering: [https://pagure.io/releng/issue/6890] All Fedora releases must be released using a released version of glibc. The Fedora glibc 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 glibc 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. The GNU C Library (glibc) does not require a mass rebuild for this release. <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
 
* Release engineering: [https://pagure.io/releng/issue/6890] All Fedora releases must be released using a released version of glibc. The Fedora glibc 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 glibc 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. The GNU C Library (glibc) does not require a mass rebuild for this release. <!-- 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 rebuid required?  If a rel-eng ticket exists, add a link here.  -->
 
<!-- Does this feature require coordination with release engineering (e.g. changes to installer image generation or update package delivery)?  Is a mass rebuid required?  If a rel-eng ticket exists, add a link here.  -->
 +
 +
** [[Fedora_Program_Management/ReleaseBlocking/Fedora{{FedoraVersionNumber|next}}|List of deliverables]]: all
  
 
* Policies and guidelines: The policies and guidelines do not need to be updated. <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
 
* Policies and guidelines: The policies and guidelines do not need to be updated. <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
 
<!-- Do the packaging guidelines or other documents need to be updated for this feature?  If so, does it need to happen before or after the implementation is done?  If a FPC ticket exists, add a link here. -->
 
<!-- Do the packaging guidelines or other documents need to be updated for this feature?  If so, does it need to happen before or after the implementation is done?  If a FPC ticket exists, add a link here. -->
 +
 +
* Trademark approval: Not needed for this change
  
 
== Upgrade/compatibility impact ==
 
== Upgrade/compatibility impact ==
Line 129: Line 133:
 
The GNU C Library version 2.26 will be released at the beginning of August 2017. 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.26 will be released at the beginning of August 2017. 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:ChangeReadyForWrangler]]
+
[[Category:ChangeAcceptedF27]]
 
<!-- 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:22, 25 July 2017


The GNU C Library version 2.26

Summary

Switch glibc in Fedora 27 to glibc version 2.26.

Owner

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

Current status

Detailed Description

The GNU C Library version 2.26 will be released at the beginning of August 2017; we have started closely tracking the glibc 2.26 development code in Fedora Rawhide and are addressing any issues as they arise. Given the present schedule Fedora 27 will branch after the GLIBC 2.26 upstream release. However, the mass rebuild schedule means Fedora 27 will mass rebuild just after GLIBC 2.26 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.26 from tested upstream release.
  • Other developers: Developers need to ensure that rawhide is stable and ready for the Fedora 27 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: [1] All Fedora releases must be released using a released version of glibc. The Fedora glibc 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 glibc 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. The GNU C Library (glibc) does not require a mass rebuild for this release.
  • 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 26.

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

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.26 NEWS update will include more details.

Dependencies

All packages do not need to be rebuilt, but for IBM POWER, particularly ppc64le we will be migrating from a long double that uses IBM double-double format to IEEE-754 128-bit long double. This is an ABI transition for ppc64le and will be backwards compatible, but the two ABIs will not interoperate, so an application needs to choose one or the other.

Contingency Plan

  • Contingency mechanism: Given that Rawhide has started tracking GLIBC 2.26, no show-stopper problems are expected. At this point, we can still revert to upstream version 2.25 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 2017-07-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

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