|| ||"Jared K. Smith" <jsmith-AT-fedoraproject.org> |
|| ||Development discussions related to Fedora <devel-AT-lists.fedoraproject.org> |
|| ||Re: glibc policy chage? |
|| ||Mon, 6 Feb 2012 06:11:11 -0500|
|| ||Article, Thread
2012/2/6 Michał Piotrowski <firstname.lastname@example.org>:
> I noticed that F17 is based on the latest stable glibc realease.
> Previously development Fedora version was based on development glibc.
> Was there a change of some Fedora glibc policy? If it is no
> coincidence, but the new policy - many thanks for the change :)
Yes, we've worked with the glibc maintainers in Fedora to change the
way that glibc packages are produced. Previously, each new updated
glibc package would sync in most (if not all) of the latest changes
from development, which made it difficult to release. For example, in
the F16 development cycle, we had several instances of bug-fix
releases for glibc causing further regressions.
In the new scheme, glibc packages will be based on stable releases,
with bug-fixes back-ported as necessary. I'll throw out a huge thank
you to Jeff Law for being willing to step up and take over maintenance
of the glibc packages in Fedora, and for building those packages in a
less chaotic way than was previously done.
Fedora Project Leader
devel mailing list
to post comments)