This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

PATCH for Re: GCC 3.0.1 Released


On Tue, 28 Aug 2001, Joe Buck wrote:
> Yes, having a good checklist will help, but you're missing a number of
> things: [...]

Well, that's exactly why I started the process by creating that web page
(as Mark didn't have the time) so that all of us can contribute!

And indeed Joseph and you already provided many useful additional items;
below you'll find the patch I installed based on your feedback:

  Further enhancements suggested by Joe Buck.

Thanks,
Gerald

Index: releasing.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/releasing.html,v
retrieving revision 1.2
diff -u -3 -p -r1.2 releasing.html
--- releasing.html	2001/08/29 09:23:54	1.2
+++ releasing.html	2001/08/29 11:52:10
@@ -10,22 +10,37 @@
 <ol>
 <li>Before rolling the release, update the release notes web pages and
 ensure that they are all listed in <code>contrib/gennews</code>.</li>
+
 <li>For a new major release, ensure that the build status page is
 present.</li>
+
 <li>Update the <code>releases.html</code> web page.</li>
+
 <li>Update the version numbers of the current and future releases on
 the main web page, and add a proper news item there as well.</li>
+
 <li>Generate online documentation for the new release with
 <code>update_web_docs</code> and link to it from
 <code>onlinedocs/index.html</code> (but don't break URLs to
 documentation for previous releases even if you remove the links to
 it).</li>
+
 <li>Add the release tag to the list in <code>cvs.html</code> (the
 branch tag should already be there).</li>
+
 <li>Update <code>~ftp/pub/gcc/README</code> and
 <code>~ftp/pub/gcc/releases/index.html</code>.</li>
+
+<li>Upload the release to <code>ftp.gnu.org</code>
+
 <li>Announce the release the gcc-announce@gcc.gnu.org and gcc@gcc.gnu.org
-mailing lists.</li>
+mailing lists.
+<ul>
+<li>Make sure that most mirrors have retrieved the new release already.</li>
+<li>In the case of a major release, coordinate announcements with the
+FSF.</li>
+</ul></li>
+
 <li>Increment the version numbers in the <code>[vV]version.c</code>
 files and make them include the date and <code>(prerelease)</code>
 instead of saying <code>(release)</code> and the old release version,


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]