15:16:22 <richard> #startmeeting Tor Browser Weekly Meeting 2024-04-22
15:16:22 <MeetBot> Meeting started Mon Apr 22 15:16:22 2024 UTC.  The chair is richard. Information about MeetBot at http://wiki.debian.org/MeetBot.
15:16:22 <MeetBot> Useful Commands: #action #agreed #help #info #idea #link #topic.
15:16:39 <richard> pad per usual: https://pad.riseup.net/p/tor-tbb-keep
15:16:41 <PieroV> o/
15:16:46 <boklm> o/
15:17:06 <ma1> o/
15:17:54 <dan_b> o/
15:18:02 <richard> FYI I'm going to be afk until evening my time this Thursday, and afk next Monday
15:18:20 <PieroV> ack
15:18:34 <PieroV> ma1 and me will be AFK Thursday as well
15:18:49 <ma1> and Wed next week.
15:18:58 <PieroV> Yep
15:19:25 <richard> in that case, I'll see about getting release-prepping alpha today, and so hopefully we'll have something for boklm to sign+publish while we're away then :3
15:19:48 <dan_b> i'm out for a few hours my tuesday morning
15:20:07 <PieroV> richard: should we keep on hold tor-browser!1000, 1001, and the related but not yet existing tor-browser-build MR?
15:20:11 <richard> dan_b, clairehurst: are there any pending android patches which may are important to get into alpha before say Tuesday evening?
15:20:22 <dan_b> i'm clear
15:20:41 <dan_b> as far as i know we're good
15:20:51 <richard> PieroV: clooking
15:21:00 <richard> um, those are the c-bindings to liblooking
15:21:01 <richard> anyway
15:21:03 <richard> looking*
15:21:10 <clairehurst> Yeah me too
15:21:19 <PieroV> It's some changes in localization files
15:21:28 <PieroV> They should be fine
15:21:38 <PieroV> But last we'll want to have a nightly with them first
15:22:04 <richard> ok, preusming they're good let's get them merged and if they're ok in nightly
15:22:18 <PieroV> (I'm already creating one for Linux in tb-build-03)
15:22:35 <richard> we can plan on building tomorrow
15:22:46 <richard> (or earlier if there are no pending problems)
15:22:56 <richard> and speaking nof which, it looks like macOS builds were failing in nightlies over the weekend
15:23:03 <richard> has anyone investigated that this morning?
15:23:12 <PieroV> Yes
15:23:14 <PieroV> My bad
15:23:20 <PieroV> I already fixed this morning
15:23:40 <richard> excellent :)
15:23:42 <richard> ok
15:23:56 <boklm> tor-browser-build#42536
15:24:06 <richard> bot?
15:24:12 <PieroV> tor-browser#42536
15:24:25 <boklm> ah, yes, tor-browser, not tor-browser-build
15:24:26 <richard> :)
15:24:49 <richard> ok, onto any discussioni points?
15:25:02 <PieroV> I have one + one announcement
15:25:35 <PieroV> The discussion, hopefully short is: what if we asked sysadmins if we can make tbb-dev ro and automatically reply any poster to post an issue on GitLab instead?
15:26:06 <PieroV> Either the few emails we get there are spam, or they'll get that as an answer
15:26:17 <PieroV> (to open an issue instead)
15:26:22 <richard> i'm not sure i'm even on that list
15:26:39 <PieroV> You should have the password to manage it... At least I think you gave it to me ^_^
15:26:47 <boklm> in the past we used the list for discussions and/or announcements
15:26:49 <richard> so no objection from me
15:26:49 <ma1> richard, I had the same doubt (for me) but then I've seen a post of yours from July :)
15:27:14 <ma1> +1, sounds like a good idea
15:27:24 <richard> yeah sounds good to me
15:27:38 <richard> does TPA manage those lists?
15:27:48 <PieroV> I think so
15:28:56 <richard> alright sounds good to me
15:29:17 <richard> and i see you've been developing some rebase automation 👀
15:29:27 <PieroV> Now, for the announcement: I've written a script to keep a few branches updated!
15:30:02 <ma1> \o/
15:30:05 <PieroV> Yep, rebase automation! I have 6 branches {base,tor,mullvad}-browser-esr115-13.{0,5} that I'm planning to keep updated
15:30:45 <PieroV> So far the script takes them, rebases base-browser onto gecko-dev/esr115 and other browser onto base-browser
15:31:15 <PieroV> Plus it cherry-picks new commits and tries to shuffle the fixups to their places
15:31:37 <PieroV> So, when a new tag is out, all we should need to do is cherry-pick from these branches and review
15:32:04 <PieroV> At this stage, I'd like to try it for a while and see how things go, but we might create a bot to run it in the future
15:32:32 <PieroV> Also, the next steps would be to run builds on every changed repository and possibly run tests
15:32:43 <PieroV> But at least for now we should have this first step :)
15:32:47 <richard> \o/
15:32:59 <boklm> \o/
15:33:14 <dan_b> oooh
15:33:27 <ma1> great PieroV!
15:33:48 <PieroV> At the moment it's in a repository of mine. I don't think it belongs to tor-browser.git, since the main branch is constantly changing
15:33:53 <dan_b> does this go hand in hand with your idea to keep an alpha branch post esr128 updating each release so next esr we're like already there?
15:34:21 <PieroV> Theoretically it should
15:34:33 <dan_b> well that seems potentialful 😄
15:34:48 <ma1> loosely realated, have we got a policy preference for python over bash for tools/torbrowser scripts? I was thinking of one for certdb updates, and it would be like 3 lines of bash vs whoa in python :P
15:35:06 <PieroV> But I haven't tried yet, because cherry-picking from ESR to RR usually involves conflicts
15:35:25 <PieroV> ma1: I think the preference is to use the easiest one for the goal
15:35:30 <richard> ^this basically
15:35:48 <richard> even if it's perl ;)
15:35:54 <ma1> okey dokey
15:38:19 <henry-x> .sed script is also ok, haha
15:38:54 <richard> ok maybe I do have an opinion after all
15:39:02 <richard> anyway
15:39:05 <dan_b> LOL
15:39:05 <richard> any furhter points?
15:39:13 <PieroV> not from me
15:39:14 <richard> otherwise let's end it yeah?
15:39:28 <dan_b> actually, we do have one macos user, isn't Gnu Sed and mac sed a bit different?
15:39:55 <richard> hmmmmm!!
15:39:57 <dan_b> i've run into that problem before
15:40:06 <richard> i think i've runinto issues w/ macOS grep in the past as well
15:40:29 <dan_b> all those bsd versions of tools forked 30 years ago and less nice upgrades added long the way since
15:40:56 <dan_b> but yeah all good
15:41:16 <richard> alright something to think about inn future scripts then :p
15:41:18 <richard> later folks o/
15:41:20 <richard> #endmeeting