aboutsummaryrefslogtreecommitdiff
path: root/doc/HACKING/ReleasingTor.md
diff options
context:
space:
mode:
authorNick Mathewson <nickm@torproject.org>2018-01-26 14:34:25 -0500
committerNick Mathewson <nickm@torproject.org>2018-01-26 14:34:25 -0500
commit73e5be5619ce39db70fa8deb7a56ae4252abfd2e (patch)
treec655d5eb962d66e6f2f260d373de935f359407b9 /doc/HACKING/ReleasingTor.md
parent7a74b3663fdaa40fc84e48990d15953a8f46a2bf (diff)
downloadtor-73e5be5619ce39db70fa8deb7a56ae4252abfd2e.tar.gz
tor-73e5be5619ce39db70fa8deb7a56ae4252abfd2e.zip
ReleasingTor.md: check for recommendation, listing on dl page
Closes ticket 23118.
Diffstat (limited to 'doc/HACKING/ReleasingTor.md')
-rw-r--r--doc/HACKING/ReleasingTor.md6
1 files changed, 5 insertions, 1 deletions
diff --git a/doc/HACKING/ReleasingTor.md b/doc/HACKING/ReleasingTor.md
index 9cbc8710bb..570a175b63 100644
--- a/doc/HACKING/ReleasingTor.md
+++ b/doc/HACKING/ReleasingTor.md
@@ -181,7 +181,11 @@ new Tor release:
0.2.2.23-alpha" (or whatever the version is), and we select the date as
the date in the ChangeLog.
-5. Mail the release blurb and ChangeLog to tor-talk (development release) or
+5. Double-check: did the version get recommended in the consensus yet? Is
+ the website updated? If not, don't announce until they have the
+ up-to-date versions, or people will get confused.
+
+6. Mail the release blurb and ChangeLog to tor-talk (development release) or
tor-announce (stable).
Post the changelog on the blog as well. You can generate a