Hi everyone!
Here is my status report for July 2024.

I worked almost exclusively on the ESR transition also this month.
I reviewed the rebased patchset more deeply to find potential runtime and logic errors caused by upstream changes or similar problems [0].
For example, upstream worked a lot on search engines, and the patch we had for providing our custom default selection broke as a result, and we had to re-implement it.
Then, before the 14.0a1 release, I rebased Tor Browser and Mullvad Browser onto 128.0.
After that, I switched to audits. During every ESR transition, we check all the bugs Mozilla closed to see if some need particular attention [1].
Until last year, this work was carried out only by a person. This year, we decided to spread it to all the team and have multiple persons review each Firefox version. I was assigned Firefox 116 to 119, and so far, I've reviewed 119+118 and started 117.

Apart from that, I worked on the usual maintenance tasks: I rebased the 13.5 series onto 115.13.0esr for 13.5.1 at the beginning of the month, and yesterday, I rebased onto 115.14.0esr and 128.1.0esr for 13.5.2 and 14.0a2, respectively.
Finally, I worked on sunsetting Windows 7 support on 14.0 [2], and I updated our pipeline to fetch Firefox's translations after they were moved to GitHub [3], as this blocked 13.5.1.

Cheers,
Pier

[0] ESR 128 Patch Review (Desktop) (#42616) · Issues · The Tor Project / Applications / Tor Browser · GitLab
[1] Firefox ESR 128 Bugzilla Triage (#42757) · Issues · The Tor Project / Applications / Tor Browser · GitLab
[2] Drop Windows 7 support for 14.0 from build tools (#41185) · Issues · The Tor Project / Applications / tor-browser-build · GitLab
[3] Use the GitHub repository for firefox-l10n (#41166) · Issues · The Tor Project / Applications / tor-browser-build · GitLab

···

_______________________________________________
tor-project mailing list
tor-project@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-project

3 Likes