public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Joe Buck <jbuck@synopsys.com>
To: Gabriel Dos Reis <gdr@integrable-solutions.net>
Cc: gcc@gcc.gnu.org
Subject: Re: Gabriel Dos Reis will be RM for the 3.2.2 release
Date: Thu, 23 Jan 2003 20:40:00 -0000	[thread overview]
Message-ID: <20030123101006.A6570@synopsys.com> (raw)
In-Reply-To: <m3znpswjyb.fsf@uniton.integrable-solutions.net>; from gdr@integrable-solutions.net on Thu, Jan 23, 2003 at 05:47:56AM +0100


I wrote:
> | There isn't a schedule yet; it is up to Gaby to decide.

On Thu, Jan 23, 2003 at 05:47:56AM +0100, Gabriel Dos Reis wrote:
> Well, I'd propose the following:
> 
>    o I would like to make a pre-release tarball on 2003-01-29.
> 
>    o We will have one week testing, i.e. from 2003-01-29 til 2003-02-04.
> 
>    o If no critical regression shows up, then we can do a release on
>       2003-02-05.
> 
> Comments?

One question is what the policy should be on adding anything else to
the 3.2 branch in the meantime.  My suggestion (and it's only a
suggestion) is to do something like this:

- allow fixes to problems in the 3.2 branch that don't appear in 3.2.1
  (idea: no new failures in 3.2.2 that aren't in 3.2.1, but no effort
  to fix problems that have been around for a while that haven't already
  been fixed)

- otherwise, a fix would have to have a very strong justification, it
  would fix some other regression, be important to multiple users or
  fix a bug in some significant free software package, and be low risk
  (Gaby would have to approve on such things)

I only know of one fix that might fall into the second category: Toon has
been asking for the following fix (approved by Richard) to be applied to
the 3.2 branch:

http://gcc.gnu.org/ml/gcc/2003-01/msg00689.html

The deadline for adding changes would have to be at least a day, maybe
two, before Gaby makes the tarball, to reduce the chance of a last-minute
botch.


  reply	other threads:[~2003-01-23 18:10 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-22  8:27 Joe Buck
2003-01-22 18:12 ` PATCh for " Gerald Pfeifer
2003-01-23 17:01 ` Gabriel Dos Reis
2003-01-23 20:40   ` Joe Buck [this message]
2003-01-24  1:41     ` Gabriel Dos Reis
2003-01-24  8:03       ` Mark Mitchell
2003-01-24 18:07 Benjamin Kosnik

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=20030123101006.A6570@synopsys.com \
    --to=jbuck@synopsys.com \
    --cc=gcc@gcc.gnu.org \
    --cc=gdr@integrable-solutions.net \
    /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).