public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Dave Korn <dave.korn.cygwin@googlemail.com>
To: Richard Guenther <rguenther@suse.de>
Cc: gcc@gcc.gnu.org
Subject: Re: GCC 4.5 Status Report (2009-09-19)
Date: Sun, 20 Sep 2009 01:35:00 -0000	[thread overview]
Message-ID: <4AB58A42.7030801@gmail.com> (raw)
In-Reply-To: <alpine.LNX.2.00.0909192244530.4520@zhemvz.fhfr.qr>

Richard Guenther wrote:

> The trunk is in Stage 1.  Stage 1 will end on Sep 30th.  After Stage 1
> Stage 3 follows with only bugfixes and no new features allowed. 
> Stage 3 will end Nov 30th.

  I don't think this is the best time to do that.  Trunk's been broken most of
last week and will probably not be buildable for at least several days yet, so
a big chunk of that warning period is going to be useless to many people.

> We've been accumulating quite a number of P1 bugs.  Entering Stage 3
> should allow to improve considerably here in a short time.

  So aren't we now likely to lose the first few days of what little remains of
stage 1 waiting for trunk to start working again, then have a mad rush of
people falling all over each other to get their new features in in the last
couple of days?  One of which will inevitably break trunk again and block all
the others and then stage 1 will be over and it'll all be too late?

  Ten days isn't even that much warning in the first place; it's less time
than you'd generally let elapse before pinging a patch.  Can I at least raise
the suggestion that a plan that might work well would be for us to go slush
for however long - less than a week, I'd suppose - it takes us to get trunk
really properly stable, and then push back the end of stage 1 by that amount?

    cheers,
      DaveK

  parent reply	other threads:[~2009-09-20  1:35 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-19 20:57 Richard Guenther
2009-09-19 22:03 ` Steven Bosscher
2009-09-19 22:22   ` Richard Guenther
2009-09-20  1:21   ` Geert Bosch
2009-09-20  1:00 ` Jack Howarth
2009-09-20  1:35 ` Dave Korn [this message]
2009-09-20  8:54   ` Richard Guenther
2009-09-20 11:38     ` Dave Korn
2009-09-20 11:48       ` Richard Guenther
2009-09-20 11:53         ` Dave Korn
2009-09-24 14:44           ` Jason Merrill
2009-09-24 14:50             ` Richard Guenther
2009-09-21 18:23     ` Cary Coutant
2009-09-21 18:57       ` Jack Howarth
2009-09-21 21:05         ` Cary Coutant
2009-09-21 21:10           ` Cary Coutant
2009-09-29 18:10 ` Sriraman Tallam
2009-09-29 22:08 ` Dave Korn
2009-09-29 22:59   ` Gerald Pfeifer
2009-09-30 10:40     ` Richard Guenther
2009-09-30 15:00       ` Jack Howarth
2009-10-01  0:17 ` Neil Vachharajani

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=4AB58A42.7030801@gmail.com \
    --to=dave.korn.cygwin@googlemail.com \
    --cc=gcc@gcc.gnu.org \
    --cc=rguenther@suse.de \
    /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).