[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

Re: [tor-bugs] #14744 [GetTor]: Automate upload of latest Tor Browser to cloud services

#14744: Automate upload of latest Tor Browser to cloud services
-----------------------------+--------------------
     Reporter:  ilv          |      Owner:  ilv
         Type:  defect       |     Status:  closed
     Priority:  major        |  Milestone:
    Component:  GetTor       |    Version:
   Resolution:  implemented  |   Keywords:
Actual Points:               |  Parent ID:
       Points:               |
-----------------------------+--------------------

Comment (by mrphs):

 Deployed as in... deployed on the running GetTor machine? or implemented
 and pushed to the repository?

 In a typical Tor workflow, ideally you'd create a branch for your new
 feature and push it to the git, then set the ticket as 'needs_review'.
 Then $someone would review the code and if everything's fine it gets
 merged to the master. Then it can get deployed.

 While skipping all this could speed up the process, but might also
 introduce unwanted (human) errors.

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/14744#comment:4>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs