[tor-commits] [tor/release-0.4.1] Mention Travis/Appveyor/Jenkins URLs in ReleasingTor.md

nickm at torproject.org nickm at torproject.org
Mon Jun 10 13:37:34 UTC 2019


commit 5d4b4f948a338a41966bb2e15af5875d4df8a08f
Author: rl1987 <rl1987 at sdf.lonestar.org>
Date:   Fri May 31 09:35:19 2019 +0300

    Mention Travis/Appveyor/Jenkins URLs in ReleasingTor.md
---
 changes/doc30630            | 3 +++
 doc/HACKING/ReleasingTor.md | 9 +++++++--
 2 files changed, 10 insertions(+), 2 deletions(-)

diff --git a/changes/doc30630 b/changes/doc30630
new file mode 100644
index 000000000..0fbd8d4dd
--- /dev/null
+++ b/changes/doc30630
@@ -0,0 +1,3 @@
+  o Documentation:
+    - Mention URLs for Travis/Appveyor/Jenkins in ReleasingTor.md. Closes
+      ticket 30630.
diff --git a/doc/HACKING/ReleasingTor.md b/doc/HACKING/ReleasingTor.md
index 4c87a366c..d9864dba2 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.
@@ -244,3 +247,5 @@ new Tor release:
    master branch.
 
 3. Keep an eye on the blog post, to moderate comments and answer questions.
+
+





More information about the tor-commits mailing list