[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-bugs] #30169 [Applications/Tor Browser]: Create repos on our infrastructure for TOPL related code
#30169: Create repos on our infrastructure for TOPL related code
-------------------------------------------------+-------------------------
Reporter: gk | Owner: tbb-
| team
Type: task | Status: new
Priority: High | Milestone:
Component: Applications/Tor Browser | Version:
Severity: Normal | Resolution:
Keywords: tbb-mobile, tbb-8.5, | Actual Points:
TorBrowserTeam201904 |
Parent ID: #27609 | Points:
Reviewer: | Sponsor:
-------------------------------------------------+-------------------------
Comment (by gk):
I set up the `tor-android-service` repo with `master` pointing to the
latest commit we ship in `tor-browser-build` (i.e.
6a9314aff4418a4edac33ff39fae266b097cf000). And I switched to the tpo repo
in commit ea0d9948bcb63cce9612f5a6d6e5cdad5db6561c on `tor-browser-
build`'s `master` (+ I cherry-picked that commit onto `maint-8.5` (commit
1f5d05032577524ad2600cc2fb7f28cd2d707256)).
Getting `master` updated follows the usual procedure. We'll have a bug in
Trac that needs to get fixed and if that involves fixes in `tor-android-
service` the respective user-owned `tor-android-service` repo is used for
providing the `tor-android-service` bits (wherever that is, be it on
Gitlab or our own infrastructure). Then the whole gets reviewed and the
commit in `tor-browser-build` gets updated if everything looks good. The
ticket then gets closed.
At some point we should think about tagging releases + sign them and use
git tags for our `maint-*` branches (will say stable releases).
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/30169#comment:2>
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