diff: release checklist.

[Tyson Richard DOWD]

Hi,

Someone want to check this?

===================================================================

Estimated hours taken: 0.5

compiler/notes/release_checklist.html:
	Update release checklist with how to upload to sunsite, post to
	comp.os.linux.announce, and update the webpage with a new
	release.

Index: compiler/notes/release_checklist.html
===================================================================
RCS file: /home/staff/zs/imp/mercury/compiler/notes/release_checklist.html,v
retrieving revision 1.3
diff -u -r1.3 release_checklist.html
--- release_checklist.html	1997/08/01 05:26:09	1.3
+++ release_checklist.html	1997/11/17 02:56:22
@@ -22,9 +22,33 @@
      releases.
      The HISTORY file should include the NEWS files from previous releases.
 
-<li> Update the WWW documentation in the `www' directory,
-     but don't commit it to the main branch yet, because otherwise
-     it would be installed on the WWW pages overnight.
+<li> Update the WWW documentation in the `www' directory.
+     <ul>
+     <li> For minor releases, update release.html with a new entry about
+	  this release (put it at the top of the page), and provide a
+	  new link to download the release. See old-release.html for
+	  examples.
+
+     <li> For major releases, you will need to create some new web pages:<br>
+          <dl>
+          <dt> release-VERSION.html
+          <dd> The release notes for this version.
+
+	  <dt> release-VERSION-bugs.html
+	  <dd> Any outstanding bugs for this release.
+
+	  <dt> release-VERSION-contents.html
+	  <dd> The contents of this distribution.
+
+          </dl>
+	  You will also need to update release.html.   Move the old
+	  information in release.html to old-release.html. Modify
+	  release.html to refer to the new html files you have created,
+	  and change the links to download the release. 
+
+     <li> Don't commit your changes to the main branch yet, because
+	  otherwise it would be installed on the WWW pages overnight.
+     </ul>
 
 <li> Use `cvs tag' to tag all the files with a `version-x_y_z' tag.
 
@@ -69,6 +93,22 @@
     to make copies of it on ftp://ftp.cs.sunysb.edu/pub/XSB/mercury
     respectively. <br>
     The mirror on ftp://ftp.csd.uu.se/pub/Mercury is supposedly automated.
+
+<li> Prepare a new "mercury-VERSION.lsm" file for this Mercury release
+     (use the one already uploaded to
+     ftp://sunsite.unc/edu/pub/Linux/Incoming as a template). The
+     version number, date, file sizes, and file names need to be updated
+     for a new release.
+
+<li> Upload "mercury-VERSION-core.tar.gz" and "mercury-VERSION.lsm" to
+     ftp://sunsite.unc.edu/incoming/Linux. They will be moved to
+     /pub/Linux/Incoming fairly quickly, and eventually should be moved
+     to /pub/linux/devel/lang/mercury.
+
+<li> Send "mercury-VERSION.lsm" to the lsm robot at lsm at execpc.com.
+
+<li> Append "mercury-VERSION.lsm" to a release notice and send it to
+     linux-announce at news.ornl.gov. This will post to comp.os.linux.announce.
 
 <li>  Email mercury-announce at cs.mu.oz.au and cross-post announcement to
     comp.lang.misc, comp.lang.prolog, comp.lang.functional, comp.object.logic,

-- 
       Tyson Dowd           # 
                            #         Linux versus Windows is a 
     trd at cs.mu.oz.au        #            Win lose situation.
http://www.cs.mu.oz.au/~trd #