diff mbox

[wwwdocs] Update releasing.html

Message ID alpine.LSU.2.20.1702012314080.2585@anthias.pfeifer.com
State New
Headers show

Commit Message

Gerald Pfeifer Feb. 1, 2017, 10:35 p.m. UTC 
I noticed that releasing.html had a reference to old-style (and
even incorrect) GCC release pages, and only one of the two files
that contrib/gennews processes per release.

Also, we do not ship gcc-core-... tarballs any more, so I removed
that reference and update to a newer version there as well.

Applied in the home it makes cutting a release a few seconds easier...

Gerald
diff mbox

Patch

Index: releasing.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/releasing.html,v
retrieving revision 1.46
diff -u -r1.46 releasing.html
--- releasing.html	13 Aug 2014 13:09:01 -0000	1.46
+++ releasing.html	1 Feb 2017 22:18:02 -0000
@@ -11,7 +11,8 @@ 
 
 <ol start="1">
 <li>Before rolling the release, update the release notes web pages
-(for example <code>gcc-4.5.0/index.html</code>)
+(for example <code>gcc-7/changes.html</code> and
+<code>gcc-7/index.html</code>)
 and ensure that they are all listed in <code>contrib/gennews</code>.
 On the announcement page for that release series, note the new
 release without removing information about any previous minor releases.
@@ -55,8 +56,7 @@ 
 option, whose argument must name the <code>.tar.bz2</code> file for a
 previous release, in a directory containing all the
 <code>.tar.bz2</code> files for that previous release (for example,
-<code>-p /some/where/gcc-4.2.2/gcc-4.2.2.tar.bz2</code>, where there are
-also files such as <code>/some/where/gcc-4.2.2/gcc-core-4.2.2.tar.bz2</code>).</li>
+<code>-p /some/where/gcc-5.4.0/gcc-5.4.0.tar.bz2</code>).</li>
 
 <li>Upload the release to ftp.gnu.org.</li>