From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 11088 invoked by alias); 12 Mar 2017 22:45:22 -0000 Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-owner@gcc.gnu.org Received: (qmail 11043 invoked by uid 89); 12 Mar 2017 22:45:20 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-11.9 required=5.0 tests=BAYES_00,GIT_PATCH_2,GIT_PATCH_3,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=ham version=3.3.2 spammy=Site, Hx-languages-length:2956, 78, accomplished X-Spam-User: qpsmtpd, 2 recipients X-HELO: ainaz.pair.com Received: from ainaz.pair.com (HELO ainaz.pair.com) (209.68.2.66) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Sun, 12 Mar 2017 22:45:18 +0000 Received: from anthias (vie-188-118-249-200.dsl.sil.at [188.118.249.200]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ainaz.pair.com (Postfix) with ESMTPSA id BD3863F530; Sun, 12 Mar 2017 18:45:10 -0400 (EDT) Date: Sun, 12 Mar 2017 22:45:00 -0000 From: Gerald Pfeifer To: Richard Biener cc: Joseph Myers , gcc@gcc.gnu.org, gcc-patches@gcc.gnu.org Subject: PATCH for Re: Release notes for GCC 7? In-Reply-To: Message-ID: References: MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII X-IsSubscribed: yes X-SW-Source: 2017-03/txt/msg00048.txt.bz2 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? Gerald 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 @@

This page documents the procedure for making a new release branch.

Preparations

Execute the following commands, substituting appropriate version numbers: @@ -38,15 +40,25 @@ for the next major release in the wwwdocs repository and populate it with initial copies of changes.html and criteria.html.

Add index.html and buildstat.html pages -to the directory corresponding to the newly created release branch. -Update the toplevel buildstat.html accordingly.

Web Site Updates

+ +

Add index.html and changes.html pages +based on the previous release branch to the directory corresponding to +the newly created release branch.
Add buildstat.html and update the toplevel +buildstat.html accordingly.
Update the toplevel index.html page to show the new active release branch, the current release series, and active development (mainline). Update the version and development stage for mainline.

Update maintainer-scripts/crontab 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 @@ Send them to the translation project if no snapshot of this version was sent during development stage 3 or 4.

Bugzilla Updates

+ +

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 not delete old @@ -85,7 +101,6 @@
Ask Daniel Berlin to adjust all PRs with the just-branched version in their summary to also contain the new version corresponding to mainline.