15:00:26 #startmeeting Tor Browser Weekly Meeting 2024-07-22 15:00:26 Meeting started Mon Jul 22 15:00:26 2024 UTC. The chair is richard. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:00:26 Useful Commands: #action #agreed #help #info #idea #link #topic. 15:00:36 the pad as usual -> https://pad.riseup.net/p/tor-tbb-keep 15:00:38 o/ 15:00:49 o/ 15:02:21 o/ 15:02:44 o/ 15:02:50 ok only two small things from me this week 15:03:00 o/ 15:03:09 first off is we've deferred the google play api update until november, by which time we will have gotten it for free from the esr128 transition 15:03:18 o/ 15:03:20 \o/ 15:03:32 thanks to the 4 or 5 people who emailed me about this :D 15:03:35 Great news, one less problem :) 15:03:41 lol 15:03:56 a bit tongue and cheak but actually thx for looking out but it has been taken care of thanks i love you 15:04:03 lol 15:04:11 :) 15:04:26 second off is after our retro last week I went off and started organising things a bit better for the 14.0 release -> https://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/42754 15:04:47 for now there's one root issue with 6 or so child issues for each of the bits 15:04:54 and each of those child issues link to the various actual work to be done 15:05:22 reminder the immediate priority (apart from dev work related to the 14.0a1 release) is the ticket triage 15:05:32 (thanks for the issues already henry-x :D ) 15:06:12 ok, apart from that I've nothing else 15:06:55 What's the plan for 14.0a1? 15:06:57 oh, we do have an (optional as always) release meeting scheduled today at 1800 so if you're actively working on some part blocking the 14.0a1 release please swing by 15:07:42 Oh, okay, should I defer my q to that meeting? Or should we briefly talk about it here? 15:07:56 Re the ticket triage, how in depth should we be? Just skimming the title to see if it sounds interesting, or also reading the bugzilla? 15:08:29 re 14.0a1, we've a slot for it in the calendar for tomorrow, but it looks like nightly failed over the weekend (and android still needs to be merged last I saw) 15:08:36 but let's cover it in more depth at the release meeting 15:08:51 Tor Browser is okay 15:08:54 (desktop) 15:09:06 henry-x: it depends, i think if your first instinct is it needs further investigation/review just make the ticket 15:09:18 Mullvad Browser Windows seems to be the problem (I'm dogfooding nightlies on Linux fwiw, and they're very good :)) 15:09:22 though in the past I've definitely done probably more in-depth review work as part of triage if an issue was interesting 15:09:37 for android: i'll get to 125 today. want to try a few quick reorders to see if they are conflict light. either way then i'll start the rebase into tb 14 128 repo 🙂 15:11:59 I *think* if it my make sense to priortise the rebase in the old order for 14.0a1, and re-order for 14.0a2 15:12:06 but that can be a topic for the release meeting too 15:12:53 +1 for keeping the order, if it helps reviewing 15:13:13 sure 15:14:41 ok, any other topics or announcements or queries? 15:16:11 o/ weren't we moving the release meeting to a different day? 15:16:29 todays is the one-off you requested for this release 15:16:45 but yes, the regularly schedule one is now wed morning at 1500 iirc 15:16:58 next one would be the 31st 15:17:01 oh right, I assumed it would be at the new time instead 15:17:07 it's clashing with our meeting with pavel atm 15:17:22 we've a meeting w/ pavel? 15:17:55 uh I guess it's just me 15:18:09 lol 15:19:22 sorry to be a bother, but can we do the release meeting at the new timeslot instead please? 15:20:08 alright sure 15:20:12 thank you :) 15:20:25 * PieroV already forgot when is the new slot ^_^; 15:20:31 wed 15 utc 15:20:41 in which case, should we chat about the release's technical aspects now? 15:20:43 just before the allhands 15:20:43 ack, thanks 15:20:53 richard: wfm 15:21:12 alright, so where are we at w/ the alpha branch(es) 15:21:37 are invites going out for that? i dont have it in my calendar 15:21:52 Desktop is doing good. We've had nightlies. 15:22:22 We have nightlies also of Android, but they have only GV patches. At least theyu build 15:23:02 dan_b: it's in the tor browser calendar 15:23:06 I've tried only Linux x86_64 builds IIRC or maybe also Windows x86_64 15:24:29 Mullvad Browser has some mingw problems. I'm trying with mingw's HEAD. It has some problems (it doesn't use qualified enough names in some places) and a header/struct is still missing 15:24:47 for WebRTC yeah? 15:24:51 richard i reloard the calendar and the meeting from today popped over to wednesday (good) but they kept their time of in 2.5 hours (not ideal?) 15:25:05 I'm happily surprised the default browser agent seems not to be a problem (unless I forgot to re-enable it in my mozconfig, I have to check it agani and check with June if her patches make mine unnecessary) 15:25:22 dan_b: give nextcloud some time :p 15:25:43 oh geez 15:25:46 a second reload did it 15:25:48 thats.... 15:25:49 cool 15:26:17 Lol same here 15:26:25 I'm happy disabling webrtc for alpha if it turns out to be an annoyance for 14.0a1 15:26:43 but it sounds like rebasing the android patches are the bigger blocker 15:26:51 The alternative is to delay MB alpha 15:27:08 (well, I took for granted 14.0a1 would be desktop-only in any case) 15:27:41 i'm also ok with making 14.0a1 desktop only too 15:27:42 if the rebase gods are nice, Im hoping to have them landing tomorrow 15:28:08 ok 15:28:17 dan_b: I think it'd be wiser to do some nightlies first 15:28:22 let's plan on 14.0a1 tomorrow(ish) and 14.0a2 next week with Android too 15:28:30 I don't know if Moz is doing a point release for 128.0 15:28:34 For the pinning problem 15:28:35 i doubt we'll make significant user-facing Android changes in the intervening week 15:28:44 but no idea how well they'll build (ie: they keep adding more nimbus use stuff, I've been trying to sqash what I saw in conflicts, but its likely other users won't surface till patch review or build and run that'll crash 15:28:45 But maybe we can plan 14.0a2 to be out with the point release 15:28:49 128.0.2 dot release this week per my email 15:29:03 Is 128.0.1 being skipped? 15:29:12 It hasn't been tagged in mozilla-esr128 15:29:23 /o 15:29:24 huh not sure 15:29:35 but just got an email from release-drivers saying 128.0.2 tomorrow 15:29:37 so.. 15:29:39 vOv 15:30:39 * ma1 checks if there's any security@mozilla.org email... 15:32:06 security-list@mo, nothing other than the weekly stats 15:33:00 maybe a non-sec bugfix release. Most likely the pinning stuff? 15:34:53 are we going to need another stable release for this? 15:35:41 if it's only pinning we're good on TB 15:36:03 There are already a lot of commits in mozilla-esr128 15:36:11 After the tag we've used 15:36:28 * ma1 was looking at the git log as well 15:37:58 i briefly forgot stable is on 115 15:38:27 in any event, my preference is not to release more than necessary 15:40:39 alright, anything else from folks? 15:40:40 some of the recent commits are also on the 115 branch, but it seems they're not releasing 115.14 so it seems we can wait. 15:40:54 otherwise let us end this meeting and go about our day/lives 15:41:23 Nothing from me 15:42:03 * thorin dreams of fingerprinting week 15:43:17 ok folks, have a good week o/ 15:43:19 #endmeeting