diff --git a/ChangeLog b/ChangeLog
index 3c20f94d5..e065bebf4 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,3 +1,7 @@
+2004-08-27  Jeremy Fincher  <jemfinch@supybot.org>
+
+	* Version 0.79.9!
+	
 	* Added Infobot, a plugin to emulate Infobot.
 
 	* Added Anonymous, a plugin for anonymously saying things to a
diff --git a/RELNOTES b/RELNOTES
index 5b50b4ae3..4e641cbe6 100644
--- a/RELNOTES
+++ b/RELNOTES
@@ -1,8 +1,16 @@
+Version 0.79.9
+
 We've changed so much stuff in this release that we've given up on
 users upgrading their configuration files for the new release.  So
 do a clean install (python2.3 setup.py install --clean), run the
 wizard again, and kick some butt.
 
+(It's rumored that you can save most of your old configuration by
+appending your new configuration at the end of your old configuration
+and running supybot with that new configuration file.  This, of
+course, comes with no warranty or guarantee of utility -- try it if
+you want, but backup your original configuration file!)
+
 Version 0.77.2
 
 This is a drop-in replacement for 0.77.1, with two exceptions.  The
diff --git a/sandbox/RELEASE_CHECKLIST b/sandbox/RELEASE_CHECKLIST
index 5503aa5cd..11897c54d 100644
--- a/sandbox/RELEASE_CHECKLIST
+++ b/sandbox/RELEASE_CHECKLIST
@@ -1,14 +1,23 @@
 These are things not to be forgotten when making a Supybot release:
 
+Make sure the RELNOTES has "Version MAJOR.MINOR.PATCHLEVEL" at the top.
+Make sure the ChangeLog has been ordered by importance.
+Make sure the ChangeLog has been given a proper header and that its
+  first change is "* Version MAJOR.MINOR.PATCHLEVEL!".
 Update the version in conf.py.
 Update the version in setup.py.
 Update the version in scripts/supybot
-Make a release-MAJOR_MINOR_PATCHLEVEL tag.  (cvs tag ...)
-Make a release-MAJOR_MINOR_PATCHLEVEL-branch branch tag.  (cvs tag -b ...)
-Remove test directory from the tarball.
-Remove CVS directories from the tarball.
-Remove sandbox directory from the tarball.
-Create .tar.gz, .tar.bz2, and .zip archives.
+Commit these updates, even though it seems useless.
+Make a release-MAJOR_MINOR_PATCHLEVEL tag.  (cvs tag <tag>)
+Make a release-MAJOR_MINOR_PATCHLEVEL-branch branch tag.  (cvs tag -b <tag>)
+Remove test directory from the directory.
+Remove CVS directories from the directory.
+Remove sandbox directory from the directory.
+Remove all dotfiles (.cvsignore, etc.) from the directory.
+Move the supybot/ directory to Supybot-MAJOR.MINOR.PATCHLEVEL
+Create .tar.gz: tar czvf Supybot-MAJOR.MINOR.PATCHLEVEL.tar.gz <dir>
+Create .tar.bz2: tar cjvf Supybot-MAJOR.MINOR.PATCHLEVEL.tar.bz2 <dir>
+Create .zip: zip -r Supybot-MAJOR.MINOR.PATCHLEVEL.zip <dir>
 Add the release to the supybot package in SF.net.
 Upload the archives to upload.sf.net, add to the release on SF.net.
 Announce the release in a News item on SF.net.
@@ -17,5 +26,5 @@ Announce the release on PyPI via "python setup.py register".
 Announce the release on the forums.
 Announce the release on comp.lang.python and comp.lang.python.announce.
 Add a topic to #supybot announcing the release.
-Send a GPG-signed tar.gz to vomjom for packing in Debian.
+Send a GPG-signed tar.gz to jamessan for packing in Debian.
 Update the version in version.txt and upload to the website.