This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: Code freeze for glibc-2.19
- From: Allan McRae <allan at archlinux dot org>
- To: Maxim Kuvyrkov <maxim at kugelworks dot com>
- Cc: libc-alpha <libc-alpha at sourceware dot org>
- Date: Thu, 09 Jan 2014 10:45:02 +1000
- Subject: Re: Code freeze for glibc-2.19
- Authentication-results: sourceware.org; auth=none
- References: <52C40F69 dot 9050604 at archlinux dot org> <E0C543E6-D346-4830-A8DB-79D9B6B30A5B at kugelworks dot com>
On 09/01/14 08:54, Maxim Kuvyrkov wrote:
> On 2/01/2014, at 1:51 am, Allan McRae <allan@archlinux.org> wrote:
>
>> Community,
>>
>> The code freeze for the glibc-2.19 release was scheduled for 31 Dec 2013.
>>
>> There is still a few patches listed in the "Release blockers" section of
>> the wiki page [1]. It looks like the "Make TLS variables thread-safe"
>> patch needed changes and is large so can target 2.20. The "System z"
>> patches are all architecture specific and do not add strings so I'll
>> leave that to the architecture maintainers (under the expectation they
>> are either committed very soon or not at all).
>>
>> I do not see any other outstanding issues so code freeze is in effect
>> now with the usual rules.
>>
>> Architecture maintainers: do your thing and report status on the wiki [1].
>
> Allan,
>
> I forgot about the freeze and committed fix for BZ #16394 in https://sourceware.org/git/?p=glibc.git;a=commitdiff;h=66671c84d58d6ae705bac39dc476c3d3b2b81116 . Sorry. Let me know if you would prefer to back out the patch.
>
> Thank you,
>
Bug fixes are free to be checked in.
Allan