This is the mail archive of the
mailing list for the glibc project.
Re: v2: The GNU C Library 2.16 release plan
- From: Allan McRae <allan at archlinux dot org>
- To: Jeff Law <law at redhat dot com>
- Cc: Carlos O'Donell <carlos_odonell at mentor dot com>, libc-alpha <libc-alpha at sourceware dot org>,Andreas Jaegar <aj at suse dot com>, Paul Eggert <eggert at cs dot ucla dot edu>, "Ryan S. Arnold" <ryan dot arnold at gmail dot com>,"H.J. Lu" <hjl dot tools at gmail dot com>, "Joseph S. Myers" <joseph at codesourcery dot com>
- Date: Fri, 11 May 2012 15:47:55 +1000
- Subject: Re: v2: The GNU C Library 2.16 release plan
- References: <4FAC3FCE.firstname.lastname@example.org> <4FAC86E4.email@example.com>
On 11/05/12 13:26, Jeff Law wrote:
> On 05/10/2012 04:23 PM, Carlos O'Donell wrote:
>> The timeline looks like this:
>> * Development freeze of trunk on Monday June 4th.
>> * Last day of active development is Sunday June 3rd.
>> * [3 weeks] Ask all machine maintainers to test and report back the
>> status of their machines.
>> * Updating ABI files so ABI check passes.
>> * Updating ULPs for the release.
>> * Regenerating any machine files that are out of date.
>> If I hear back from the machine maintainers quickly then this might
>> be as short as 1-2 days and we release early.
>> * [1 week] Between June 25th-29th I will branch master to the 2.16
>> branch and, after any last minute tweaks, tag it for a final release.
>> * The release will be made on the first week of July.
> Seems pretty reasonable. I don't see that there'll be time to dive into
> the ongoing problems with pthread_cond_wait on x86/x86_64, so the
> distros will likely continue to hack that up.
Is there a bug report open for that issue? I found various distribution
ones, but non in the glibc tracker.
Apart from that issue, the only patch in the Arch Linux package that is
not flagged for glibc-2.16 is for the assertion error in res_query.c
. This has been around since glibc-2.14 and from memory the patch in
that report is widely used.