public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Toon Moene <toon@moene.indiv.nluug.nl>
To: Neil Booth <neil@daikokuya.demon.co.uk>
Cc: Mark Mitchell <mark@codesourcery.com>, gcc@gcc.gnu.org
Subject: Re: GCC 3.1 Release
Date: Sat, 13 Apr 2002 07:50:00 -0000	[thread overview]
Message-ID: <3CB823A0.136EF4E3@moene.indiv.nluug.nl> (raw)
In-Reply-To: <20020413091819.GA16217@daikokuya.demon.co.uk>

Neil Booth wrote:

> Mark Mitchell wrote:-

> > I have a proposal before the SC to slip the GCC 3.2 schedule even
> > further; so that the first phase of GCC 3.2 development will now end
> > one month  beyond the release of GCC 3.1 -- June 1st -- pushing the
> > GCC 3.2  release date back to October 1st so as to give people time to
> > work on major changes for GCC 3.2 *after* GCC 3.1 is released.
> 
> IMO this is still too short; I think there should be two months after
> the previous release for the first phase, giving us an 8-month cycle
> instead of a 6-month one.

The problem with Mark's "mental model" of the release process is that
bug fixing doesn't screech to a grinding halt the moment 3.1 is out.

Because then a whole group of "new" testers comes along and finds new
bugs that we (and our "regular" testers) haven't found.  For 3.0 this
effect was so bad that basically only the 3.0.4 release can be described
as "generally useful".

I do not have a good solution to that problem.

-- 
Toon Moene - mailto:toon@moene.indiv.nluug.nl - phoneto: +31 346 214290
Saturnushof 14, 3738 XG  Maartensdijk, The Netherlands
Maintainer, GNU Fortran 77: http://gcc.gnu.org/onlinedocs/g77_news.html
Join GNU Fortran 95: http://g95.sourceforge.net/ (under construction)

  reply	other threads:[~2002-04-13 12:25 UTC|newest]

Thread overview: 80+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-12 18:51 Mark Mitchell
2002-04-13  2:21 ` Neil Booth
2002-04-13  7:50   ` Toon Moene [this message]
2002-04-13  8:40     ` Tim Prince
2002-04-13 23:07     ` Bryce McKinlay
2002-04-14 17:04       ` David Edelsohn
2002-04-15 17:19         ` David O'Brien
2002-04-15 18:02           ` David Edelsohn
2002-04-16 17:06           ` Marc Espie
2002-04-22 19:44       ` David O'Brien
2002-04-22 20:11         ` Bryce McKinlay
2002-04-23 11:04           ` David O'Brien
2002-04-23 16:15             ` Bryce McKinlay
2002-04-22 22:25         ` Kaveh R. Ghazi
2002-04-14  1:33     ` H . J . Lu
2002-04-16 17:00     ` Marc Espie
2002-04-17  2:08       ` Gerald Pfeifer
2002-05-17  5:42         ` Marc Espie
2002-05-17 16:19           ` Loren James Rittle
2002-05-17 17:07             ` David O'Brien
2002-05-17 17:08               ` Marc Espie
2002-04-13 13:18 ` Tom Tromey
2002-04-14  6:59   ` Jason Merrill
2002-04-14  7:25     ` Andreas Jaeger
2002-04-14  8:16       ` Jason Merrill
2002-04-15 10:56     ` Geoff Keating
2002-04-15 11:19       ` H . J . Lu
2002-04-16 15:16         ` mark
2002-04-16 15:23           ` H . J . Lu
2002-04-17  2:54             ` Andreas Schwab
2002-04-15 11:36       ` Andreas Jaeger
2002-04-15 11:37         ` Joe Buck
2002-04-15 13:13         ` Geoff Keating
2002-04-15 12:00 ` Andreas Jaeger
2002-04-15 12:01   ` Mark Mitchell
2002-04-15 12:13     ` Michael Matz
2002-04-15 12:22       ` Mark Mitchell
2002-04-15 14:52 ` Geoff Keating
2002-04-15 15:01   ` Mark Mitchell
  -- strict thread matches above, loose matches on Subject: below --
2002-05-05 11:37 Mark Mitchell
2002-05-05 15:00 ` Florian Weimer
2002-05-06  3:24   ` Andreas Schwab
2002-05-06  7:54     ` Mark Mitchell
2002-05-06  7:57       ` Andreas Schwab
2002-05-06 15:16         ` Mark Mitchell
2002-05-07  1:43           ` Andreas Schwab
2002-04-15 15:06 Richard Kenner
2002-04-14 10:34 Robert Dewar
2002-04-13 13:51 Robert Dewar
2002-04-03 23:20 John David Anglin
2002-04-03  2:38 Reichelt
2002-04-03 13:21 ` Mark Mitchell
2002-04-02 14:38 Mark Mitchell
2002-04-02 14:47 ` Tom Tromey
2002-04-03 15:06 ` Phil Edwards
2002-04-03 16:08   ` Joe Buck
2002-04-03 17:57     ` Phil Edwards
2002-04-04 10:17     ` Mark Mitchell
2002-04-09  9:48       ` Joe Buck
2002-04-09 10:44         ` Benjamin Kosnik
2002-04-09 11:35         ` Gabriel Dos Reis
2002-04-10  2:37         ` Mark Mitchell
2002-04-10  7:59           ` Joe Buck
2002-04-10  8:17             ` Gabriel Dos Reis
2002-04-10  8:22               ` Joe Buck
2002-04-10 10:14             ` Mark Mitchell
2002-04-10 11:39               ` Benjamin Kosnik
2002-04-10 11:47                 ` Paolo Carlini
     [not found]                   ` <flwuvfqrme.fsf@jambon.cmla.ens-cachan.fr>
2002-04-12  5:12                     ` Paolo Carlini
2002-04-10 13:01                       ` Gabriel Dos Reis
2002-04-11  6:02                         ` Joe Buck
2002-04-11 14:58                           ` Gabriel Dos Reis
2002-04-15 17:51               ` Gabriel Dos Reis
2002-04-15 19:36                 ` Gabriel Dos Reis
2002-04-15 19:43                 ` Mark Mitchell
2002-04-15 20:03                   ` Gabriel Dos Reis
2002-04-06  7:47 ` Jason Merrill
2002-04-10 10:17 ` Janis Johnson
2002-04-10 10:24   ` Mark Mitchell
2002-04-10 10:35   ` Christian Jönsson

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=3CB823A0.136EF4E3@moene.indiv.nluug.nl \
    --to=toon@moene.indiv.nluug.nl \
    --cc=gcc@gcc.gnu.org \
    --cc=mark@codesourcery.com \
    --cc=neil@daikokuya.demon.co.uk \
    /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).