public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Alec Warner <antarus@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] glibc-2.16 moving to ~arch
Date: Mon, 20 Aug 2012 16:43:37 +0200	[thread overview]
Message-ID: <CAAr7Pr9BF-_U_Os7r+4xt+3euD0Yc-oHU=47Barq5HgNpFCHHw@mail.gmail.com> (raw)
In-Reply-To: <CAGfcS_me230uT_9gq_0G0uXFW1VJSNBgktF9kO+oZHabj2NeuQ@mail.gmail.com>

On Mon, Aug 20, 2012 at 4:27 PM, Rich Freeman <rich0@gentoo.org> wrote:
> On Mon, Aug 20, 2012 at 10:14 AM, Alec Warner <antarus@gentoo.org> wrote:
>>
>> I think part of Mike's point is that time and time again has proven
>> that the way to a mans heart^H^H^H^H to get things fixed is to break
>> them. The aforementioned example of a tracker open for months with no
>> progress is an example of halted progress. If we waited to fix all
>> known issues prior to launch, then we would never launch. This is very
>> common in software development. Some features are v2 features, some
>> bugs are not worth fixing. Some bugs we will fix with a patch
>> post-launch; I don't see how this is any different.
>>
>
> 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.

>
> If the announcement were that we have a tracker and some languishing
> bugs, and we'd like to push to get them closed in two weeks I'd feel
> differently.

I can't really say Mike is the shining example of how we should
communicate; but then again, neither am I :)

-A

>
> Rich
>


  reply	other threads:[~2012-08-20 14:45 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 [this message]
2012-08-20 14:54             ` Rich Freeman
2012-08-20 19:30               ` Mike Frysinger
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='CAAr7Pr9BF-_U_Os7r+4xt+3euD0Yc-oHU=47Barq5HgNpFCHHw@mail.gmail.com' \
    --to=antarus@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