More robust homedir detection on Windows.

[sbcl.git] / doc / internals-notes / release-checklist.txt

diff --git a/doc/internals-notes/release-checklist.txt b/doc/internals-notes/release-checklist.txt
index dc23421..8b98165 100644 (file)
--- a/doc/internals-notes/release-checklist.txt
+++ b/doc/internals-notes/release-checklist.txt
@@ -54,6 +54,8 @@ Create the distribution files:
            *** (In sbcl-x.y.z/, run clean.sh and/or distclean.sh to
                clean up.)
            *** Run "sh sbcl-x.y.z/source-distribution.sh sbcl-x.y.z".
+        ** copy the change descriptions in NEWS for this release to
+           sbcl-x.y.z-release.notes.txt
       * Run "md5sum > sbcl-x.y.z-$sfuserid" on the renamed tar files.
         (On *BSD, it's "md5" instead of "md5sum".)
       * Edit the digest file to add
@@ -69,34 +71,18 @@ Now we have e.g.:
       * sbcl-0.7.0-html.tar.bz2
       * sbcl-0.7.0-wnewman.asc
 
-for sf anonymous ftp:
- # no longer possible now that sf doesn't provide anonftp:
- # cd /usr/stuff/
- # scp sbcl-x.y.z-* shell1.sourceforge.net:/home/groups/ftp/pub/sbcl/
- # cd /usr/stuff/sbcl/
- # for stem in NEWS README INSTALL; do
- #   scp $stem shell1.sourceforge.net:/home/groups/ftp/pub/sbcl/$stem-x.y.z
- # done
-for sf 'module release' system:
- # no longer possible now that sf doesn't have upload.sourceforge.net
- # * Upload the distribution files via anonymous ftp to
- # upload.sourceforge.net in the /incoming directory.
- * Upload the distribution files via sftp to the uploads/ directory at 
-   $sfuser@frs.sourceforge.net
+ * upload the distribution files via sftp to
+   $sfuser,sbcl@frs.sourceforge.net to the directory
+   /home/frs/project/s/sb/sbcl/sbcl/<version> (creating the directory
+   first. The directory will be created with bad permissions, chmod
+   it to 0775 so that other developers can upload binaries too)
  * possible shortcuts:
     <https://sourceforge.net/project/admin/?group_id=1373>
-    <https://sourceforge.net/project/admin/editpackages.php?group_id=1373>
-    <https://sourceforge.net/project/admin/newrelease.php?package_id=1354&group_id=1373>
- * Do the misbegotten^Wunscriptable HTTPforms thing on the sourceforge
-  project home to make the distribution files visible.
-  ** (from "Admin", then "File Releases")
-  ** "Add release" for package "sbcl", "release name"="x.y.z". (not
-     "release name"="sbcl-x.y.z")
-  ** boilerplate for "Release Notes":
-      For information about this release, see the NEWS file
-      in the distribution. The information is also available
-      in the "Change Log"/"Changes" section of the SourceForge
-      webbed description of this release.
+    sftp $sfuser,sbcl@frs.sourceforge.net
+ * Do the misbegotten^Wunscriptable AJAX thing on the sourceforge File
+   Manager site to make the release notes associated with the file releases
+   ** In the File Manager interface, click on the release notes file,
+      tick the release notes box.
 
 For a new port (e.g. OpenBSD in sbcl-0.6.7) it's particularly good to
 upload the appropriate binary distribution.