[tor-commits] [tor/master] doc: Add a new Travis CI cron job when there's a new maint branch

[asn@xxxxxxxxxxxxxx]

commit c390f1dd7ef6f458fff9064c82f3804581de07a9
Author: teor <teor@xxxxxxxxxxxxxx>
Date:   Thu Nov 15 12:05:28 2018 +1000

    doc: Add a new Travis CI cron job when there's a new maint branch
    
    Part of 28453.
---
 doc/HACKING/ReleasingTor.md | 8 ++++++--
 1 file changed, 6 insertions(+), 2 deletions(-)

diff --git a/doc/HACKING/ReleasingTor.md b/doc/HACKING/ReleasingTor.md
index 4c87a366c..c7cd0bc11 100644
--- a/doc/HACKING/ReleasingTor.md
+++ b/doc/HACKING/ReleasingTor.md
@@ -240,7 +240,11 @@ new Tor release:
     `maint-x.y.z` branch to "newversion-dev", and do a `merge -s ours`
     merge to avoid taking that change into master.
 
-2. Forward-port the ChangeLog (and ReleaseNotes if appropriate) to the
+2. If there is a new `maint-x.y.z` branch, create a Travis CI cron job that
+   builds the release every week. (It's ok to skip the weekly build if the
+   branch was updated in the last 24 hours.)
+
+3. Forward-port the ChangeLog (and ReleaseNotes if appropriate) to the
    master branch.
 
-3. Keep an eye on the blog post, to moderate comments and answer questions.
+4. Keep an eye on the blog post, to moderate comments and answer questions.



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