15:00:35 #startmeeting Tor Browser Weekly Meeting 2024-08-06 15:00:35 Meeting started Tue Aug 6 15:00:35 2024 UTC. The chair is morganava. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:00:35 Useful Commands: #action #agreed #help #info #idea #link #topic. 15:00:43 o/ 15:00:49 o/ 15:01:25 hi folks, the pad per usual -> https://pad.riseup.net/p/tor-tbb-keep 15:01:32 o/ 15:03:37 ma1: re android security backports, I don't think there's nay reason to specifically backport to base-browser for now, as we shuffle such commits to the start of the tor-browser.git commit history the next month anyway 15:04:13 ack 15:04:31 obv if MB android becomes a thing that changes things 15:08:57 ok, so can we get a status update on where TB Android is at, and the current signing situation w/ macOS? dan_b/boklm 15:09:35 anroid 128 rebase is in review, pierov is starting comments, and I'll be looking at making a commented range diff today and then starting to reposnd to comments 15:11:41 alright excellent 15:12:21 last i checked almost all of the RR versions have had at least 1 reviewer 15:13:33 next steps for folks (unless you're working on some other blocker like the android build or signing) will be to start investigating/resolving the revew tickets 15:13:43 and possibly developing patches 15:14:16 I'll plan on on assigning them out as seems appropriate, but it would be helpful if you all could start claiming reviews in the meantime 15:14:41 as a reminder, they can all be found linked to the relevant parent audit issues in tor-browser-spec: https://gitlab.torproject.org/tpo/applications/tor-browser-spec/-/issues 15:15:47 otherwise I don't think I have anything else, are there any blockers people need help with? 15:16:09 morganava: I assigned 13.5.2 to boklm 15:16:28 But maybe you want to take them instead 15:16:44 ah yeah, I can do that 15:16:49 Builds are matching and I've already sent the tor-qa@ email (but a moderator needs to approve it) 15:16:54 do we know if the latest signing iteration has resolved our macOS problems for 14.0a1? 15:17:01 Yes 15:17:05 I tested on x86 15:17:12 ah thank christ 15:17:15 Maybe somebody should test on arm 15:17:32 115 should be unaffected, but still a good idea to check it 15:17:40 In case of spills from 128 15:18:02 Mullvad won't do the QA today at this point, but tomorrow 15:18:20 (also, we haven't built on their infra, but we have our builds) 15:18:38 alright brilliant 15:18:50 dan_b, clairehurst: woudl one of you midn verifying the 14.0a1 arm build? 15:18:56 would*, mind* 15:18:58 Apart from this, I'll give P1 to reviewing Android 15:19:08 yes plelase 15:19:19 The review is assigned to me, but I'll need someone to verify things such as resources 15:19:44 dan_b: do you have a 125-based branch in your tor-browser.git fork? 15:20:09 14.0a1? is that just stock firefox-android on our modified geckoview? 15:20:10 Or should I cherry-pick from firefox-android.git to my tor-browser.git fork for reviewing? 15:20:20 alright lets flag down clairehurst for additional review for the android rebase 15:20:23 dan_b: I think it was for macOS 15:20:31 pierov: no, I restructured in firefox-android and then jumped straight to TB 128 15:20:39 arm for mac? I can do that 15:20:39 ah then yes I can try that out 15:20:43 where is it? 15:20:54 is it just running it or what do you mean by verifying? 15:20:54 dan_b: with `git am -d`? 15:21:22 clairehurst: dan_b: https://gitlab.torproject.org/tpo/applications/tor-browser-build/-/issues/41202#note_3056376 15:21:44 pierov? whats git am? 15:21:55 There's a dmg boklm signed, it shouldn't crash at the startup 15:22:23 dan_b: it's a way for moving patches without adding the remote of different repositories 15:22:25 oh as patches 15:22:26 And yeah just assign/ping me on anything you want reviewed 15:22:29 no 15:22:32 :) 15:22:38 am is apply mail 15:22:47 i just restructured the structure of firefox-android to match tb, then added it as a remote and cherry picked the changes 15:22:58 And it's the command to work with git format-patch 15:23:13 dan_b: ack, I will work my way to review then 15:23:38 the initial 128 I discovered is a bit of a mess, the -fix is muuuch better 15:24:00 Yep, I found a couple of rebase problems with range-diff 15:24:17 But I saw you already fixed them in the final branch :) 15:25:01 Should we plan for a -2 rebase for 128.1.0 after we merge Android? 15:25:27 Or should we give absolute priority to audits? 15:25:44 what's a -2 rebase? 15:26:01 ma1: it's a rebase where we shuffle commits, squash/unsquash, reorder the patchset in general 15:26:09 ack 15:26:23 It's the last number of the branch names 15:26:32 We use it for all the cases that can't be solved with a normal MR 15:26:53 And we need to push it on top of the FIREFOX_ tag (e.g., we did a -2 rebase also for linting) 15:28:10 wfm, so long as it's just a shuffling and the total diff is the same 15:28:59 I think doing it earlier would be better 15:29:10 Because it's already time to rebase on RR 15:29:43 But if we do a reorder earlier we can wait to start the work, and do two-three versions (129, 130 and if needed 131) together 15:31:12 so wait is 14.0 following rapid release? 15:31:18 No 15:31:33 But the idea is to spread the ESR work during the year 15:31:37 At least for rebases and audits 15:31:42 yes 15:31:49 what is RR on now? 15:31:50 129? 15:31:54 today 15:32:00 Today 129 has been released as stable 15:32:10 So, 130 is going beta and 131 is starting nightly 15:32:31 I suppose post TB 14 we'll need a few months of double audits to catch up 15:32:45 The most of the work happens when in nightly, so I think we best tag to do rebases at are when a nightly ends 15:32:57 After that there are only backports that might cause conflicts 15:33:20 And we don't really have a reason to ride a beta with our patchset unless we plan of building 15:34:24 right 15:35:07 well in the short term i think we should somewhat prioritise the nightly rebases behind 14.0 must haves, and plan on catching up on audits in the fall 15:35:24 and hopeuflly be in a good spot by the time we need to start transitioning in April 15:35:49 alright any other discussion points, topics, blockers? anything people need help with? 15:36:41 Not from me. I will try to finish reviewing Android ASAP, hopefully tomorrow 15:36:57 sweet thanks 15:37:05 you still want me to try a commented range diff? 15:37:28 or should i prioritize responding to comments? 15:37:29 dan_b: no, I think I'm good with 115-125 15:37:40 splendid 15:37:50 There weren't stuff that was hard to understand. In case I added comments 15:37:50 then comments and then I can start looking at patch review 😄 15:38:07 i'll planon signing 13.5.2 today 15:38:11 wfm. I think the priority at this point is start having nightlies 15:38:19 dan_b, clairehurst: are one of you free to check the macOS build? 15:38:34 later today I mean 15:38:39 clairehurst i think said she was? but I can otherwise 15:38:43 I can do that yeah 15:39:06 ah ok 15:39:11 alright brilliant 15:39:24 then have a good week folks, lemme know if you need anything o/ 15:39:27 #endmeeting