summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorNick Mathewson <nickm@torproject.org>2011-07-14 09:51:58 -0400
committerNick Mathewson <nickm@torproject.org>2011-07-14 09:51:58 -0400
commitd67b304b20a3dbca9ad3072b33d6e1d54680f220 (patch)
tree1c3c42125e543c5a0d394483779ab63861b4822b
parente8bfe89365e86dc9ed311431d3cc87af88132f34 (diff)
parent5580fbb0c481a1f52fcef9e5b65966d5a91446d9 (diff)
downloadtor-d67b304b20a3dbca9ad3072b33d6e1d54680f220.tar.gz
tor-d67b304b20a3dbca9ad3072b33d6e1d54680f220.zip
Merge remote-tracking branch 'origin/maint-0.2.2'
-rw-r--r--doc/HACKING6
1 files changed, 5 insertions, 1 deletions
diff --git a/doc/HACKING b/doc/HACKING
index feeb05d028..9747f22651 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.