This is the mail archive of the
mailing list for the glibc project.
Re: glibc 2.20 status?
- From: Allan McRae <allan at archlinux dot org>
- To: "Carlos O'Donell" <carlos at redhat dot com>, GNU C Library <libc-alpha at sourceware dot org>, Siddhesh Poyarekar <siddhesh at redhat dot com>, Roland McGrath <roland at hack dot frob dot com>, Andreas Schwab <schwab at linux-m68k dot org>, David Holsgrove <david dot holsgrove at xilinx dot com>, Kaz Kojima <kkojima at rr dot iij4u dot or dot jp>, Thomas Schwinge <thomas at codesourcery dot com>, Chris Metcalf <cmetcalf at tilera dot com>
- Cc: Andreas Jaeger <aj at suse dot com>, "Joseph S. Myers" <joseph at codesourcery dot com>, Maxim Kuvyrkov <maxim at kugelworks dot com>, Alexandre Oliva <aoliva at redhat dot com>
- Date: Thu, 04 Sep 2014 12:03:19 +1000
- Subject: Re: glibc 2.20 status?
- Authentication-results: sourceware.org; auth=none
- References: <54071FF4 dot 2090203 at redhat dot com>
On 04/09/14 00:04, Carlos O'Donell wrote:
> What's the status of 2.20?
> Are -Wundef fixes and machine maintainer testing
> all that blocks the release?
I was waiting for the CVE-2014-6040 fix to land to avoid all
distributions backporting it. With that done, I intend to call a
My opinion on the -Wundef fixes is that they needed to have been
committed by this point. It has now been two months since the start of
the slushy freeze. I consider the risk/reward ratio too high to commit
them now (even with small risk, the reward is smaller).
Given I can not deal with the release until the weekend, I am happy for
the tilegx fix to land before then.
Unless anyone yells very loudly (and for a good reason...), I intend to
call a freeze on Saturday in order for the release to be made on Monday.