--- a/doc/cheatsheets/making_a_release
+++ b/doc/cheatsheets/making_a_release
@@ -1,13 +1,12 @@
-All code/doc changes should be committed.
+All code/doc changes should be committed in the release_1 branch.
 
-To get the svn revision of the previous release:
+To get the hg revision of the previous release:
 
-    $ svn log https://pyke.svn.sourceforge.net/svnroot/pyke/tags
+    $ hg tags
 
-Do "svn log" to see what's changed:
+Do "hg log" to see what's changed:
 
-    $ svn log -r 48:HEAD \
-        https://pyke.svn.sourceforge.net/svnroot/pyke/branches/release_1.0
+    $ hg log -v -r .:48
 
 Write: RELEASE_NOTES-1.0.2
 
@@ -39,14 +38,19 @@
     >>> krb_compiler.compile_krb('compiler', 'compiled_krb', 'compiled_krb', 'compiler.krb')
     $ mv compiled_krb/compiler_bc.py .
 
-COMMIT SVN UPDATES
+COMMIT HG UPDATES
 
 REBUILD DOCUMENTS
 
     $ cd doc/source
     $ bin/gen_html
 
-COMMIT SVN UPDATES (if any)
+COMMIT HG UPDATES (if any)
+
+CHECK FOR OTHER CHANGES
+
+    $ hg fetch release_1-hg
+    $ retest as necessary
 
 BUILD RELEASE
 
@@ -59,9 +63,13 @@
 
 TAG RELEASE
 
-    $ svn copy \
-          https://pyke.svn.sourceforge.net/svnroot/pyke/branches/release_1.0 \
-          https://pyke.svn.sourceforge.net/svnroot/pyke/tags/1.0.2
+    $ hg tag 1.0.2
+ ?? $ hg commit
+
+PUSH TO SOURCEFORGE
+
+    $ hg push
+    $ hg push hg
 
 ADD NEW RELEASE TO SOURCEFORGE TRACKERS:
 
@@ -124,3 +132,20 @@
     $ unset PYTHONPATH
     $ source bin/activate
 
+COPY TO PYKE BRANCH:
+
+    $ cd ../pyke_working
+    $ hg pull -u hg (no merge should be required here!)
+    $ hg fetch release_1
+    $ (test)
+    $ hg push
+    $ hg push hg
+
+COPY TO PRE_2TO3 BRANCH:
+
+    $ cd ../pre_working
+    $ hg pull -u hg (no merge should be required here!)
+    $ hg fetch pyke
+    $ (clone, run 2to3 and test)
+    $ hg push
+    $ hg push hg