public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Mike Frysinger <vapier@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] glibc-2.16 moving to ~arch
Date: Mon, 20 Aug 2012 15:30:43 -0400	[thread overview]
Message-ID: <201208201530.44091.vapier@gentoo.org> (raw)
In-Reply-To: <CAGfcS_mRbSnypWEQOcnED-u0m94qacyj-8HDq=KDKw+Rvm2tdw@mail.gmail.com>

[-- Attachment #1: Type: Text/Plain, Size: 1153 bytes --]

On Monday 20 August 2012 10:54:03 Rich Freeman wrote:
> On Mon, Aug 20, 2012 at 10:43 AM, Alec Warner <antarus@gentoo.org> wrote:
> > On Mon, Aug 20, 2012 at 4:27 PM, Rich Freeman <rich0@gentoo.org> wrote:
> >> I agree with your point.  I'm fine with setting deadlines and such,
> >> but my main concern is that the first deadline shouldn't be two days
> >> after it is announced.
> > 
> > The tracker has been open since July 4th.
> 
> Yes, and it does not contain any deadlines at all (not even the one
> announced on the mailing list).

glibc is on a known release period (~every 6 months).  i posted some time ago 
that Gentoo will be rolling along as well:
 - have a version in the stable pipeline
 - have a version in the unstable pipeline
 - have a version in the masked pipeline
as versions in the lower pipeline clear out, the next one will be moving into 
place.  so while exact times haven't been posted (because i don't have them), 
glibc versions will continue to be released, so maintainers can't sit on their 
bugs.  2.15 has gone stable which means there's now room for 2.16 which has 
largely settled down.
-mike

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  reply	other threads:[~2012-08-20 19:32 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-18  3:31 [gentoo-dev] glibc-2.16 moving to ~arch Mike Frysinger
2012-08-18  5:16 ` Diego Elio Pettenò
2012-08-18  5:44   ` Mike Frysinger
2012-08-18  5:50     ` Tiziano Müller
2012-08-18  6:08       ` Diego Elio Pettenò
2012-08-18  6:01     ` Diego Elio Pettenò
2012-08-18 15:42       ` Mike Frysinger
2012-08-18 15:49         ` Diego Elio Pettenò
2012-08-18 16:00           ` Mike Frysinger
2012-08-18 16:22             ` Nathan Zachary
2012-08-18 15:50         ` [gentoo-dev] " Nikos Chantziaras
2012-08-19  8:41 ` [gentoo-dev] " Luca Barbato
2012-08-20  3:07   ` Mike Frysinger
2012-08-20  3:13     ` Diego Elio Pettenò
2012-08-20 11:09     ` Rich Freeman
2012-08-20 14:14       ` Alec Warner
2012-08-20 14:27         ` Rich Freeman
2012-08-20 14:43           ` Alec Warner
2012-08-20 14:54             ` Rich Freeman
2012-08-20 19:30               ` Mike Frysinger [this message]
2012-10-02 19:53 ` Mike Frysinger
2012-10-30  7:22   ` Mike Frysinger
2012-10-30 14:44     ` Diego Elio Pettenò
2012-10-30 15:21       ` Rich Freeman
2012-10-30 15:32         ` Diego Elio Pettenò
2012-10-30 17:46       ` [gentoo-dev] " Duncan
2012-10-30 17:56         ` Diego Elio Pettenò
2012-10-30 22:33           ` Duncan

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=201208201530.44091.vapier@gentoo.org \
    --to=vapier@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.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