aboutsummaryrefslogtreecommitdiff
path: root/doc/HACKING/ReleasingTor.md
diff options
context:
space:
mode:
Diffstat (limited to 'doc/HACKING/ReleasingTor.md')
-rw-r--r--doc/HACKING/ReleasingTor.md13
1 files changed, 10 insertions, 3 deletions
diff --git a/doc/HACKING/ReleasingTor.md b/doc/HACKING/ReleasingTor.md
index c7cd0bc111..15c8ac55d8 100644
--- a/doc/HACKING/ReleasingTor.md
+++ b/doc/HACKING/ReleasingTor.md
@@ -20,8 +20,11 @@ new Tor release:
=== I. Make sure it works
-1. Make sure that CI passes: have a look at Travis, Appveyor, and
- Jenkins. Make sure you're looking at the right branches.
+1. Make sure that CI passes: have a look at Travis
+ (https://travis-ci.org/torproject/tor/branches), Appveyor
+ (https://ci.appveyor.com/project/torproject/tor/history), and
+ Jenkins (https://jenkins.torproject.org/view/tor/).
+ Make sure you're looking at the right branches.
If there are any unexplained failures, try to fix them or figure them
out.
@@ -40,10 +43,14 @@ new Tor release:
* clang scan-build. (See the script in ./scripts/test/scan_build.sh)
* make test-network and make test-network-all (with
- --enable-expensive-hardening)
+ --enable-fragile-hardening)
* Running Tor yourself and making sure that it actually works for you.
+ * Running Tor under valgrind. (Our 'fragile hardening' doesn't cover
+ libevent and openssl, so using valgrind will sometimes find extra
+ memory leaks.)
+
=== II. Write a changelog