From: Jakub Jelinek <jakub@redhat.com>
To: Richard Guenther <richard.guenther@gmail.com>
Cc: Gerald Pfeifer <gerald@pfeifer.com>,
gcc@gcc.gnu.org, Ian Lance Taylor <iant@google.com>
Subject: Re: Renaming Stage 1 and Stage 3
Date: Mon, 11 Jun 2012 15:05:00 -0000 [thread overview]
Message-ID: <20120611150457.GE15191@sunsite.ms.mff.cuni.cz> (raw)
In-Reply-To: <CAFiYyc2AGbBtzhJTodneCt7i54wBUqC4cD0s8asJO4ziSYdy2Q@mail.gmail.com>
On Mon, Jun 11, 2012 at 11:18:23AM +0200, Richard Guenther wrote:
> Eh - why not give them names with an actual meaning? "Development Stage"
> and "Stabilizing Stage"? I realize those are rather long names, but you
> can always put short forms in tables, like Dev Stage and Stab Stage.
Shouldn't we have names for the 3 phases we actually use, rather than just
two? I.e. development phase, stabilization phase (no new features,
bugfixes allowed) and release branch freeze phase (only regression bugfixes and
documentation, same as for release branches)?
Jakub
prev parent reply other threads:[~2012-06-11 15:05 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-26 17:38 Potentially merging cxx-mem-model with mainline Andrew MacLeod
2011-10-26 18:59 ` David Gilbert
2011-10-27 5:22 ` Benjamin Kosnik
2011-10-27 11:58 ` Richard Guenther
2011-10-27 17:51 ` Andrew MacLeod
2011-10-27 6:29 ` Joseph S. Myers
2011-10-31 15:58 ` Aldy Hernandez
[not found] ` <mcrbosxvvww.fsf@dhcp-172-18-216-180.mtv.corp.google.com>
2012-06-10 22:03 ` Renaming Stage 1 and Stage 3 Gerald Pfeifer
2012-06-11 9:18 ` Richard Guenther
2012-06-11 10:28 ` Dodji Seketeli
2012-06-11 12:21 ` Andrew MacLeod
2012-06-11 13:57 ` Diego Novillo
2012-06-11 12:17 ` Paolo Bonzini
2012-06-11 14:16 ` Miles Bader
2012-06-11 14:18 ` Richard Guenther
2012-06-11 15:05 ` Jakub Jelinek [this message]
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=20120611150457.GE15191@sunsite.ms.mff.cuni.cz \
--to=jakub@redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=gerald@pfeifer.com \
--cc=iant@google.com \
--cc=richard.guenther@gmail.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).