Re: [tor-bugs] #30429 [Applications/Tor Browser]: Rebase Tor Browser patches for Firefox ESR 68

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

#30429: Rebase Tor Browser patches for Firefox ESR 68
--------------------------------------+------------------------------
 Reporter:  gk                        |          Owner:  tbb-team
     Type:  task                      |         Status:  needs_review
 Priority:  Very High                 |      Milestone:
Component:  Applications/Tor Browser  |        Version:
 Severity:  Normal                    |     Resolution:
 Keywords:  TorBrowserTeam201905R     |  Actual Points:
Parent ID:                            |         Points:
 Reviewer:                            |        Sponsor:
--------------------------------------+------------------------------

Comment (by gk):

 Replying to [comment:2 acat]:

 [snip]

 Okay, let me start by replying to the ToDos:

 > Some TODOs:

 [snip]

 > * Integrate in tor-browser-build: is the toolchain ready? would it "just
 work" to change the firefox repo to point to this one?

 No, it is not yet. The current branch is `linux_esr68_v3` in my repo (with
 probably a bunch of `linux_esr68_v$` to follow) but there are still build
 requirements missing (`nodejs` is the next one to add)

 [snip]

 > * Updater: will mcs/brade work on these?

 Yes.

 > * Onboarding: as described in #28822, this needs to be ported, since
 onboarding (bootstrapped) extension is not there anymore. I could take a
 look at this one.

 Sounds good.

 > * Onion security expectations: a couple of patches, depending on
 availability, perhaps pospeselr could work on these?

 What are the issues here? Could you file a new bug to track that work?

 > * Decide what to do with patches from #28711.

 Ideally we could backport them and have some knowledgeable Mozilla person
 looking over the result.

 [snip]

 > * Backport https://bugzilla.mozilla.org/show_bug.cgi?id=1330467 or wait
 if it's included in 68.

 It seems we need to backport them, alas. :( They got a minus for beta
 (that is esr68) inclusion.

 > * Android: should we do this after desktop patches? here or in a
 separate ticket?

 We should do it in parallel or better: not blocking the rebasing work on
 desktop patches. sysrqb will pick this up and probably decide whether to
 use a child bug or have the rebase in this ticket.

 [snip]

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