16:00:46 #startmeeting Applications Team Meeting 2025-01-13 16:00:46 Meeting started Mon Jan 13 16:00:46 2025 UTC. The chair is morganava. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:00:46 Useful Commands: #action #agreed #help #info #idea #link #topic. 16:00:57 it's 2025-01-13 aka 2024-13-13 16:01:10 lol 16:01:13 o/ 16:01:24 the apd as usual: https://pad.riseup.net/p/tor-tbb-keep 16:01:40 it's the start of the year, so perhaps a good time to prune out your old entries 16:02:14 o/ 16:03:08 o/ 16:03:18 good morning everyone 16:03:29 brizental: I just sent a nice email to BrowserSstack re quota 16:03:32 oke 16:04:16 14.0.4 and 13.5.11 went out last week 16:04:25 (thanks ma1 for the help) 16:04:30 morganava: thanks! hope they give us unlimited access to app automate as well 16:05:01 this week we have Tor/Mullvad 14.5a2 on the docket 16:06:29 PieroV has already rebased TB and I'm sure MB is imminent 16:06:39 morganava: there's a MR already 16:06:48 Let me check if it's draft by mistake 16:07:01 \o/ 16:07:35 mullvad-browser!154 16:08:05 My tuesday is completely booked, so can someone else take the release-prep tomorrow? 16:08:23 and is anyone keen to sign+publish this week? 16:08:46 I can do anything after this meeting 16:09:07 i suppose we should somehow formalise a signing rotation 16:09:14 E.g., relprep today and build overnight 16:09:19 I can sign+publish if necessary 16:10:18 when I'm done, anyway, I'd like to mainstream some QoL tweaks to the signing process I've got in my local tbb repo ;) 16:10:29 alright that works for me 16:10:32 ma1: yes please :D 16:11:23 ok PieroV release prep, PieroV+ma1 build: ma1 publish? 16:11:31 wfm 16:11:56 it looks like the devmole build script isn't working given no hashes appeared for last weeks build 16:11:56 wfm too. I still need to braintransplant my new 96GB machine, so I'd prefer to build remotely 16:12:01 i'll poke mullvad 16:12:14 ma1: sure, I can build locally 16:12:18 jesus, you coan build so many noscripts with that 16:12:38 ok 16:12:42 lol, emulated in android studio 16:13:28 the other thing from me is that right before break I sent out a pair of proposals emails re: updating some gitlab processes 16:13:56 issue labelling and using separate issues for uplift+backports 16:14:31 if you haven't already please have a read and comment if you've any wisdom to share 16:15:08 oh ma1! congrats on a new comp? I just "upgraded" from 64gb ram to 96 over the holidays too 16:15:29 dan_b, ty, I guess RAM is a must in android dev land :) 16:15:41 and a reminder from last year that I shifted around 1:1s to all be on Tuesdays now rather than Thursdays so don't let that surprise you 16:15:48 tho i also learned modern motherboard advertised max capacity is like "with ideal ram conditions" so just adding more sometimes doesn't work, had to swap the 64 for entirely new 96 😕 16:16:31 I had it built by tuxedo (a German linux hw shop), so it's under their warranty :P 16:16:54 and finally, i've scheduled our sync w/ Mozilla for Thursday at 1600 UTC; if you're interested in being in on that feel free to join otherwise you're more than welcome to ignore 16:17:29 ok i think that's everything out of my head 16:17:39 does anyone have topics of discussion to go over? 16:17:44 I do 16:17:50 go for it PieroV 16:18:00 We're still finalizing the process for RR rebases 16:18:18 However, when shall we start with them? 16:18:52 morganava: the calendar invite for the moz colab looks like its for ... 1400 utc? 16:18:57 I think we should start them ASAP 16:18:59 The blockers would be the process itself (which is almost figured out, I believe), and any patchset work we want to do 16:19:03 or maybe I can't read 16:19:07 dan_b: yeah I messed up the initial invite but since edited it 16:19:35 * morganava double-checks 16:19:42 * dan_b awaits nextcloud figuring that out 16:19:44 However, can we even put any further patchset big work on our schedule? 16:20:43 pierov: are you happy enough with the android patchset to start RRing it? 16:21:11 (yes confirmed it is 1600 UTC on Thurs) 16:21:28 dan_b: there's still a too big commit 16:21:38 (morganava it moved for me when I accepted the updated one!) 16:21:38 Or maybe even a couple 16:22:24 But there are also desktop/shared stuff we could fix (e.g., the onion security expectations) 16:23:09 But it all boils down to what we want to do during these 3 months before 14.5 stable (IIRC it's scheduled around April 20) 16:23:36 perhaps we just get going with RR rebasing, and do any remaining patch shuffing/splitting during the 15.0 release cycle in the summer vOv 16:23:52 Yep. I've checked Moz's calendar 16:24:11 And we have 3 scheduled alphas (4, if we count 14.5a2) 16:24:59 agreed: we can never hit perfection, but you got in some big improvements, can always optimistically schedule more for the summer and get going now 🙂 16:25:57 that works for me 16:26:26 PieroV: I'm prioritising the rebase template this week and have gotten through most of your suggestions 16:29:03 ack, thanks 16:29:24 * ma1 takes advantage of this temporary silence to thank PieroV for taking on letterboxing uplifting <3 16:30:15 :) 16:30:32 ok, any other topics for discussion? 16:30:45 ma1: yw :) But sadly I'm stuck on Windows tests failing 16:31:21 PieroV, let's chat later of what went wrong(er) since last morning with that 16:33:17 and looks like BorwserStack has acquiesed to our request :D 16:33:43 morganava: whaat! that was fast haha and great news! 16:34:07 * ma1 suspect it's not everyday that a browser vendor asks something :D 16:34:43 morganava: can confirm, it's now listed as an unlimited product 16:34:48 \o/ 16:34:57 the power of email 16:36:08 alright folks 16:36:31 i hope you all had a relaxing break, slept a lot and had all the right snacks 16:36:31 woo congrats 16:36:40 if there's nothing else today, then let's call it :) 16:36:55 ty have a great week 16:37:27 ok. later everyone o/ 16:37:30 #endmeeting