17:59:07 #startmeeting Tor Browser Release Meeting 2022-10-17 17:59:07 Meeting started Mon Oct 17 17:59:07 2022 UTC. The chair is donuts. Information about MeetBot at http://wiki.debian.org/MeetBot. 17:59:07 Useful Commands: #action #agreed #help #info #idea #link #topic. 17:59:13 release meeters assemble 17:59:19 o/ 17:59:20 o/ 17:59:23 pad is here: https://pad.riseup.net/p/tor-browser-release-meeting-keep 17:59:33 pls update kthanx 17:59:39 no 17:59:51 i mean ok 18:00:05 :< 18:00:10 >:[ 18:00:28 * ma1 lurking 18:03:47 I think I'm done for discussion points 18:03:54 ty pierov 18:04:06 * donuts is reading the pad... 18:04:30 when's 12.0a4 due? 18:04:34 * richard quickly skimms through board to see if any other issues stand out as blockers 18:04:45 oh 25/10 18:05:01 this week should see the next stable release, and then alpha after 18:05:15 so release prep will probably start on alpha this week 18:05:28 wfm 18:05:50 is the release cal wrong then? 18:05:53 12.4 ESR is already rebased, we should squash and maybe merge another pair of MRs first 18:05:58 1.5.5 will be a week earlier? 18:06:11 donuts: we don't have a real calendar for stable at this point 18:06:15 we got tags last week 18:06:25 we're doing the backports, not Moz 18:06:38 yeah 18:06:42 So we're late in a certain sense :D 18:06:54 right, I'm looking at nextcloud though which says Oct 25th for both stable and alpha 18:07:50 in any case, want to continue with the discussion items? 18:07:55 25th would be the rebase due-date 18:08:11 oh ha 18:08:20 I saw "re..." and my brain populated the rest with -lease 18:08:34 right, I see now 18:08:36 ty 18:11:52 okay we're just talking in the pad now 18:12:23 donuts: I think we can go with your question about the multi-lingual? 18:12:30 * questions 18:12:39 is that going to miss 12.0a4? or will it make it? 18:12:45 Merged! 18:12:50 okay great 18:12:53 So it's going in 12.0a4 indeed 18:12:58 I'm concerned about the lack of alphas, and it's a very big change 18:12:59 It was a blocker to it :) 18:13:06 (cc richard) 18:13:12 At least IIRC from previous meeting 18:13:21 Yeah, also the tor-launcher change is a big one 18:13:47 we chatted about potentially delaying 1 month, or doubling up on november alphas last week I think 18:14:10 Yeah, I think I meant "doing an alpha also in November" 18:14:20 For 11.5 stable we skipped the alpha 18:14:29 And released a pair of weeks after the corresponding Moz release 18:14:34 we can always delay stable some weeks 18:15:04 QAing localization issues can be a blind spot for us 18:15:06 (like 91.x was released on 10 July, and we released the 11.5 based on that version around the 25th of July, or something similar) 18:15:11 we don't get a lot back from alpha testers at all 18:15:23 in fact pierov usually finds most of the bugs themself :D 18:15:29 :D 18:15:31 hm 18:15:33 but that worries me a little with a change of this scope 18:15:44 I hope things are going to change when we merge the localization in tor-browser.git 18:15:58 RTL languages are also a big blind spot as well 18:16:06 We could get rid of the importing script, and at that point running the nightlies on the latest and greatest translations 18:16:09 yeah, is hard to get translators to give feedback on the alphas :S 18:16:15 I can ask comms to do another bunch of social posts, but last time the entire campaign maybe netted us three-ish testers 18:16:24 :( 18:16:36 this is the current state of activity in the alpha feedback section too: https://forum.torproject.net/c/feedback/tor-browser-alpha-feedback/6 18:16:40 it's... quiet... 18:16:42 so we do have the outreachy candidate pool 18:16:42 too quiet 18:16:48 the thing is they translate and then the alpha comes out some months later, they are not interested anymore. maybe the nightlies will be better 18:17:25 emmapeel: ah, that's a shame :( 18:18:01 although maybe they'll be more motivated at testing this change? any bugs should be more obvious than the odd incorrect string 18:18:22 sure 18:18:24 we could do a special forum post too 18:18:32 with instructions of what to test 18:18:38 but everyone's obviously very busy atm 18:19:35 maybe we can dogfood a little and ping it round internal too 18:20:21 what do you think richard? could you do an email when we publish 12.0a4? 18:20:42 yes I think that is a good plan 18:20:59 also what web changes should I start coordinating here, if any? 18:21:12 to https://www.torproject.org/download/ 18:21:56 (just noticed the YEC also on that page - nice!) 18:22:06 ha yep! 18:22:12 donuts: we will have only one language 18:22:24 At the moment we're using _ALL as a suffix, instead of the language 18:22:32 Let me double check in my testbuilds 18:23:08 Yes, _ALL uppercase 18:23:14 hmm 18:23:21 Like tor-browser-linux64-testbuild_ALL.tar.xz 18:23:24 well we'll need some change to the webstie for alpha 18:23:32 (we'll have the version instead of testbuild) 18:23:47 right now there's a big list of locales we use to generate both the stable and alpha downoad pages 18:23:59 richard: yep 18:24:29 so if there are web changes to be made we need that soooon 18:24:47 The big table should disappear: https://www.torproject.org/download/alpha/ 18:24:49 oh shit we need that very soon, for 12.0a4 18:24:59 damn pierov i need to read more 18:25:23 And we could add the instruction on how to change the language, if it's wrong 18:25:53 So new screenshots, too. If everything goes well, they could be taken from today/tomorrow's nightly 18:26:18 okay, I can start looking into this tomorrow after I get my hands on a nightly to test it 18:26:33 donuts: I can probably generate a testbuild, if needed 18:26:44 (either me or possibly richard too) 18:26:56 pierov: thanks, I may as well wait for the nightly at this point I guess 18:27:09 if it doesn't fail :D 18:27:21 ha 18:27:25 fingers crossed 18:27:40 do you think we need some first-launch UX? 18:27:46 PieroV: latest in tor-browser-build/main ? 18:27:57 with the option to override the automatic language selection? 18:27:59 I'll get that going 18:28:01 donuts: you said we wanted to update the onboarding to include it 18:28:10 richard: yes, I've merged a few hours ago 18:28:17 excellent 18:28:21 pierov: yeah, I've since discovered issues with that approach 18:28:28 donuts: once you go to the language page it should stay selected forever 18:28:29 namely our current onboarding is bad 18:29:15 maybe we need a chrome banner on both torconnect and about:tor 18:29:41 I'll have a think about that tomorrow too 18:30:08 okay I am done thinking out loud now 18:30:17 Maybe we can add a direct link? 18:30:29 pierov: yeah that's what I'm thinking 18:30:29 Like about:preferences#general-language or whatever it is 18:30:39 just a warning as to what's changed and a link to prefs 18:32:05 okay let's move on 18:32:59 Chrome font size 18:33:10 It's currently tor-browser!394 18:33:36 I thought it would have looked worse, but it's acceptable after all 18:33:44 \o/ 18:33:47 i'm glad lol 18:34:18 However, we don't contain any preset for people using like font: caption, font: icon etc... which looks in a certain way on macOS 18:34:34 But developers shouldn't rely on these anyway imho :P 18:35:02 sorry I don't understand the first bit 18:35:06 what do you mean? 18:35:14 In CSS you can set special fonts to match your OS 18:35:21 Like font: icon, or font: caption, or font: menu 18:35:25 ahhhh gotcha 18:35:30 We completely normalized those 18:35:52 To the same value, we don't apply any customization to normalize to what would the platform have normally 18:36:05 (macOS set some of them to bold) 18:36:10 will that break things like emoji or symbols in page titles? 18:36:18 No 18:37:15 donuts: these will be rendered all the same, that's the only thing https://www.w3schools.com/cssref/tryit.asp?filename=trycss_font_caption 18:37:35 In Linux they're already the same, on macOS they might be a little bit different 18:37:46 oh I see 18:37:53 across the whole browser? 18:38:23 The original patch normalized them also if used in privileged pages, the new patch will not normalize them in the chorme 18:38:29 And this fixes the bad behaviors 18:38:39 i'm having a hard time envisaging what the actual differences could look like, but I guess I'll find out soon anyway :) 18:38:48 I see 18:39:02 well I'll shout if I notice anything weird 18:39:11 ahaha, okay :) 18:39:42 richard: do you want to talk about 12.0 blockers? 18:40:07 "Various Review Mozilla XXXXXX tickets" <- i'm hoping those aren't roman numerals :D 18:40:54 of course they are 18:42:03 haha 18:42:12 nothing to talk about really 18:42:28 i think ma1 is planning on going through his this week iirc from the today's meeting pad 18:42:42 but not much dev work expected there 18:42:45 richard, confirmed 18:42:47 cool sounds good 18:43:09 and dan_b has a similar amount as well 18:43:52 i have two with MRs out and two more to look at this week 18:43:57 and the audit issue resolutions are pretty much copy contents of issue into doc in tor-browser-specs and commit/close :p 18:44:33 fantastic 18:44:46 okay action items for me: 1. coordinate web for multi-locales, 2. think about first launch UX for multi-locales, 3. ask comms to fire off some alpha tester posts/tweets after 12.0a4 18:45:08 and i'll have testbuild for you later today with muti-locales 18:45:14 lovely tyvm 18:45:53 I think we're all good then? 18:46:21 richard: what about pref audit? 18:46:57 i have that one on my plate, not sure how much of it has already done 18:48:18 okay; I can take the macOS bug, it should be easy enough to solve 18:48:35 that would be lovely 18:48:37 The bookmarks, I mean, not the arm :) 18:48:44 aha yes 18:49:02 I'm assuming ARM isn't a real blocker 18:49:08 hm 18:49:09 i.e. if we can't fix it, we just won't ship it 18:49:19 We should be able to fix bookmarks for 12.0a4 18:49:32 For ARM I think we still need to sign it 18:49:49 Is ARM enabled in main now? 18:49:50 yeah, let me see if I can just manually sign a testbuild for you donuts 18:49:56 richard: okaydokes, ty 18:49:57 PieroV: yeah I think so 18:50:08 Very interesting 18:50:10 i'm also getting general-lack-of-alpha nervousness about this one too 18:50:30 hello i'm donuts and my job is to be nervous 18:50:40 hey that's MY job 18:50:46 hey that's my job 18:50:59 lmao 18:51:13 can mine be yoloing? :D 18:51:40 yeah wfm 18:52:14 👉🤠👉 18:52:19 confiremd we have a torbrowser-alpha-osx-aarch64 make target in origin/main 18:52:20 ^ pierov firing off the patches 18:52:28 lol 18:52:36 richard: but is it enabled? 18:52:46 Like, is make torbrowser-alpha going to build it? 18:53:03 only one way to find out 18:53:18 (prety sure it does) 18:53:32 we'll see :) 18:54:54 i've added a fourth action item to my list 18:54:59 "Retest ARM build on M1 mac after @richard gets me a signed build" 18:55:13 and with that, I'm gonna put the bot back to sleep 18:55:17 since it's now HH:56 18:55:18 and i've updated my todo list on the pad 18:55:22 cool 18:55:23 awesome 18:55:28 ok l8r sk8rs 18:55:33 Thank you all! 18:55:38 tyvm all! 18:55:46 another fine release meeting was had 18:55:52 #endmeeting