(Mention strlcpy/strlcat) |
|||
| (6 intermediate revisions by 3 users not shown) | |||
| Line 50: | Line 50: | ||
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=1308553 #1308553] | ||
== Detailed Description == | == Detailed Description == | ||
| Line 76: | Line 76: | ||
== Upgrade/compatibility impact == | == Upgrade/compatibility impact == | ||
<!-- What happens to systems that have had a previous versions of Fedora installed and are updated to the version containing this change? Will anything require manual configuration or data migration? Will any existing functionality be no longer supported? --> | <!-- What happens to systems that have had a previous versions of Fedora installed and are updated to the version containing this change? Will anything require manual configuration or data migration? Will any existing functionality be no longer supported? --> | ||
The library is backwards compatible with the version of glibc that was shipped in Fedora 23 | The library is backwards compatible with the version of glibc that was shipped in Fedora 23. | ||
No packaging changes required, see: | No packaging changes required, see: | ||
| Line 105: | Line 105: | ||
<!-- What other packages (RPMs) depend on this package? Are there changes outside the developers' control on which completion of this change depends? In other words, completion of another change owned by someone else and might cause you to not be able to finish on time or that you would need to coordinate? Other upstream projects like the kernel (if this is not a kernel change)? --> | <!-- What other packages (RPMs) depend on this package? Are there changes outside the developers' control on which completion of this change depends? In other words, completion of another change owned by someone else and might cause you to not be able to finish on time or that you would need to coordinate? Other upstream projects like the kernel (if this is not a kernel change)? --> | ||
<!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | ||
All packages do not need to be rebuilt. | |||
The librtkaio removal (https://fedoraproject.org/wiki/Changes/GLIBC223_librtkaio_removal) proposal will depend on the glibc 2.23 update. | The librtkaio removal (https://fedoraproject.org/wiki/Changes/GLIBC223_librtkaio_removal) proposal will depend on the glibc 2.23 update. | ||
| Line 132: | Line 132: | ||
The GNU C Library version 2.23 will be released at the end of February 2016. 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.23 will be released at the end of February 2016. 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: | [[Category:ChangeAcceptedF24]] | ||
<!-- 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 13:53, 15 February 2016
The GNU C Library version 2.23
Summary
Switch glibc in Fedora 24 to glibc version 2.23.
Owner
- Name: Carlos O'Donell
- Email: carlos@redhat.com
- Release notes owner:
Current status
Detailed Description
The GNU C Library version 2.23 will be released at the end of February 2016; we have started closely tracking the glibc 2.23 development code in Fedora Rawhide and are addressing any issues as they arise. Given the present schedule Fedora 24 will branch before GLIBC 2.23. Fedora 24 will be rebased on the stable GLIBC 2.23 release.
Benefit to Fedora
Stays up to date with latests security and bug fixes from glibc.
Scope
- Proposal owners: Update glibc to 2.23 from tested upstream release.
- Other developers: Aside from Carlos O'Donell <carlos@redhat.com>, Florian Weimer <fweimer@redhat.com>, Torvald Riegel <triegel@redhat.com>, Martin Sebor <msebor@redhat.com>, and Patsy Franklin <pfrankli@redhat.com>, no other developers are required. These developers need to ensure that rawhide is stable and ready for the Fedora 24 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: In general coordination with release engineering is not required. A mass rebuild is not required.
- Policies and guidelines: The policies and guidelines do not need to be updated.
Upgrade/compatibility impact
The library is backwards compatible with the version of glibc that was shipped in Fedora 23.
No packaging changes required, see: https://sourceware.org/glibc/wiki/Release/2.23#Packaging_Changes
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 1000+ 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.23 NEWS update will include more details.
Dependencies
All packages do not need to be rebuilt.
The librtkaio removal (https://fedoraproject.org/wiki/Changes/GLIBC223_librtkaio_removal) proposal will depend on the glibc 2.23 update.
Contingency Plan
- Contingency mechanism: Given that Rawhide has started tracking GLIBC 2.23, no show-stopper problems are expected. In the unlikely event a major problem were discovered, we could fall back to the older glibc 2.22 and release with that.
- Contingency deadline: Beta freeze.
- 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 upraded. 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.23 will be released at the end of February 2016. 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