14:59:28 #startmeeting Tor Browser weekly meeting 20 December 2021 14:59:28 Meeting started Mon Dec 20 14:59:28 2021 UTC. The chair is sysrqb. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:59:28 Useful Commands: #action #agreed #help #info #idea #link #topic. 14:59:36 Hello! 14:59:38 hi! 14:59:39 o/ 14:59:52 * sysrqb remembers their clock is ~30 seconds faster than meetbot's 15:00:00 Pad: https://pad.riseup.net/p/tor-tbb-keep 15:00:48 Hi! 15:01:03 o/ 15:02:02 o/ 15:04:06 o/ 15:05:09 GeKo: I'm happy to see your comment on https://gitlab.torproject.org/tpo/applications/tor-browser-build/-/issues/40345#note_2767389 15:05:20 I was going to ask if that was on boklm's radar 15:05:29 but it seems we're in a better situation than I expected 15:05:39 assuming the build is/was successful 15:06:41 it was as i wrote 15:06:42 oh, tor-browser-build!385 says it was successful, excellent. 15:07:05 great 15:07:09 yeah, that one made me nervous so i tried over the weekend 15:07:20 to figure out how urgent/complicated it is 15:07:34 we are lucky it seems 15:08:40 yeah, i'll take that outcome 15:09:42 okay. Tor Browser 11.0.3 is syncing onto the webservers now 15:10:01 \o/ 15:10:09 it should be ready in ~4 hours 15:10:33 boklm: are you planning on publishing the blog post today or tomorrow? 15:10:41 I can prepare the blog post after the meeting 15:10:51 and publish it later today 15:11:04 okay, sounds good 15:11:17 yes 15:11:25 we should try to get 11.0.3 out today 15:11:32 so we have tomorrow for assessing fallout 15:11:40 before everyone vanished on wed 15:12:14 a couple more forum users made promising noises, so fingers crossed 15:13:16 okay, good 15:15:01 boklm: i'll take the mozilla95 toolchain updates and look at the geckoview build failure, yes? 15:15:11 sysrqb: ok 15:15:14 i think you are busy working on other things? 15:15:25 yes 15:15:31 okay 15:15:41 what is the plan for a new tba release? 15:15:52 currently, we should have nightlies based on Fenix94 15:16:37 I was debating rushing a TBA Alpha release this week 15:16:59 based on Fenix94, which is better than the current situation 15:17:33 well, i meant stable release 15:18:13 at this point, we won't have a stable release until next month 15:19:38 how many alpha releases do you think are necessary before stable? one for 94 and one for 95, at least? 15:19:56 donuts: it depends on when we publish the alpha release 15:20:03 but yes, probably 15:20:06 with an alpha Fenix94 this week, we could get a stable Fenix94 early next month while we work on the 95 update? 15:20:06 right 15:20:24 maybe skip the 95 update and switch to 96? 15:20:38 boklm: yes, that would be the goal, if we build a last-minute alpha this week 15:20:40 because we somehow need to catch up 15:20:55 and there are 96 betas available 15:21:35 GeKo: yes, but getting a working Fenix95 build will make getting Fenix96 builds easier 15:21:56 well, it depends 15:22:19 if mozilla fixed things in the 96 cycle that we hit in the 95 one and solve on our own 15:22:33 than this saves us precious time 15:23:34 like if they revert patches that cause e.g. build issues for us there is no need that we spend time fixing those build issues ourselves 15:23:56 but we should be quite close with getting Fenix95 building, so I believe spending some time on that is more worth our time right now 15:24:17 compared with starting the toolchain work again for Fenix96 15:24:38 this should be a smaller "stepping stone" 15:25:48 because if there are larger problems in Fenix96, then jumping directly there will block any release 15:26:05 instead of allowing us to release based on Fenix95 in January 15:26:23 so it sounds like the plan is Fenix94 Alpha this week (if possible, given this 'week' is two days) -> Fenix94 Stable in Jan, then figure out what to do with 95/96 separately? 15:27:00 donuts: yes, that's a fair summary 15:28:13 we can also look at how many toolchain updates are needed for 96 before deciding if we skip 95 15:28:32 ideally, we'll have a Fenix 95 alpha or Fenix96 alpha concurrently with the Fenix94 stable 15:29:41 boklm: good idea, I'll run the commands after this meeting 15:31:32 Jeremy_Rand_Talos_: Hrm. Yes. We planned on discussing the ports before next year 15:32:13 Unfortunately, as you can see, we're still overloaded 15:32:28 sysrqb, indeed. Based on the above discussion it sounds like Fenix chaos is wrecking timelines? 15:33:13 yeah 15:33:49 but, boklm is looking at macos-aarch64 due to potential impending doom on mac M1s by Apple 15:34:14 so I wonder if boklm could begin looking over some of your patches next year 15:34:42 Jeremy_Rand_Talos_: keeping up with Android is already most of a full-time job for boklm, though 15:35:05 so reviewing your patches will likely be slow, regardless 15:35:40 sysrqb, That would work for me. I don't know how much of my code will be applicable for macOS, but if doing them together makes review easier, I have no objection. 15:35:54 I can discuss this with boklm separately, and maybe we can come up with a plan 15:36:08 yes, I think I can start reviewing them in january 15:36:39 boklm: fyi I added some text to the bottom of the 11.0.2 release post on the forum about why readers couldn't view bugs 40698 and 40721 anymore, feel free to copy parts of it or ignore entirely (assuming nobody cares if the issues are "fixed") 15:37:09 ok. So I guess I'll do a git rebase late December and make sure everything works with current master. 15:37:11 donuts: ok 15:38:02 I don't expect any merge conflicts, but can't hurt for me to verify that before you start reviewing. 15:38:17 that sounds good 15:39:07 boklm / sysrqb, feel free to ping me on IRC or email or the GitLab threads to coordinate so that we can make sure everyone's time is being used most frugally 15:39:44 Okay 15:39:58 ok 15:40:59 the only other topic I have for today is making sure we have coverage in case of an emergency release over the holidays 15:41:12 i can take lead, so I just need a second builder 15:41:31 I'm free for building 15:41:32 will anyone be around that I can ping? 15:41:39 great, thanks richard 15:41:39 I have never released a build, but I can help if needed 15:41:56 i can build, too 15:41:56 I should be able to build too 15:42:11 okay, so the entire team can build, great :) 15:42:34 there is the question as well for prepping desktop releases at the begin of january 15:42:43 i guess i am doing those at least 15:42:51 yep, we'll need to take down the campaign too – I'll post a ticket about that 15:43:18 great, richard that's a ticket you could work on 15:43:26 on that subject everyone's hard work has 100% paid off, and we're currently sitting at $756,685.65 raised with the match \o/ 15:43:29 so thank you! 15:43:33 dope 15:43:37 yeah 15:43:38 Nice! 15:43:44 nice 15:43:49 nice 15:43:52 donuts: I'll see about writing a revert patch tomorrow for the eoy campaign 15:44:32 GeKo: I can prep 11.0.4 on Jan 05 15:44:46 no worries 15:44:52 that sounds great, thanks everyone 15:44:53 i definitely won't be opposed to you helping, but if you need to work on other things then that's okay, too 15:44:58 i can do it. there is enough in tba land to do i think 15:45:09 no, i am still in tor browser land for the time being 15:45:11 thanks 15:45:48 Apart from the reordering I don't have anything in my bucket 15:46:13 you could start looking at fixing the test suite 15:46:19 or getting used to it 15:46:31 seems like a useful experience :) 15:46:38 Okay, is there an issue related to it? 15:46:48 that way you could test your re-ordered patches, too 15:46:55 well, the tests are busted 15:47:07 i can file a ticket for the general esr91 work if you want 15:47:19 "make tests for esr91 pass, thx" :) 15:47:19 Okay, thanks 15:47:26 Ahaha 15:47:39 PieroV: i started poking at the testsuite, but I didn't get very far 15:47:46 you may want to start with looking at tor-browser-bundle-testsuite#40006 15:48:07 yeah 15:48:12 but trying the current version and see what breaks is probably the best place 15:48:15 Okay, I will do it 15:48:16 to start 15:49:09 gacar filed some tickets, too. so, there is plenty to do. 15:49:22 we'll see how important that is compared to upcoming sponsor work etc. 15:49:37 but getting things started would be good 15:51:06 GeKo: you have your "get 11.0.3 out" item bolded, did we cover the parts of that you wanted? 15:51:30 i think we are good, yes 15:51:48 okay, great 15:52:05 i don't see any other discussion topics on the pad 15:52:28 Maybe about the reordering 15:52:43 I'm waiting for feedbacks if the squashes sound good 15:53:18 Then I'll push my branch 15:53:22 (I'm also awaiting review for the tor-browser#40679 fixes, but no rush until the new year I suspect :) ) 15:53:35 yeah 15:53:50 i might not finish them tomorrow :) 15:54:14 but the moat one i will so you can build more s96 stuff on that 15:54:45 PieroV: i gonna look at that tomorrow 15:54:54 but richard should look too 15:55:03 yeah i'll look as well 15:55:16 Thank you :) 15:55:35 fyi richard, we presented some torconnect 2.0 stuff at the DRL Gathering and it went down well :) 15:55:44 woo! 15:55:49 PieroV: we looking at tor-browser#40562 then? 15:55:58 folks were particularly excited about the tor settings changes actually, so I'll post a separate ticket for those and we can review them properly in the new year 15:56:03 donuts: ooh you'll have to fill me in 15:56:09 richard: yes 15:56:11 richard: yep 15:56:16 great and great 15:58:10 Alright. And with that, I with you all happy holidays and a happy new year. You all did great work this year 15:58:32 and see you at the next meeting in 2022 15:58:38 Seconded :) 15:58:41 thanks sysrqb! happy holidays and great work everyone! :D 15:58:43 thanks everyone 15:58:48 o/ 15:58:48 Thanks! Happy holidays and a happy new year to everybody :) 15:58:55 s/i with/i wish/ :) 15:59:05 #endmeeting