From: Richard Biener <rguenther@suse.de>
To: gcc-patches@gcc.gnu.org
Subject: [PATCH][www][pushed] Clarify GCC versioning, esp. the DEV-PHASE.
Date: Mon, 17 Jan 2022 13:28:18 +0100 (CET) [thread overview]
Message-ID: <8615r15-sopq-p7q9-640-p145n1qq63q@fhfr.qr> (raw)
---
htdocs/develop.html | 10 ++++++----
1 file changed, 6 insertions(+), 4 deletions(-)
diff --git a/htdocs/develop.html b/htdocs/develop.html
index 263cbc79..1ac48b09 100644
--- a/htdocs/develop.html
+++ b/htdocs/develop.html
@@ -266,8 +266,10 @@ way and on the following timeline:</p>
<tr><th>Version</th><th>DEV-PHASE</th><th>When</th></tr>
<tr><td>5.0.0</td><td>(experimental)</td>
<td>during active development of GCC 5 (stage 1 to 3)</td></tr>
+ <tr><td>5.0.1</td><td>(experimental)</td>
+ <td>during the stabilization period of GCC 5 (stage 4)</td></tr>
<tr><td>5.0.1</td><td>(prerelease)</td>
- <td>during the stabilization period of GCC 5</td></tr>
+ <td>after branching for the release of GCC 5.1</td></tr>
<tr><td>6.0.0</td><td>(experimental)</td>
<td>during active development of GCC 6 (stage 1 to 3)</td></tr>
<tr><td>5.1.0</td><td></td>
@@ -278,12 +280,12 @@ way and on the following timeline:</p>
<td>for the second release from the GCC 5 branch</td></tr>
<tr><td>5.2.1</td><td></td>
<td>during development on the branch post the 5.2.0 release</td></tr>
- <tr><td>6.0.1</td><td>(prerelease)</td>
- <td>during the stabilization period of GCC 6</td></tr>
+ <tr><td>6.0.1</td><td>(experimental)</td>
+ <td>during the stabilization period of GCC 6 (stage 4)</td></tr>
<tr><td>...</td><td></td><td></td></tr>
</table>
<p>To summarize, the first release of GCC 5 will be GCC 5.1.0 while
-development snapshots will be GCC 5.0.0 and snapshots from the
+development snapshots will be GCC 5.0.0 or GCC 5.0.1 and snapshots from the
release branch GCC 5.n.1.</p>
<p><strong>Rationale</strong></p>
--
2.31.1
reply other threads:[~2022-01-17 12:28 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=8615r15-sopq-p7q9-640-p145n1qq63q@fhfr.qr \
--to=rguenther@suse.de \
--cc=gcc-patches@gcc.gnu.org \
/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).