This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: Development timeline for glibc 2.17 (code freeze in one week!)
- From: Andrew Pinski <pinskia at gmail dot com>
- To: "Carlos O'Donell" <carlos at systemhalted dot org>
- Cc: GNU C Library <libc-alpha at sourceware dot org>, David Miller <davem at davemloft dot net>
- Date: Mon, 29 Oct 2012 19:43:30 -0700
- Subject: Re: Development timeline for glibc 2.17 (code freeze in one week!)
- References: <CAE2sS1gSKBWAx4zpxV_cr1n+wcroH7+rdA7eppTj2Eb+3B-2Wg@mail.gmail.com>
On Mon, Oct 29, 2012 at 6:31 AM, Carlos O'Donell
<carlos@systemhalted.org> wrote:
> Community,
>
> The current glibc 2.17 release process timeline [1] is as follows:
>
> November:
> 1st week - Freeze. Testing starts.
> 2nd week - Send the updated libc.pot upstream for translation.
> 3rd week - More testing.
> 4th week - Tag 2.17 and update POT.
>
> December:
> 1st week - Release 2.17.
>
> Does anyone have any comments or concerns?
I hope the aarch64 port can make it before the release. I don't have
a link to the patch though.
Thanks,
Andrew Pinski
>
> Dave,
>
> Are you still available to be the release manager for 2.17
> and shepherd the release process?
>
> The biggest mistake I always make is to assume I have to
> do everything myself. I'm here, and so are many others to
> assist with the release process. Please remember that
> this is only the 2nd time we've gone through the new
> process. The notes in [2] might not be completely coherent
> or self-consistent.
>
> Thanks for your help.
>
> Cheers,
> Carlos.
>
> [1] http://sourceware.org/glibc/wiki/Glibc%20Timeline
> [2] http://sourceware.org/glibc/wiki/Release