This is the mail archive of the
mailing list for the GCC project.
Re: PATCH for Re: Release notes for GCC 7?
- From: Richard Biener <richard dot guenther at gmail dot com>
- To: Gerald Pfeifer <gerald at pfeifer dot com>
- Cc: Joseph Myers <joseph at codesourcery dot com>, GCC Development <gcc at gcc dot gnu dot org>, GCC Patches <gcc-patches at gcc dot gnu dot org>
- Date: Mon, 13 Mar 2017 09:31:34 +0100
- Subject: Re: PATCH for Re: Release notes for GCC 7?
- Authentication-results: sourceware.org; auth=none
- References: <alpine.DEB.email@example.com> <alpine.LSU.firstname.lastname@example.org> <CAFiYyc1nv6EH9nYSirXBZE2G_+w1ma483oRqjJSvj9oBCZOFVw@mail.gmail.com> <alpine.LSU.email@example.com>
On Sun, Mar 12, 2017 at 11:45 PM, Gerald Pfeifer <firstname.lastname@example.org> wrote:
> On Wed, 24 Aug 2016, Richard Biener wrote:
>> We've been creating those lazily over the last decade. We can change
>> that, an entry for releasing.html is appreciated then so we don't forget.
> And here we go, in time for the release of GCC 7 / branching of GCC 8.
> (Except, this time I went ahead and already created gcc-8/changes.html
> so that you guys don't have to worry about that. ;-)
> Note, I added this to branching.html, not releasing.html, not the least
> since branching.html already had the creation of other web pages for the
> new release series and that also seems the more appropriate point time-
> wise. Agreed?
> Index: branching.html
> RCS file: /cvs/gcc/wwwdocs/htdocs/branching.html,v
> retrieving revision 1.32
> diff -u -r1.32 branching.html
> --- branching.html 28 Jun 2014 10:34:16 -0000 1.32
> +++ branching.html 12 Mar 2017 22:37:59 -0000
> @@ -7,6 +7,8 @@
> <p>This page documents the procedure for making a new release branch.</p>
> <li>Execute the following commands, substituting appropriate version
> @@ -38,15 +40,25 @@
> for the next major release in the <code>wwwdocs</code> repository and
> populate it with initial copies of <code>changes.html</code> and
> -<li>Add <code>index.html</code> and <code>buildstat.html</code> pages
> -to the directory corresponding to the newly created release branch.
> -Update the toplevel <code>buildstat.html</code> accordingly.</li>
> +<h2>Web Site Updates</h2>
> +<ol start="6">
> +<li>Add <code>index.html</code> and <code>changes.html</code> pages
> +based on the previous release branch to the directory corresponding to
> +the newly created release branch.</li>
> +<li>Add <code>buildstat.html</code> and update the toplevel
> +<code>buildstat.html</code> accordingly.</li>
> <li>Update the toplevel <code>index.html</code> page to show the new active
> release branch, the current release series, and active development
> (mainline). Update the version and development stage for mainline.</li>
> +<ol start="9">
> <li>Update <code>maintainer-scripts/crontab</code> on the mainline by
> adding an entry to make snapshots of the new branch and adjusting the
> version number of the mainline snapshots.
> @@ -67,7 +79,11 @@
> <a href="translation.html#submit">Send them
> to the translation project</a> if no snapshot of this version was sent
> during development stage 3 or 4.</li>
> +<h2>Bugzilla Updates</h2>
> +<ol start="11">
> <li>Create new versions in Bugzilla corresponding to the new mainline
> version. This can be accomplished by choosing "products", choosing "gcc",
> and editing the versions. Please do <strong>not</strong> delete old
> @@ -85,7 +101,6 @@
> <li>Ask Daniel Berlin to adjust all PRs with the just-branched version
> in their summary to also contain the new version corresponding to