17:59:41 #startmeeting Tor Browser meeting 5 October 2020 17:59:41 Meeting started Mon Oct 5 17:59:41 2020 UTC. The chair is sysrqb. Information about MeetBot at http://wiki.debian.org/MeetBot. 17:59:41 Useful Commands: #action #agreed #help #info #idea #link #topic. 18:00:13 Hello! 18:00:28 Pad: https://pad.riseup.net/p/tor-tbb-2020-keep 18:00:46 o/ 18:01:38 o/ 18:07:03 o/ 18:09:58 hi 18:11:10 okay, let's see where we are 18:11:21 * antonela goes for the mate 18:11:28 I added some announcements based on a timeline GeKo, acat, and I discussed earlier today 18:12:11 mikeperry: did you make any more progress on the code audit script? 18:12:45 * sysrqb has some mate, too 18:12:51 "October Schedule" section of pad seems off; the 14th is a Wednesday 18:13:00 mmm 18:13:18 * gaba goes to look at the calendar 18:13:41 thanks :) 18:17:25 "TB Release meetings" section also looks off; October 15 is a Thursday 18:17:28 * sysrqb add review fenix#34179 onto this week's list 18:19:29 ahf: i forgot to ask during the retro 18:19:41 are you concentrating on tor now? :) 18:20:00 same for mikeperry ^ 18:20:11 yeah, i am on s30 right now 18:20:29 okay 18:21:31 sysrqb: hey sorry distracted. here now 18:21:43 if there are things around testing of upgrade paths that comes in the next few days before the release i can easily do that though 18:21:53 so the donation script went from somethign that I thought would be nicely supported by git to basically a minor outline of the existing workflow :/ 18:22:07 make a diff, save it, grep it.. the output will kinda look like shit 18:22:11 I have not finished it 18:22:48 okay 18:22:52 ahf: ack, thanks 18:22:54 sysrqb: what is the timeline for needing it for rapid release? 18:23:05 "now" :) 18:23:11 oh boy 18:23:12 we have https://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/40130 on our plate 18:23:21 we're going from 81 to 82? 18:23:22 ok 18:23:27 i mean, we can continue with the manual audit 18:23:38 but having something a little more automated woulld be nice 18:23:49 I can finish my hax and see how they look... but it's gonna be a bit ugly 18:23:49 but if that's not ready then we'll do what we can 18:24:08 having the ff82 tag will help 18:24:13 can I use ff82 now or just beta? 18:24:46 acat: rebased our patches onto 82b 18:25:00 we only have beta for another couple weeks 18:25:01 7 18:25:12 *82b7 18:25:34 i don't have much to discuss in today's meeting 18:25:50 so i was thinking we could distribute/assign tasks for tihs transition 18:26:10 if someone else has a topic we should discuss, plesase make say it 18:26:17 *please 18:29:10 sysrqb, safe to assume that no Browser Team attention will be available for Namecoin things until after October 20? 18:29:36 acat: do you want to pick up #40134 and #40131 18:29:46 or #40132? 18:29:54 ah, right :) 18:30:09 tor-browser#40134 tor-browser#40131 18:30:12 sure 18:30:17 or tor-browser#40132? 18:30:57 Jeremy_Rand_Talos: yeah :/ that's a safe assumption 18:31:12 we may have some time beginning next week 18:31:23 or I don't want to promise that 18:31:31 sorry for all of the delay 18:31:42 i know you've worked hard on this 18:32:03 s/or/but/ 18:32:17 sysrqb: acat: i think a good idea for our rewview process is that folks doing the closed bugs review are keeping an eye on all patches landing on mozilla-beta, too 18:32:44 sysrqb, ok, no worries. Got plenty of other things I can spend dev time on in the interim, and I think I've managed to keep Namecoin community expectations damped down enough that the delay won't bother anyone 18:33:03 GeKo: keep an eye on patches until it merges into release? 18:33:10 so we don't miss new uplifts? 18:33:13 yes 18:33:23 yeah, that makes sens 18:33:31 that's what i did for mozilla81 18:33:47 and it felt kind of "natural" for have mozilla-beta on the radar, too 18:33:53 while looking over all the closed bugs 18:33:59 that sounds good 18:34:11 s/for have/to have/ 18:34:25 ack 18:35:22 sysrqb: so, should i do tor-browser#40131, tor-browser#40132, tor-browser#40134? 18:36:17 i was thinking you could take either reviewing developer notes and closed bugs 18:36:32 or going through the proxy bypass audit 18:37:04 and tor-browser#40132 and fenix#40049 should (maybe) go together 18:37:04 ok, i can take tor-browser#40131 and tor-browser#40134 this time 18:37:20 thanks 18:37:41 so i can take the proxy bypass audit for 82 18:37:56 and try understanding what mike has created 18:38:26 acat: do you want to take tor-browser-bundle-testsuite#40008 too? 18:39:01 that may be easiest for you right now 18:39:12 but i don't want to overload you, 18:39:52 yeah, i guess i should get the tor-browser-bundle-testsuite!1 mr finished first 18:40:03 haven't prioritized that much 18:40:34 yeah, difficult to prioritize that right now 18:40:49 i'm okay with delaying tor-browser-bundle-testsuite#40008 until next week 18:41:02 i'll try if there's time 18:41:02 but if you can try running the tests on 82, at least 18:41:07 yup 18:41:16 maybe that will give us some infom about new breakage 18:41:19 *info 18:41:58 yeah 18:42:07 okay, i'll pick up fenix#40050, too 18:43:20 i think that's all of the mozilla82 tickets 18:43:33 i was not sure whether we need more 18:43:42 so, if there things missing, please add them 18:43:52 *there are 18:44:22 anyone have questions or concerns about the proposed relesae schedule described in the announcement sections of the pad? 18:45:47 yeah, we'll learn which pieces are missing, that is a good starting place 18:47:15 * sysrqb hears nothing 18:47:40 thanks everyone, i'll close this meeting 18:47:53 Thanks! 18:47:59 #endmeeting