18:58:35 #startmeeting Tor Browser meeting 22 March 2021 18:58:35 Meeting started Mon Mar 22 18:58:35 2021 UTC. The chair is sysrqb. Information about MeetBot at http://wiki.debian.org/MeetBot. 18:58:35 Useful Commands: #action #agreed #help #info #idea #link #topic. 18:58:59 Hello! 18:59:15 hi! 18:59:47 o/ 19:00:35 Pad: https://pad.riseup.net/p/tor-tbb-keep 19:01:01 o/ 19:01:09 hello hello! 19:04:02 Alright 19:04:39 hi 19:04:48 pospeselr: you can delete/overwrite your old statuses, if you want 19:05:30 got it 19:06:03 (woo. Google Play finally approved 10.5a12.) 19:06:55 This is your weekly reminder to update your Gitlab Boards, if needed 19:08:14 tor-browser-build#40252 19:09:09 GeKo: do you have an opinion on landing this? 19:09:19 i was a little confused by your comment 19:10:49 i think this is okay for now 19:11:01 okay, that was my feeling, too 19:11:10 we have a proper 11.0.1 project for clang-source on master 19:11:18 and i think it would be smarter to use that 19:11:25 which is what my comment aimed at 19:11:56 but we don't get rid of drawbacks until windows switches over to rapid release 19:12:12 as rapid release will be moving to clang 12 soon i think 19:12:30 is that the same as tor-browser-build#40048 ? 19:13:01 yes, if you look at the commit message of !217 it solves this for linux 19:13:15 ok 19:13:19 and then windows and osx would remain for #40048 19:13:28 it's a piece-by-piece business 19:13:39 or it would be it ideally 19:13:46 but we have not started with pieces yet 19:15:02 right. 19:15:46 okay, then i'll prep 10.5a13 and land the boklm's patch for tor-browser-build#40252 19:16:48 related to that, i'm think we should build desktop platforms for 10.5a13 tomorrow, and then build Android stable and alpha as -build2's at the end of this week 19:17:23 does that seem unreasonable? 19:18:53 do we plan release them at the same time? 19:19:24 or do we release the desktop 10.5a13 before the android one? 19:20:40 boklm: release desktop before Android, and update the blog posts when Android is published 19:21:01 ok 19:21:07 wfm 19:21:20 wfm too 19:21:58 okay 19:22:57 Next, should we adjust our meeting time after next week's time change? 19:23:14 And, going one step further, considering more people are in Europe than anywhere else 19:23:22 1800utc would work well for me then 19:23:25 would an earlier meeting time be preferred? 19:23:38 heh, indeed 19:23:47 finally, the majority :) 19:23:56 heh 19:24:07 * Jeremy_Rand_Talos has a mild preference for later in the day, but my preference is of minimal relevance 19:24:12 hah 19:24:16 earlier is always better for me 19:24:21 but 19:24:50 I def appreciate all the europeans being available at unreasonable hours back when i was west coast 19:24:57 yw 19:24:58 not sure wth y'all were thinkin 19:25:29 ha 19:26:26 GeKo: were you adding something after "but"? 19:27:16 earlier is better for me too (but 1800utc would still be ok) 19:27:32 i don't care one way or the other 19:30:39 okay, does 1500 UTC (1100 ET) work for most people? 19:30:54 +1 19:30:59 wfm 19:31:02 I think the net team is remaining at 1700 UTC 19:31:09 (wfm too!) 19:31:16 so this should give GeKo some time between meetings, at least : 19:31:23 :) 19:31:39 * Jeremy_Rand_Talos slightly dislikes it but will be able to cope, so +1 if it's better for the Europeans 19:31:40 just a "but" :) 19:31:53 ah ha :) 19:32:11 i only have the net team meeting i have to attend 19:32:24 otherwise i can meet essentially whenever 19:32:57 okay, let's try 1500 UTC beginning next week and we'll see how well that works 19:33:22 (i am a bit distracted due to real life fun, sorry) 19:33:47 (no worries) 19:34:05 Next, #17400 19:34:21 tor-browser#17400 19:34:21 in which components is this ticket? 19:34:31 ok :) 19:35:00 i'd like us to start looking at this ticket again 19:35:21 i had it in the bavck of my mind for a while 19:36:19 but the more I thought about the burden of our release process, the more I think creating multi-lingual packages is a good idea 19:36:45 reducing the number of separate bundles sounds like a good idea 19:37:44 i don't know if we should go as far as creating one package per OS, and put all locales into a single package 19:38:11 and I don't yet know what the update process looks like for going from single-locale to multi-locale 19:38:51 but I know the current release process is painful (for me), and I'd like to improve it 19:39:31 so this is more of an FYI, but I want to hear other opinions now (and later) if you have them 19:41:03 keeping separate bundles for the 5 or 10 most used locales, and one containing all the other less used locales sounds like a good idea to me 19:42:06 yeah 19:42:54 okay, and finally, someone added a comment about the banner 19:42:57 was that dun ? 19:43:03 yes! 19:43:03 dunqan 19:43:12 not sure if I'm being daft 19:43:14 yes, indeed, it is still there 19:43:29 nope, that is a problem 19:43:36 i just checked, as well 19:43:43 ha ok 19:44:01 i'll look into it and then we'll re-build it 19:44:12 thanks very much, appreciate it! 19:44:39 boklm: expect a 10.0.14-build2 tag in the morning :/ 19:44:51 ok 19:44:56 thanks 19:45:46 alright, that's everything for today's meeting 19:45:52 thanks everyone! 19:45:54 have a good week 19:45:57 #endmeeting