public inbox for gcc-cvs-wwwdocs@sourceware.org help / color / mirror / Atom feed
From: Richard Biener <rguenth@sourceware.org> To: gcc-cvs-wwwdocs@gcc.gnu.org Subject: gcc-wwwdocs branch master updated. 956e42549676172be23a0a3e11d98fc0b9e8b340 Date: Mon, 17 Jan 2022 12:27:24 +0000 (GMT) [thread overview] Message-ID: <20220117122724.C3FA83858D3C@sourceware.org> (raw) This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "gcc-wwwdocs". The branch, master has been updated via 956e42549676172be23a0a3e11d98fc0b9e8b340 (commit) from 8df3cd9d7aa84b69ece8024154bf0d4898071f50 (commit) Those revisions listed above that are new to this repository have not appeared on any other notification email; so we list those revisions in full, below. - Log ----------------------------------------------------------------- commit 956e42549676172be23a0a3e11d98fc0b9e8b340 Author: Richard Biener <rguenther@suse.de> Date: Mon Jan 17 13:27:03 2022 +0100 Clarify GCC versioning, esp. the DEV-PHASE. 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> ----------------------------------------------------------------------- Summary of changes: htdocs/develop.html | 10 ++++++---- 1 file changed, 6 insertions(+), 4 deletions(-) hooks/post-receive -- gcc-wwwdocs
reply other threads:[~2022-01-17 12:27 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=20220117122724.C3FA83858D3C@sourceware.org \ --to=rguenth@sourceware.org \ --cc=gcc-cvs-wwwdocs@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: linkBe 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).