Re: [tor-bugs] #25741 [Applications/Tor Browser]: Create tor-browser for mobile branch based on mozilla-central

["Tor Bug Tracker & Wiki" <blackhole@xxxxxxxxxxxxxx>]

#25741: Create tor-browser for mobile branch based on mozilla-central
----------------------------------------------+--------------------------
 Reporter:  gk                                |          Owner:  sysrqb
     Type:  defect                            |         Status:  assigned
 Priority:  Very High                         |      Milestone:
Component:  Applications/Tor Browser          |        Version:
 Severity:  Normal                            |     Resolution:
 Keywords:  TorBrowserTeam201805, tbb-mobile  |  Actual Points:
Parent ID:                                    |         Points:
 Reviewer:                                    |        Sponsor:
----------------------------------------------+--------------------------
Changes (by gk):

 * cc: boklm (added)


Comment:

 I guess we can use that (parent) bug to work on our general idea of
 automatically rebasing our patches against mozilla-central and figuring
 out what to do in case everything is okay/not okay. Should we run this
 rebase attempt daily? Weekly? Bi-weekly? I think I am against daily as a
 rebase failure might just be due to a broken m-c patch which is get fixed
 in $timeframe on mozilla-central "automatically" by Moz people. So, maybe
 starting with rebasing once a week could be a thing we try?

 I guess having an automated system that sends notification email about the
 result of the rebase would be good, indicating on which git commit the
 rebase was on. In case everything is fine I can do the rebase locally and
 push the result to our nightly branch.

 If it is not okay, we should file a ticket I guess with a special keyword
 and then someone from the team (maybe we create a particular role for that
 that is assigned on a weekly basis, like "rebase-hero") is looking into
 that and fixing up the issues. The idea would be to have things ready for
 review and merged until the next rebase attempt is running.

 If things are more thoroughly broken we can decide on a case-by-case basis
 what to do but fixing those problems will always be a top prio because we
 need enough testing time with functional builds to get the next Tor
 Browser for Android into stable shape.

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/25741#comment:8>
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