diff options
| author | teor <teor@torproject.org> | 2018-11-15 12:05:28 +1000 |
|---|---|---|
| committer | Nick Mathewson <nickm@torproject.org> | 2019-05-30 09:02:13 -0400 |
| commit | c390f1dd7ef6f458fff9064c82f3804581de07a9 (patch) | |
| tree | a923677d9b274ab188920ecbb2de578f530f7dca /doc/HACKING | |
| parent | 70553a91343e242e05e569d59584674a21d09679 (diff) | |
| download | tor-c390f1dd7ef6f458fff9064c82f3804581de07a9.tar.gz tor-c390f1dd7ef6f458fff9064c82f3804581de07a9.zip | |
doc: Add a new Travis CI cron job when there's a new maint branch
Part of 28453.
Diffstat (limited to 'doc/HACKING')
| -rw-r--r-- | doc/HACKING/ReleasingTor.md | 8 |
1 files changed, 6 insertions, 2 deletions
diff --git a/doc/HACKING/ReleasingTor.md b/doc/HACKING/ReleasingTor.md index 4c87a366cc..c7cd0bc111 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. |