From: Tom de Vries <tdevries@suse.de>
To: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>, gcc@gcc.gnu.org
Cc: Richard Biener <rguenther@suse.de>, Gerald Pfeifer <gerald@pfeifer.com>
Subject: [RFC] Update Stage 4 description
Date: Wed, 09 Jan 2019 08:41:00 -0000 [thread overview]
Message-ID: <869742ac-5f7e-7673-48c4-f393a1e2eb65@suse.de> (raw)
[ To revisit https://gcc.gnu.org/ml/gcc-patches/2018-04/msg00385.html ]
The current formulation for the description of Stage 4 here (
https://gcc.gnu.org/develop.html ) is:
...
During this period, the only (non-documentation) changes that may be
made are changes that fix regressions.
Other changes may not be done during this period.
Note that the same constraints apply to release branches.
This period lasts until stage 1 opens for the next release.
...
This updated formulation was proposed by Richi (with a request for
review of wording):
...
During this period, the only (non-documentation) changes that may
be made are changes that fix regressions.
-Other changes may not be done during this period.
+Other important bugs like wrong-code, rejects-valid or build issues may
+be fixed as well. All changes during this period should be done with
+extra care on not introducing new regressions - fixing bugs at all cost
+is not wanted.
Note that the same constraints apply to release branches.
This period lasts until stage 1 opens for the next release.
...
If a text can be agreed upon, then I can prepare a patch for wwwdocs.
Thanks,
- Tom
next reply other threads:[~2019-01-09 8:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-09 8:41 Tom de Vries [this message]
2019-01-09 8:47 ` Richard Biener
2019-01-09 9:20 ` [wwwdocs, committed] " Tom de Vries
2019-01-09 9:02 ` [RFC] " Jonathan Wakely
2019-01-09 15:14 ` Nathan Sidwell
2019-01-09 14:16 ` Paul Koning
2019-01-09 14:31 ` Richard Biener
2019-01-09 16:33 ` Joseph Myers
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=869742ac-5f7e-7673-48c4-f393a1e2eb65@suse.de \
--to=tdevries@suse.de \
--cc=gcc-patches@gcc.gnu.org \
--cc=gcc@gcc.gnu.org \
--cc=gerald@pfeifer.com \
--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).