This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: glibc 2.18: One month left!
- From: "Carlos O'Donell" <carlos at redhat dot com>
- To: "Ryan S. Arnold" <ryan dot arnold at gmail dot com>
- Cc: Andreas Jaeger <aj at suse dot com>, GNU C Library <libc-alpha at sourceware dot org>
- Date: Thu, 09 May 2013 14:43:32 -0400
- Subject: Re: glibc 2.18: One month left!
- References: <517968C4 dot 9030503 at redhat dot com> <518BBEF9 dot 8050006 at suse dot com> <CAAKybw9SRGGo5Pg8sawOxrwSqRcsAj0GkDUJxbRGOcV4Tn2+wQ at mail dot gmail dot com>
On 05/09/2013 11:36 AM, Ryan S. Arnold wrote:
> On Thu, May 9, 2013 at 10:21 AM, Andreas Jaeger <aj@suse.com> wrote:
>> On 04/25/2013 07:32 PM, Carlos O'Donell wrote:
>>>
>>> Community,
>>>
>>> The GNU C Library version 2.18 is planned to release
>>> at the end of June.
>>>
>>> That leaves a little over one month of active development
>>> and up to one month of stabilization.
>>>
>>> Enjoy your freedom while it lasts :-)
>>
>>
>> Looking at bugzilla and the email archives, I noticed quite some pings - and
>> patches that were unreviewed.
>>
>> I propose that everybody with patches older than 3 weeks without review,
>> send them again and hope a few of us step up to review them finally.
>>
>> I also encourage distributions to look for patches that they care and send
>> them in for review,
>
> Would it be helpful if we created bugzillas for 2.18 'features' that
> we want in place (and already have, or will have patches for) by the
> deadline?
Bugzilla is for bugs, though I can understand how a placeholder bug
would prevent the release from going out.
However I think it best if you simply put your feature on the 2.18
release page so that we review the feature status before 2.18 goes out.
http://sourceware.org/glibc/wiki/Release/2.18
Cheers,
Carlos.