< Changes
m (Jreznik moved page Features/GLIBC218 to Changes/GLIBC218: Features are now Changes) |
(A few minor edits, empty release notes owner (docs guys should pick it up) etc.) |
||
| Line 33: | Line 33: | ||
* Name: [[User:Codonell|Carlos O'Donell]] | * Name: [[User:Codonell|Carlos O'Donell]] | ||
* Email: carlos@redhat.com | * Email: carlos@redhat.com | ||
* Release notes owner: | * Release notes owner: | ||
<!-- Include you email address that you can be reached should people want to contact you about helping with your change, status is requested, or technical issues need to be resolved. If the change proposal is owned by a SIG, please also add a primary contact person. --> | <!-- Include you email address that you can be reached should people want to contact you about helping with your change, status is requested, or technical issues need to be resolved. If the change proposal is owned by a SIG, please also add a primary contact person. --> | ||
<!--- UNCOMMENT only for Changes with assigned Shepherd (by FESCo) | <!--- UNCOMMENT only for Changes with assigned Shepherd (by FESCo) | ||
| Line 63: | Line 62: | ||
== Scope == | == Scope == | ||
<!-- What work do the developers have to accomplish to complete the change 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 developers have to accomplish to complete the change 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?--> | ||
* Proposal owners: Update glibc to 2.18 from tested upstream release. | |||
<!-- 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: | * Other developers: N/A (not a System Wide Change) <!-- 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 80: | Line 77: | ||
<!-- 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 19. | The library is backwards compatible with the version of glibc that was shipped in Fedora 19. | ||
== How To Test == | == How To Test == | ||
Revision as of 14:46, 8 July 2013
GLIBC 2.18
Summary
Switch GLIBC in Fedora 20 to GLIBC version 2.18
Owner
- Name: Carlos O'Donell
- Email: carlos@redhat.com
- Release notes owner:
Current status
- Targeted release: Fedora 20
- Last updated: 2013-07-08
- Tracker bug: <will be assigned by the Wrangler>
Detailed Description
GLIBC 2.18 will be released at the end of July 2013; we have started closely tracking the GLIBC 2.18 development code in Fedora Rawhide and are addressing any issues as they arise. There should be little difference from the users perspective between GLIBC 2.17 used in F19 and GLIBC 2.18 used in F20.
Benefit to Fedora
Stays up to date with latests bug fixes from glibc.
Scope
- Proposal owners: Update glibc to 2.18 from tested upstream release.
- Other developers: N/A (not a System Wide Change)
- Release engineering: N/A (not a System Wide Change)
- Policies and guidelines: N/A (not a System Wide Change)
Upgrade/compatibility impact
The library is backwards compatible with the version of glibc that was shipped in Fedora 19.
How To Test
GLIBC has its own testsuite, which is run during the package build, plus many other packages with automated tests also help to test the new GLIBC.
User Experience
Users will see improved performance, many bugfixes and improvements to POSIX compliance, additional locales, etc.
Dependencies
All packages do not need to be rebuilt.
Contingency Plan
- Contingency mechanism: Given that Rawhide has started tracking GLIBC 2.18, no show-stopper problems are expected. In the unlikely event a major problem were discovered, we could fall back to the older GLIBC 2.17 from Fedora 19.
- Contingency deadline: N/A (not a System Wide Change)
- Blocks release? N/A (not a System Wide Change), No
Documentation
The glibc manual contains the documentation for the release and doesn't need any more additional work.
Release Notes
The glibc 2.18 NEWS file will contain all the relevant release notes and will be available once 2.18 is released in the next couple of weeks (2013-07-08). You can see the current NEWS entry here: http://sourceware.org/git/?p=glibc.git;a=blob_plain;f=NEWS;hb=HEAD