[tor-commits] [tor/release-0.2.2] Add a couple of notes to doc/HACKING based on 0.2.2.25-alpha process

[nickm@xxxxxxxxxxxxxx]

commit 033c27ac5ea02fa1a44651c5a324cb78e787f1a3
Author: Nick Mathewson <nickm@xxxxxxxxxxxxxx>
Date:   Mon May 2 14:45:44 2011 -0400

    Add a couple of notes to doc/HACKING based on 0.2.2.25-alpha process
---
 doc/HACKING |    5 +++++
 1 files changed, 5 insertions(+), 0 deletions(-)

diff --git a/doc/HACKING b/doc/HACKING
index 6336232..86d4a98 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.)



_______________________________________________
tor-commits mailing list
tor-commits@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-commits