This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: 3.3.2 prerelease still on ftp
- From: Gerald Pfeifer <gerald at pfeifer dot com>
- To: Mark Mitchell <mark at codesourcery dot com>
- Cc: Dara Hazeghi <dhazeghi at yahoo dot com>, gcc at gcc dot gnu dot org,gcc-patches at gcc dot gnu dot org
- Date: Sun, 16 Nov 2003 16:57:58 +0100 (CET)
- Subject: Re: 3.3.2 prerelease still on ftp
- References: <20031115005207.72865.qmail@web41103.mail.yahoo.com> <Pine.BSF.4.58.0311151252450.45619@acrux.dbai.tuwien.ac.at><1068920094.19838.531.camel@doubledemon.codesourcery.com>
On Sat, 15 Nov 2003, Mark Mitchell wrote:
>> We probably should make removing prereleases part of the regular release
>> process. Agreed?
> Yes, that's a good idea.
>
> Would you mind adding it to the release checklist?
Not at all.
Installed.
Gerald
Index: releasing.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/releasing.html,v
retrieving revision 1.17
diff -u -3 -p -r1.17 releasing.html
--- releasing.html 4 Oct 2003 11:39:47 -0000 1.17
+++ releasing.html 16 Nov 2003 15:54:59 -0000
@@ -45,15 +45,17 @@ previous release, in a directory contain
<code>-p /some/where/gcc-3.1/gcc-3.1.tar.gz</code>, where there are
also files such as <code>/some/where/gcc-3.1/gcc-core-3.1.tar.gz</code>).</li>
-<li>Upload the release to <code>ftp.gnu.org</code>.</li>
+<li>Upload the release to ftp.gnu.org.</li>
<li>Update <code>~ftp/pub/gcc/releases/index.html</code>.</li>
+
+<li>Remove pre-release sources from gcc.gnu.org:~ftp/pub/gcc/.</li>
</ol>
<h2>Web Site Updates</h2>
-<ol start="7">
+<ol start="8">
<li>Update the <code>releases.html</code> and <code>develop.html</code>
web pages.</li>
@@ -79,7 +81,7 @@ number inserted).</li>
<h2>Announcements</h2>
-<ol start="12">
+<ol start="13">
<li>Announce the release to the gcc-announce@gcc.gnu.org and gcc@gcc.gnu.org
mailing lists.
<ul>
@@ -99,7 +101,7 @@ allowed.</li>
<h2>Bugzilla Updates</h2>
-<ol start="15">
+<ol start="16">
<li>Create a new version in Bugzilla corresponding to the new branch
version. This can be accomplished by choosing products, choosing gcc,
and editing the versions. Please do <strong>not</strong> delete old