18:01:29 #startmeeting Tor Browser Release Meeting 2022-08-29 18:01:29 Meeting started Mon Aug 29 18:01:29 2022 UTC. The chair is donuts. Information about MeetBot at http://wiki.debian.org/MeetBot. 18:01:29 Useful Commands: #action #agreed #help #info #idea #link #topic. 18:01:36 pad is here: https://pad.riseup.net/p/tor-browser-release-meeting-keep 18:01:52 gonna brb one sec, feel free to fill it out :D 18:02:03 already doing :) 18:04:58 okay back 18:05:02 * donuts checks the pad... 18:05:43 wow that's a lot of releases 18:05:56 it's FINE 18:06:11 lol 18:06:14 why do both 11.5.2 and 11.5.3 include android? 18:06:19 just curious 18:06:41 11.5.3 fixes NoScript 18:06:46 bad planning on my part mostly 18:06:50 ah okay 18:06:55 I proposed to say 11.5.2 is desktop only 18:06:59 Even though we built also Android 18:07:15 (fwiw I built 11.5.3 also for desktop because I used the wrong make target) 18:07:17 riiight 18:07:36 i had anticipated publishing saturday AM but then the web server said no 18:07:49 computers 18:07:49 so here we are 18:07:59 i'm hoping there's an email in my queue telling me it's all fixed :p 18:08:16 lavamind came to #tor-browser-dev to say something about it 18:08:21 You could ping him directly 18:08:25 will do 18:08:34 did you run out of giga bits again? 18:08:49 yep 18:08:53 sad noises 18:09:05 lavamind | web-fsn-01 and 02 are borked, zero free space 18:09:42 lavamind | was there a TB upload recently ? 18:09:46 I wonder why he asked :) 18:09:52 lol 18:10:06 well, hopefully multi-locale pack will solve 18:10:19 🤞 18:10:52 okay i think the first agenda item is yours richard 18:10:57 "Remaining todo for esr102" 18:11:48 oh right 18:12:05 was just enumerating things left to do 18:12:20 it looks like we're all good though pending build review 18:12:26 tor-browser-build review* 18:13:19 great, doesn't look like too much? 18:13:32 seems that way :) 18:13:47 :) 18:13:57 pierov: Plans for Android 11.5 based on 102? 18:13:58 ? 18:14:07 we have plans for an 11.5 based on 102? 18:14:13 I certainly hope so 18:14:33 Backporting CVEs to 99 doesn't make sense, imho 18:14:58 i meant backporting 103 and 104 CVEs to esr-102 18:15:03 I know 18:15:13 But we also have a 11.5 :) 18:15:22 oh sorry I skipped over the _Android_ portion 18:15:30 hm 18:16:03 well if we had a properly maintained android stable i'd say no we should wait until all the esr102 stuff is done and do a simulatenous android+desktop esr102 release 18:16:24 but we don't really so upgrading 11.5 to 102 early may be a good idea 18:16:36 in which case we'd be doing that in the end of Sept release 18:16:45 11.5.4 18:16:45 The rebase has been a thing for more than a month, but only in nightly 18:16:53 So it hasn't been tested so much 18:17:12 But hopefully 20 days-one month should be enough, unless we get bad feedbacks 18:17:55 Soft freeze is Sep 15. I guess we'll be a little late for next stables. Maybe we should tell Tails 18:19:29 hm 18:19:44 Tails only cares about stable right? 18:19:49 Yes 18:20:31 oh i see the whole meeting thing 18:21:47 Yep, probably the rebase is feasible, but I will be able to build starting from Sep 17 18:22:14 well fwiw we won't be doing a rebase for 11.5.4 18:22:16 only backports 18:22:19 since no more esr91 series 18:22:37 Oh, right, I totally forgot 18:22:43 so it should be an 'easy' release 18:24:51 to the next point 18:25:06 merged geckoview/desktop for esr102 12.0a3 seems like a good plan to me 18:25:48 12.0 is currently scheduled for Nov 22nd 18:26:18 sounds good 18:26:36 So 102.5 18:26:52 Sep 15 is 102.3 18:27:04 So 2 more releases for 11.5? 18:27:24 yeah 18:27:47 wuft that many huh 18:28:08 i'm sure it will be fine 18:28:22 question: if we have branding things as part of S131 that also affect Tor Browser, will those all be 12.5? 18:28:31 i mean seriously though, that's two months after 12.0a3 to find and fix bugs :D 18:29:14 hmm 18:29:28 or is it a case of "depends how big they are" 18:30:18 so any branding type of commits which would affect both would be something affecting the common features 18:30:19 so like 18:30:25 new identity and security level 18:30:34 anything s131 speicfic would go in its own privacy-browser branch 18:30:56 Are we moving the crypto thing to base browser? 18:31:15 the non-secure crypot address copy detection thing? 18:31:21 We kept in the Tor Browser part of the patchset because of the dependency on TorStrings 18:31:23 Yes 18:31:45 yeah that should be moved to base-browser I think 18:32:26 yep, I'm mostly thinking about potential changes to about:tor and the onboarding templates, or the about:preferences#privacy UI changes 18:32:32 okay. We could do that when moving to fluent 18:33:27 makes sense 18:34:42 changes to about:tor and the onboarding templates --> S131 specific, I'd say 18:34:58 about:preferences#privacy UI changes --> common. donuts: did you have any in mind? 18:35:30 pierov: well regarding the first point, I think we should take the opportunity to modernize TB's templates for both 18:35:37 so there would be common templating changes 18:35:47 and then the privacy browser specific content/theming later 18:36:17 regarding about:preferences#privacy, not really anything specific beyond what we talked about at the last S131 catch up 18:36:18 Actually about:tor has some stuff related to getting little-t-tor updates 18:36:34 on a related note, do you think we have the UX resources for updating/modernizing the new user onboarding UX? 18:37:14 So the template would be only for the HTML and maybe something on the CSS. So I'm wondering if it makes sense to DRY them, and make everything more difficult to share the files 18:37:17 with the assumption henry would be available for implementation 18:38:12 richard: I think we do, it's not a very design-heavy activity tbh 18:38:49 pierov: wdym? 18:39:13 donuts: I don't think sharing the same files makes much sense from a technical point of view 18:39:25 We could copy and paste, rather than having shared files with different strings 18:40:11 So, they're changes we could do at the same time, but not-so-common 18:40:20 pierov: oh right, sure – whatever you think makes sense. I just don't really want to maintain two different "UX"es and potential sets of bugs, if that makes sense. 18:40:42 Sure 18:41:04 In my head the ideal scenario would be for both browsers to have their own content, branding and colors or w/e, but otherwise the onboarding and start screens would be functionally the same 18:41:19 hmm 18:41:51 i feel like that is going to get tricky 18:42:06 given the additional features tor-browser has to onboarder users 18:42:23 and things like the year-end campaign and other differences 18:42:46 but we may be able to smart here with regards to common functionality 18:43:19 i'm really just thinking about the really basic stuff, like the layouts etc. 18:43:25 general interactions 18:43:34 and what happens when the browser's been updated 18:44:31 the magic feature tour stuff in TB doesn't affect the functionality of the preceding slide templates at all 18:44:45 from a UX/Design pov i mean 18:44:59 right right 18:45:49 this could all just be copy pasting though, it doesn't need to be smart 18:45:56 whatever you think works best from a dev pov 18:47:04 yeah makes sense 18:47:49 we might need to let this stuff bake in TB alpha for a few releases though 18:47:53 because bugz 18:48:01 yeah for sure 18:48:10 so I'm not sure if it makes sense to try and squeeze it into 12.0? 18:48:20 or I can prioritize it in time for the next alpha? 18:49:33 i think squeezing much into the next alpha is not going to happen 18:50:44 well it may happen in 12.0a3 (end of Sept) but we may need to test in nightlies after that release 18:50:54 that's what I meant, sorry 18:51:19 but if we miss 12.0a3 (which is very likely, because work needs to happen) that leaves two alphas left? 18:51:50 which is why I'm starting to lean towards "maybe this is a 12.5 thing"? 18:51:50 there would be 1 after 12.0a3 (end of october) 18:51:55 oh just one 18:52:08 oh god it's nearly September already 18:52:11 I KNOW 18:52:30 so the first beta for privacy browser is scheduled for end of march 18:52:33 okay so definitely no about:tor, onboarding or privacy settings changes in 12.0 18:52:39 which is when that all needs to *really* be in 18:52:54 but we can start dropping them in 12.5aX 18:52:56 yeah 18:53:00 right 18:53:19 cool no prob 18:53:37 sorry for derailing the meeting 18:53:46 :D 18:54:05 we should launch 12.5 earlier next year though lol 18:54:14 6 month cycles would be nice 18:54:17 if there's antyhing on fire we can meet on the 5th, otherwise 19th work for y'all? 18:54:24 donuts: yeah agreed 18:54:31 sgtm! 18:54:32 Let's hope next year isn't like this one :P 18:54:40 evergreen hope lol pierov 18:54:41 next year should be a bit more chill 18:54:54 wfm re: dates 18:54:58 more devs = fewer problems??? 18:55:09 just different problems :p 18:55:17 After a certain threshold it isn't true 18:55:21 Especially if you're late 18:55:26 Don't ask me the name of this law, though 18:55:40 But I think we were below this threshold 18:57:36 yeah I don't think we're close haha 18:57:48 I think we're all good here? shall i close the meeting? 18:57:49 Found it: Brooks’s Law 18:57:54 yes, good for me! 18:57:56 let's get out of here 18:57:56 ! 18:58:05 perfect timing pierov xD 18:58:08 #endmeeting