aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorNick Mathewson <nickm@torproject.org>2011-05-02 14:45:44 -0400
committerNick Mathewson <nickm@torproject.org>2011-05-02 16:55:50 -0400
commit033c27ac5ea02fa1a44651c5a324cb78e787f1a3 (patch)
treeb592ee89c1e3ac64e5803019b6896ce28783bebe
parentdbd73b9689e8008adc149472ca5c02692a49923d (diff)
downloadtor-033c27ac5ea02fa1a44651c5a324cb78e787f1a3.tar
tor-033c27ac5ea02fa1a44651c5a324cb78e787f1a3.tar.gz
Add a couple of notes to doc/HACKING based on 0.2.2.25-alpha process
-rw-r--r--doc/HACKING5
1 files changed, 5 insertions, 0 deletions
diff --git a/doc/HACKING b/doc/HACKING
index 633623217..86d4a9878 100644
--- a/doc/HACKING
+++ b/doc/HACKING
@@ -472,6 +472,9 @@ in their approved versions list.
7) Sign and push the tarball to the website in the dist/ directory. Sign
and push the git tag.
+ (That's either "git tag -u <keyid> tor-0.2.x.y-status", then
+ "git push origin tag tor-0.2.x.y-status". To sign the
+ tarball, "gpg -ba <the_tarball>")
8) Edit include/versions.wmi to note the new version. Rebuild and push
the website.
@@ -490,3 +493,5 @@ the date in the ChangeLog.
packages are up (for a stable release), and mail the release blurb and
changelog to tor-talk or tor-announce.
+ (We might be moving to faster announcements, but don't announce until
+ the website is at least updated.)