#32480: Use Github/Gitlab releases to distribute gettor binaries ---------------------------------+----------------------------------- Reporter: cohosh | Owner: cohosh Type: defect | Status: needs_information Priority: Medium | Milestone: Component: Applications/GetTor | Version: Severity: Normal | Resolution: Keywords: github, releases | Actual Points: .5 Parent ID: | Points: 1 Reviewer: phw | Sponsor: ---------------------------------+-----------------------------------
Comment (by cohosh): Replying to [comment:9 phw]: > It's a great idea to use releases and the script looks good to me! I left a few comments in the commits. Thanks! > > Are we monitoring the return code of the script? At some point, something will break and we should notice right away when the script failed to upload new Tor Browser releases. Right now this script is run manually, but this is something we should definitely do if/when it is automated in the future. I'm not quite sure how to handle this since I don't want an error to stop the update script and start over when it is run again. This wastes a lot of bandwidth and time. My current thought is that we can print out the missing releases in a log file and manually upload them later, but that's not a very elegant solution. -- Ticket URL: <https://trac.torproject.org/projects/tor/ticket/32480#comment:10> Tor Bug Tracker & Wiki <https://trac.torproject.org/> The Tor Project: anonymity online
_______________________________________________ tor-bugs mailing list tor-bugs@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs