16:01:06 <morganava> #startmeeting Applications Team Meeting 2025-06-16 16:01:06 <MeetBot> Meeting started Mon Jun 16 16:01:06 2025 UTC. The chair is morganava. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:01:06 <MeetBot> Useful Commands: #action #agreed #help #info #idea #link #topic. 16:01:10 <morganava> pad -> https://pad.riseup.net/p/tor-tbb-keep 16:01:41 <morganava> so i suppose we should be treating this meeting a bit differently going forward 16:02:29 <morganava> i reckon we can drop updating the pad since we're doing stuffs in mostly in bbb now 16:02:59 <boklm> o/ 16:03:05 <morganava> and maybe just use this space as a sort of 'first contact point of the week' in case there are any fires or otherwise urgent tasks 16:03:33 <morganava> to chat about and/or coordinate spinoff meetings as they are needed 16:03:55 <morganava> and barring that, yield the floor to community and/or other visitors in the chat? 16:05:25 <morganava> well, i guess the only immeidiate announcement is that Juneteenth is Thurs this week, so if you take US holidays obv don't show up on Thrusday :p 16:05:56 <morganava> otherwise i'll just leave the meeting bot open for a bit in case anyone wonders in 16:06:04 <morganava> o7 16:06:38 <PieroV> I wanted to quickly discuss a couple of things without waiting for Wed 16:06:45 <morganava> go for it! 16:06:51 <PieroV> Since Wed is last day of the week at this point for some ^_^; 16:07:11 <PieroV> So, in a few hours we're getting tags for 128+140 16:07:27 <PieroV> I've seen gecko-dev has an esr140 branch 16:07:39 <PieroV> So we should be good there, but is there any update on the migration to the new history? 16:09:32 <morganava> is there any reason to not 'just try it' re bringing in the new canonical upstream git repo? 16:09:51 <morganava> ie would it cause irreperable damage? 16:10:08 <PieroV> Unknown, as nobody knows what GitLab does under the hood 16:10:16 <boklm> I think we could try it and if possible get tpa to run `git gc --aggressive` on the git server 16:10:48 <PieroV> Also, if we don't manage to pack everything, any clone of tor-browser.git will be a few more GBs 16:10:58 <morganava> i mean, seems like, worst case scenario we push it and gitlab is sad and TPA has to revert our push 16:11:15 <PieroV> So, should we switch to the official tags? 16:11:45 <morganava> actually 16:12:03 <morganava> ok, the only thing which will probably break 16:12:11 <morganava> is the bugzilla triage script 16:12:12 <dan_b> more motivation for tpa to do the scale up servers plan? 16:12:34 <morganava> if someone naively tries to build the scpreadsheet from 139 out of the one history and 140 from the other, it will probably be a bad time 16:12:49 <morganava> but i think that's just a me problem and one can just use a real commit hash in that case 16:14:10 <morganava> yeah do the switch/tag starting with 140, then the spreadsheet script can use the other branch's nightly tags 16:14:34 <morganava> starting wth esr140* 16:15:16 <PieroV> Okay, apart from that I wanted to give an update about Android nightlies 16:15:18 <PieroV> Or nightlies in general 16:15:34 <morganava> yes please :) 16:15:54 <PieroV> We merged desktop changes for 140. Windows and macOS apparently work 16:16:16 <PieroV> Linux had a small problem that we fixed earlier. Hopefully tomorrow we'll have TBB+MB nightlies for desktop 16:16:22 <PieroV> For Android there are a few blockers 16:16:48 <PieroV> tor-browser!1538, tor-browser#43856 and a reproducibility issue 16:16:54 <PieroV> Luckily, the reproducibility 16:16:59 <PieroV> issue should be easy to solve 16:17:07 <PieroV> I already worked a little bit to solve it, at least 16:17:22 <PieroV> It's only about licenses 16:17:46 <henry-x[mds]> Are there differences in the tag names with the new repo? Will our commits still be based on `FIREFOX_*`? 16:18:02 <PieroV> One is a MR, and for the other one we'll need an (actual) Android dev to take a look. I have a workaround for testing the build 16:18:41 <PieroV> No, tags are the same 16:19:30 <dan_b> for the onBackPresses i suspect clairehurst might just know the answer when she's back or if it's pressing i can look at it sooner? 16:20:52 <morganava> presuming we can ignore/allow the warning i think it can wait until claire is back 16:21:09 <morganava> presuming it isn't an urgent blocker 16:21:12 <PieroV> Warnings make builds fail 16:21:33 <PieroV> That's the default at least for Fenix 16:21:56 <morganava> right but I mean, can one annotate the function to ignore the deprecation warning in the short term 16:21:57 <PieroV> But we can probably relax that, I don't know how 16:22:22 <PieroV> Oh, right, we can do an annotation on the source in Kotlin. I was thinking about changing it somewhere else 16:23:59 <morganava> yeah presuming it's not urgent i'd rather have claire on any remainnig easy wins for project 163 if possible, but i'll have to sync w/ her on Wednesday 16:24:20 <morganava> easy wins before the end of June* 16:24:53 <PieroV> In the meantime I found that we have also unexpected repro problems with nimbus-fml again 16:25:06 <morganava> truly the most accurate project name 16:25:58 <PieroV> Which means I can open a MR at least for the rest 16:26:52 <PieroV> I almost forgot 16:26:56 <PieroV> What about 128 tags? 16:27:22 <morganava> hmm 16:27:30 <PieroV> Are we switching also that one, or are we staying on gecko-dev for 128? I think it's safe to assume gecko-dev will be still updated until 128 goes EOL 16:27:32 <morganava> probably smarter to keep 128+115 on gecko-dev 16:27:32 <PieroV> Same for 115 16:27:51 <ma1> +1 16:27:55 <morganava> on first think 16:28:39 * ma1 votes "don't touch anything until it breaks" 16:28:42 <boklm> +1 16:28:55 <morganava> lol 16:28:56 <morganava> exactly 16:29:11 <morganava> 140 is def the time of yolo and break shit 16:29:15 <morganava> magic school bus vibes 16:31:05 <morganava> anything else? 16:31:36 <PieroV> Nothing from me I believe 16:31:36 <morganava> do we need to make someones responsible for the 128 and 115 whatever rebases this week? 16:31:46 <PieroV> 128, 115, and 140 16:32:23 <PieroV> Even though 140 has lower priority (it's going to conflict more though, however I can take that one) 16:32:39 <morganava> yeah we should def get 115+128 out of the way first 16:33:07 <ma1> I can do the two rebases + the security backports 16:33:26 <morganava> oke dokey 16:34:05 * dan_b fell down a rabbit hole when google returned minecraft forge (mod loader) results for "fml feature manifest language" but it's just fuzzy google, it the minecraft mod context (it's a whole code module) it stands for "forge mod loader" 16:34:22 <morganava> lol of course 16:34:54 <dan_b> as far as i can tell, fml as feature manifest language does appear to be a moz invention. 16:35:12 <dan_b> and i struggle to believe someone didn't know what they were doing with that acronym 16:35:14 <morganava> alright if there's nothing else then let's end this 16:35:44 <morganava> have a good week everyone o/ 16:35:51 <jwilde> o/ 16:35:55 <morganava> #endmeeting