From Fedora Project Wiki
< Changes
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
<!-- | <!-- Self Contained or System Wide Change Proposal? | ||
Use this guide to determine to which category your proposed change belongs to. | |||
Self Contained Changes are: | |||
* changes to isolated/leaf package without the impact on other packages/rest of the distribution | |||
* limited scope changes without the impact on other packages/rest of the distribution | |||
* coordinated effort within SIG with limited impact outside SIG functional area, accepted by the SIG | |||
= GLIBC 2.18 = | System Wide Changes are: | ||
* changes that does not fit Self Contained Changes category touching | |||
* changes that require coordination within the distribution (for example mass rebuilds, release engineering or other teams effort etc.) | |||
* changing system defaults | |||
For Self Contained Changes, sections marked as "REQUIRED FOR SYSTEM WIDE CHANGES" are OPTIONAL but FESCo/Wrangler can request more details (especially in case the change proposal category is | |||
improper or updated to System Wide category). For System Wide Changes all fields on this form are required for FESCo acceptance (when applies). | |||
We request that you maintain the same order of sections so that all of the change proposal pages are uniform. | |||
--> | |||
<!-- The actual name of your proposed change page should look something like: Changes/Your_Change_Proposal_Name. This keeps all change proposals in the same namespace --> | |||
= GLIBC 2.18 <!-- The name of your change proposal --> = | |||
== Summary == | == Summary == | ||
<!-- A sentence or two summarizing what this change is and what it will do. This information is used for the overall changeset summary page for each release. --> | |||
Switch GLIBC in Fedora 20 to GLIBC version 2.18 | Switch GLIBC in Fedora 20 to GLIBC version 2.18 | ||
== Owner == | == Owner == | ||
<!-- | |||
<!-- | For change proposals to quality as self-contained, owners of all affected packages need to be included here. Alternatively, a SIG can be listed as an owner if it owns all affected packages. | ||
This should link to your home wiki page so we know who you are. | |||
--> | |||
* Name: [[User:Codonell|Carlos O'Donell]] | |||
* Email: carlos@redhat.com | * Email: carlos@redhat.com | ||
* Release notes owner: [[User:Codonell|Carlos O'Donell]] carlos@redhat.com | |||
<!-- 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. --> | |||
* Email: <your email address so we can contact you, invite you to meetings, etc.> | |||
* Release notes owner: <!--- To be assigned by docs team [[User:FASAccountName| Release notes owner name]] <email address> --> | |||
<!--- UNCOMMENT only for Changes with assigned Shepherd (by FESCo) | |||
* FESCo shepherd: [[User:FASAccountName| Shehperd name]] <email address> | |||
--> | |||
== Current status == | == Current status == | ||
* Targeted release: [[Releases/20]] | * Targeted release: [[Releases/20 | Fedora 20 ]] | ||
* Last updated: 2013-07- | * Last updated: 2013-07-08 | ||
* | <!-- After the change proposal is accepted by FESCo, tracking bug is created in Bugzilla and linked to this page | ||
Bugzilla states meaning as usual: | |||
NEW -> change proposal is submitted and announced | |||
ASSIGNED -> accepted by FESCo with on going development | |||
MODIFIED -> change is substantially done and testable | |||
ON_QA -> change is code completed and could be tested in the Beta release (optionally by QA) | |||
CLOSED as NEXTRELEASE -> change is completed and verified and will be delivered in next release under development | |||
--> | |||
* Tracker bug: <will be assigned by the Wrangler> | |||
== 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. --> | |||
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. | 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 == | == Benefit to Fedora == | ||
<!-- What is the benefit to the platform? If this is a major capability update, what has changed? If this is a new functionality, what capabilities does it bring? Why will Fedora become a better distribution or project because of this proposal?--> | |||
Stays up to date with latests bug fixes from glibc. | Stays up to date with latests bug fixes from glibc. | ||
== 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?--> | |||
Updated glibc to 2.18 from tested upstream release. | Updated glibc to 2.18 from tested upstream release. | ||
* Proposal owners: [[User:Codonell|Carlos O'Donell]] carlos@redhat.com | |||
<!-- 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: [[User:Codonell|Carlos O'Donell]] carlos@redhat.com <!-- 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?--> | |||
* Release engineering: N/A (not a System Wide Change) <!-- 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. --> | |||
* Policies and guidelines: N/A (not a System Wide Change) <!-- 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. --> | |||
== 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? --> | |||
The library is backwards compatible with the version of glibc that was shipped in Fedora 19. | |||
<!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | |||
N/A (not a System Wide Change) | |||
== How To Test == | == How To Test == | ||
<!-- This does not need to be a full-fledged document. Describe the dimensions of tests that this change implementation is expected to pass when it is done. If it needs to be tested with different hardware or software configurations, indicate them. The more specific you can be, the better the community testing can be. | |||
Remember that you are writing this how to for interested testers to use to check out your change implementation - documenting what you do for testing is OK, but it's much better to document what *I* can do to test your change. | |||
A good "how to test" should answer these four questions: | |||
0. What special hardware / data / etc. is needed (if any)? | |||
1. How do I prepare my system to test this change? What packages | |||
need to be installed, config files edited, etc.? | |||
2. What specific actions do I perform to check that the change is | |||
working like it's supposed to? | |||
3. What are the expected results of those actions? | |||
--> | |||
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. | 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 == | == User Experience == | ||
<!-- If this change proposal is noticeable by its target audience, how will their experiences change as a result? Describe what they will see or notice. --> | |||
<!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | |||
Users will see improved performance, many bugfixes and improvements to POSIX compliance, additional locales, etc. | Users will see improved performance, many bugfixes and improvements to POSIX compliance, additional locales, etc. | ||
== Dependencies == | == Dependencies == | ||
All packages do not need to be | <!-- 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 --> | |||
All packages do not need to be rebuilt. | |||
== Contingency Plan == | == Contingency Plan == | ||
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. | <!-- If you cannot complete your feature by the final development freeze, what is the backup plan? This might be as simple as "Revert the shipped configuration". Or it might not (e.g. rebuilding a number of dependent packages). If you feature is not completed in time we want to assure others that other parts of Fedora will not be in jeopardy. --> | ||
* 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. | |||
<!-- When is the last time the contingency mechanism can be put in place? This will typically be the beta freeze. --> | |||
* Contingency deadline: N/A (not a System Wide Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | |||
<!-- Does finishing this feature block the release, or can we ship with the feature in incomplete state? --> | |||
* Blocks release? N/A (not a System Wide Change), No <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | |||
== Documentation == | == Documentation == | ||
<!-- Is there upstream documentation on this change, or notes you have written yourself? Link to that material here so other interested developers can get involved. --> | |||
The glibc manual contains the documentation for the release and doesn't need any more additional work. | |||
<!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | |||
== Release Notes == | == Release Notes == | ||
Fedora | <!-- The Fedora Release Notes inform end-users about what is new in the release. Examples of past release notes are here: http://docs.fedoraproject.org/release-notes/ --> | ||
<!-- The release notes also help users know how to deal with platform changes such as ABIs/APIs, configuration or data file formats, or upgrade concerns. If there are any such changes involved in this change, indicate them here. A link to upstream documentation will often satisfy this need. This information forms the basis of the release notes edited by the documentation team and shipped with the release. | |||
Release Notes are not required for initial draft of the Change Proposal but has to be completed by the Change Freeze. | |||
--> | |||
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 | |||
[[Category: | [[Category:ChangePageIncomplete]] | ||
<!-- 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 --> | ||
| Line 57: | Line 141: | ||
<!-- Select proper category, default is Self Contained Change --> | <!-- Select proper category, default is Self Contained Change --> | ||
[[Category:SystemWideChange]] | [[Category:SelfContainedChange]] | ||
<!-- [[Category:SystemWideChange]] --> | |||
Revision as of 14:11, 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: Carlos O'Donell carlos@redhat.com
- Email: <your email address so we can contact you, invite you to meetings, etc.>
- 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
Updated glibc to 2.18 from tested upstream release.
- Proposal owners: Carlos O'Donell carlos@redhat.com
- Other developers: Carlos O'Donell carlos@redhat.com
- 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.
N/A (not a System Wide Change)
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