summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorNick Mathewson <nickm@torproject.org>2021-06-07 13:51:05 -0400
committerNick Mathewson <nickm@torproject.org>2021-06-07 13:51:05 -0400
commitf93d9d8bacb672c123674cfe9fbb01320e6cb3d7 (patch)
treec3710b2ca4ccb85abf7e255bec1d3b1b17c420f9 /doc
parentc62bd0e70883088713f3bc78eba9fc1451dd7ddc (diff)
downloadtor-f93d9d8bacb672c123674cfe9fbb01320e6cb3d7.tar.gz
tor-f93d9d8bacb672c123674cfe9fbb01320e6cb3d7.zip
Add a checklist to releasingtor.md
Diffstat (limited to 'doc')
-rw-r--r--doc/HACKING/ReleasingTor.md11
1 files changed, 11 insertions, 0 deletions
diff --git a/doc/HACKING/ReleasingTor.md b/doc/HACKING/ReleasingTor.md
index 358b53a8db..8ee57b0cb5 100644
--- a/doc/HACKING/ReleasingTor.md
+++ b/doc/HACKING/ReleasingTor.md
@@ -1,3 +1,14 @@
+# CHECKLIST
+
+Here's a summary checklist, with the things that Nick messes up most often.
+
+Did you:
+
+ * [ ] Copy the ChangeLog to the ReleaseNotes?
+ * [ ] Check that the new versions got approved?
+ * [ ] Check the release date in the ChangeLog?
+ * [ ] Update the GeoIP file?
+
# Putting out a new release
Here are the steps that the maintainer should take when putting out a