aboutsummaryrefslogtreecommitdiff
path: root/doc/HACKING
diff options
context:
space:
mode:
authorNick Mathewson <nickm@torproject.org>2011-03-10 16:10:53 -0500
committerNick Mathewson <nickm@torproject.org>2011-03-10 16:10:53 -0500
commit48c4d532814ae4fdbf07635e57911bdf0e962b75 (patch)
tree6cea7363fc95e22a2d016aa19241010d2bc50ca8 /doc/HACKING
parent78d5955e5beee201087fc9af19190c964fafaed7 (diff)
downloadtor-48c4d532814ae4fdbf07635e57911bdf0e962b75.tar
tor-48c4d532814ae4fdbf07635e57911bdf0e962b75.tar.gz
Add a step to the release process: tell trac about the version.
Diffstat (limited to 'doc/HACKING')
-rw-r--r--doc/HACKING9
1 files changed, 8 insertions, 1 deletions
diff --git a/doc/HACKING b/doc/HACKING
index 32cea9967..b61295374 100644
--- a/doc/HACKING
+++ b/doc/HACKING
@@ -442,7 +442,14 @@ the website.
9) Email Erinn and weasel (cc'ing tor-assistants) that a new tarball
is up. This step should probably change to mailing more packagers.
-10) Wait up to a day or two (for a development release), or until most
+10) Add the version number to Trac. To do this, go to Trac, log in,
+select "Admin" near the top of the screen, then select "Versions" from
+the menu on the left. At the right, there will be an "Add version"
+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
packages are up (for a stable release), and mail the release blurb and
changelog to tor-talk or tor-announce.