From: Mike Frysinger <vapier@gentoo.org>
To: libc-alpha@sourceware.org
Subject: Re: glibc 2.24 --- Release on August 1st (hard deadline).
Date: Wed, 13 Apr 2016 20:07:00 -0000 [thread overview]
Message-ID: <20160413200746.GN6588@vapier.lan> (raw)
In-Reply-To: <56FD2577.6060407@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1004 bytes --]
On 31 Mar 2016 09:26, Carlos O'Donell wrote:
> I would like to suggest that we release glibc 2.24 on August 1st
> 2016 and consider this a hard deadline.
>
> This suggestion is strongly motivated by the accelerated Fedora 25
> schedule which could use a stable glibc 2.24 released on August 1st
> to synchronize with an Alpha Freeze on August 9th [1].
>
> This request is not out of line with the expected schedule. The
> glibc schedule is nominally February 1st / August 1st (after
> having shifted it to avoid the holiday season, starting with 2.19
> in 2014).
>
> We are somewhat lax in the exact release date, but for the 2.24
> release I'm asking that we be firm and release on August 1st. I'm
> happy to help the RM review patches leading up to this point.
>
> The 2.23 release was only 18 days behind the expected schedule,
> but that's 18 days we will lose in 2.24 development.
Gentoo is rarely concerned by specific release dates,
so any schedule works for us.
-mike
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
prev parent reply other threads:[~2016-04-13 20:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-31 13:26 Carlos O'Donell
2016-03-31 20:13 ` Adam Conrad
2016-03-31 20:18 ` Adhemerval Zanella
2016-04-13 18:24 ` Carlos O'Donell
2016-03-31 20:25 ` Zack Weinberg
2016-04-13 18:22 ` Carlos O'Donell
2016-03-31 21:41 ` Aurelien Jarno
2016-04-04 7:49 ` Andreas Schwab
2016-04-13 20:07 ` Mike Frysinger [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160413200746.GN6588@vapier.lan \
--to=vapier@gentoo.org \
--cc=libc-alpha@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).