aboutsummaryrefslogtreecommitdiff
path: root/doc/HACKING
diff options
context:
space:
mode:
authorSebastian Hahn <sebastian@torproject.org>2011-07-14 13:03:55 +0200
committerNick Mathewson <nickm@torproject.org>2011-07-14 09:51:24 -0400
commit5580fbb0c481a1f52fcef9e5b65966d5a91446d9 (patch)
treea444abac4f5dde8d0de2b9e5f83f1da7a73c2a6b /doc/HACKING
parent8e3830352f806b680d1c60b66c8cc7fb67f76175 (diff)
downloadtor-5580fbb0c481a1f52fcef9e5b65966d5a91446d9.tar
tor-5580fbb0c481a1f52fcef9e5b65966d5a91446d9.tar.gz
Update HACKING with some more release instructions
Diffstat (limited to 'doc/HACKING')
-rw-r--r--doc/HACKING6
1 files changed, 5 insertions, 1 deletions
diff --git a/doc/HACKING b/doc/HACKING
index feeb05d02..9747f2265 100644
--- a/doc/HACKING
+++ b/doc/HACKING
@@ -495,7 +495,11 @@ box. By convention, we enter the version in the form "Tor:
0.2.2.23-alpha" (or whatever the version is), and we select the date as
the date in the ChangeLog.
-11) Wait up to a day or two (for a development release), or until most
+11) Forward-port the ChangeLog.
+
+12) Update the topic in #tor to reflect the new version.
+
+12) Wait up to a day or two (for a development release), or until most
packages are up (for a stable release), and mail the release blurb and
changelog to tor-talk or tor-announce.