public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Kelley Cook <kcook34@ford.com>
To: Mark Mitchell <mark@codesourcery.com>
Cc: gcc@gcc.gnu.org
Subject: Re: GCC 3.3 branch open
Date: Fri, 08 Aug 2003 20:05:00 -0000	[thread overview]
Message-ID: <3F33F365.9010606@ford.com> (raw)
In-Reply-To: <200308081809.h78I90Z4010155@doubledemon.codesourcery.com>

Mark Mitchell wrote:

> The 3.3 branch is now open, under the usual regression-only check-in
> rules.

Is this really the usual checkin rules for a branch?

For example after 3.1 was released you said:

> 1. Anyone who can normally approve patches can approve patches that
>    fix regressions from previously released versions of GCC.
> 
> 2. I will review and approve patches that do not fix regressions if
> 
>    a) they appear safe
>    b) they fix very important problems, or
>    c) they add support for new platforms, language features, etc.
>       that we did not support before -- and that we cannot, therefore,
>       be regressing.
> 
>    Please make your case explicitly; assume I know very little (a
>    good assumption!) and explain why your patch fits these criteria.

-- http://gcc.gnu.org/ml/gcc/2002-05/msg01212.html

I thought regression-only was only the requirement when the next release 
was close.  I personally would think that important bug fixes should not 
necessarily have to wait for 3.4, even if that bug has been always 
present in GCC.

You, of course, are the release manager, so it is your call to make.

Kelley Cook


  reply	other threads:[~2003-08-08 19:02 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-08 19:03 Mark Mitchell
2003-08-08 20:05 ` Kelley Cook [this message]
2003-08-08 20:16   ` Mark Mitchell
  -- strict thread matches above, loose matches on Subject: below --
2003-10-17 19:30 GCC 3.3 Branch Open Mark Mitchell
2003-10-18 15:53 ` Eric Botcazou
2003-10-20  6:12   ` Mark Mitchell
2003-05-14 23:48 Mark Mitchell
2003-05-15  0:12 ` Daniel Berlin
2003-05-15 10:19   ` Joseph S. Myers
2003-05-15 14:04     ` Daniel Berlin
2003-05-15 15:59       ` Daniel Berlin
2003-05-15 12:41   ` Gerald Pfeifer
2003-05-15 14:08     ` Daniel Berlin

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=3F33F365.9010606@ford.com \
    --to=kcook34@ford.com \
    --cc=gcc@gcc.gnu.org \
    --cc=mark@codesourcery.com \
    /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).