On Thu, 11 Oct 2007, [EMAIL PROTECTED] wrote: > Snapshot gcc-4.2-20071011 is now available on > ftp://gcc.gnu.org/pub/gcc/snapshots/4.2-20071011/ > and on various mirrors, see http://gcc.gnu.org/mirrors.html for details.
I ran this script manually and reenabled the generation of snapshots off the GCC 4.2 branch. I assume we just missed the latter because we hadn't documented this step in our release documentation. Mark, what do you think of the patch below? It adds this piece of documentation and removes the step to remove RC sources from our server since we are now treating these pretty similar to regular snapshots which we do not remove either and we have users (including the FreeBSD Ports Collection who refer to these RC tarballs). (Also, it's less work for the release manager. ;-) Gerald Index: releasing.html =================================================================== RCS file: /cvs/gcc/wwwdocs/htdocs/releasing.html,v retrieving revision 1.29 diff -u -3 -p -r1.29 releasing.html --- releasing.html 21 Sep 2006 14:17:36 -0000 1.29 +++ releasing.html 11 Oct 2007 19:12:35 -0000 @@ -47,8 +47,6 @@ also files such as <code>/some/where/gcc <li>Upload the release to ftp.gnu.org.</li> -<li>Remove pre-release sources from gcc.gnu.org:~ftp/pub/gcc/.</li> - <li>If you are making a release of GCC 4.1 or later: Increment the version number in <code>gcc/BASE-VER</code>. Restore the word "prerelease" (without the quotation marks) to <code>gcc/DEV-PHASE</code>. @@ -60,6 +58,9 @@ stamp and (prerelease) annotation. Incr <li>Notify developers that checkins to the branch are once again allowed.</li> + +<li>Reenable the generation of snapshots off the respective release +branch in the crontab of gccadmin on gcc.gnu.org.</li> </ol> <h2>Web Site Updates</h2>
