16:58:43 #startmeeting Network team meeting 11 january 2020 16:58:43 Meeting started Mon Jan 11 16:58:43 2021 UTC. The chair is ahf. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:58:43 Useful Commands: #action #agreed #help #info #idea #link #topic. 16:58:49 hello hello all 16:58:56 new pad is at https://pad.riseup.net/p/tor-netteam-2021.1-keep 16:59:21 o/ 16:59:23 short announcement: next arti hackathon will be the 21st of January at 13:00 UTC 16:59:37 we have a few more people joining, so that is gonna be interesting! 16:59:44 love it 16:59:46 looking forward 17:00:08 Oh, also next monday is MLK day, which is a US holiday 17:00:32 I'm not planning to work then, but I don't have anywhere to go, so I'll be glad to stop by for a meeting if people have one 17:00:34 ah, that is good to know, so you will be out that day and mike i guess 17:00:46 or we can resched for tues 17:00:46 nah, let's take the things on our thursday sync if there is anything then? 17:00:52 or we can do our meeting tuesday 17:01:01 the thursday sync is replaced by the arti hackathon I think? 17:01:16 no, actually, i can't do tuesday next week because that is where i have my long peer code session with maria 17:01:42 ah ok 17:01:43 yeah, let's just skip next week then? 17:01:48 o\ 17:01:51 s/peer/pair/ 17:02:41 ok! 17:02:45 how are folks doing with their boards? 17:03:01 i know we just started so maybe people are still syncing up 17:03:01 well been first day back so I will say "stable" :) 17:03:08 yeah, that is my state too 17:03:10 but it looks correct 17:03:42 I'm a little lost about 0.4.5, but my board is fine. 17:03:56 lost in what ways? 17:04:06 we can talk about it when we get there :) 17:04:09 ack 17:04:24 okay, so we have reviewer assignments 17:04:45 asn, and dgoulet: our gitlab got upgraded over the holidays, so we now have a "Reviewer" field 17:04:50 wow 17:04:54 so you can have both an assignee and a reviewer on MR's 17:04:55 im not ready for this 17:04:58 interesting 17:05:08 oh really! 17:05:16 so i guess they have an official workflow now 17:05:17 unfortunately, geko found out that tickets where you are reviewer on does not show up in your MR's list on Gitlab 17:05:28 but it means we no longer have to move things back and forward 17:05:38 you can now do queries such as Reviewer = @ahf 17:06:00 so, when you delegate, if you use that, i will update our queries in the pad to use Reviewer=@person queries instead 17:06:58 we can talk about this when you start delegating and i can clean up the pda 17:06:58 ok! 17:07:08 sounds okay to me. I'll miss the stuff appearing on the MR list, but it won't take long to make a new link 17:07:13 okay, 0.4.5 is next 17:07:23 nickm: yeah, i am gonna open a ticket with upstream if one could toggle that somehow 17:07:48 it's odd because the submitter is not the assignee by default, so i am not sure what the difference is with having both assignee and reviewer 17:09:10 ok 17:09:14 0.4.5 17:09:21 nickm: you were lost? 17:10:03 yeah, I see a bunch of 045 tickets and I don't know if i'm supposed to be making prpogress on any... there is a pretty big backlog there. 17:10:24 right now we have 18 oppen issues in 045-stable, right? 17:10:41 yes, that is what i count too 17:10:59 16 without backports 17:11:31 Let's say we need to get these all fixed in a final rc that comes out... hm, when? 17:11:48 * ahf moves tor#40048 out of 0.4.5 17:12:16 The rc probably has to come out in the first week of February, so that TB can pick it up for 10.5a11 17:12:35 so that means we need all this stuff fixed by around the end of the month. 17:12:40 (or otherwise addressed) 17:12:42 can we do that? 17:13:17 i have two that i think i can solve and 1 mystery that i havent been able to reproduce 17:13:20 i think that is possible 17:13:30 yeah we can pull it off I think, 17:13:44 and we must get the v3 fixes in 045 and likely stables (unclear at this moment) 17:14:12 ya 17:15:14 ok 17:15:22 I have comparatively little stuff in 045 at the moment... 17:15:29 so if anybody needs to offload, I'm here 17:15:42 my only request is that we should not wait till its too late 17:16:15 asn: is your 045 stuff under control? 17:16:17 ya, i can prioritize my stuff this week easily 17:16:54 045 blitz time indeed 17:17:08 ya, if we blitz it this week we should be good. that is a good idea 17:17:21 nickm: yes i think so 17:17:22 ok! 17:17:27 but im also kinda catching up to it 17:17:35 but i think it should be ok 17:18:10 this is slightly related to our releases page on gitlab: https://gitlab.torproject.org/tpo/core/team/-/wikis/NetworkTeam/CoreTorReleases 17:18:14 is that looking OK? 17:18:39 I think so 17:18:57 ok 17:19:24 we have 15 tickets in the backport category: https://gitlab.torproject.org/tpo/core/tor/-/issues?scope=all&utf8=%E2%9C%93&state=opened&label_name[]=Backport 17:19:28 Would it make sense for us to add an "anticipated release date" list, like TB has at https://gitlab.torproject.org/tpo/applications/tor-browser/-/wikis/Release-Schedule 17:19:32 maybe we should ignore that for now given the 0.4.5 part is coming up? 17:19:40 * ahf looks 17:20:03 like, "let's try to do this release around this date"? 17:20:14 yeah that is how I interpret somehow our release dates lol 17:20:22 just for the public, non-fixed is ... a bit harsher 17:20:39 i am not sure i understand - so we change it from our "strict" date to a more fluid thing? 17:20:51 err, I was thinking that we would say something like 17:21:28 "aim for 0.4.5.3-rc around 30 Jan; aim for 0.4.5.4-stable around 15 Feb" 17:22:00 ah for all minor versions? 17:22:12 ohh, hmmm, i think we can do that, but i am unsure if people care much for the rc's for specific future dates? 17:22:12 or "aim for 0.4.5.3-rc around 15 Jan; 0.4.5.4-rc around 30 Jan, 0.4.5.5-stable around 15 feb" 17:22:19 I think it's for our own planning 17:22:26 we can do that 17:22:27 so we can see how it syncs up with our schedule and with TB 17:22:34 yeah 17:22:38 ok. I'll try adding it in for 045 and see what we think 17:22:45 sounds good! 17:23:13 were people OK with ignoring the backports list at least for now while we have 0.4.5 coming up? 17:24:05 fine by me but my I do think a series of stable "soon" might be good especially considering the potential v3 fix backported 17:24:58 ack 17:25:27 dgoulet: yes 17:25:37 dgoulet: maybe we should put our heads together next week on that when the 0.4.5 blitz is over 17:25:42 and maybe crunch through the backports list 17:25:56 sure sounds good strategy to me 17:26:27 should you and i try to do that? you are here on monday, no? 17:26:32 it's a US specific holiday 17:26:59 I'm there yes 17:27:01 US specific one 17:27:29 oki, let's do a sync on that on monday then! and see if we can create a lot of prep branches for it and then nickm can check in on it afterwards 17:27:30 cool 17:27:32 are we okay with this plan: https://gitlab.torproject.org/tpo/core/team/-/wikis/NetworkTeam/CoreTorReleases#upcoming-release-dates ? 17:27:43 I'vee chosen Jan 13 and Jan 25 because they are a little before TB alpha dates 17:28:07 tbb-team -- do those dates respectively give you enough time to get a release candidate into the alpha coming out on the upcoming day? 17:28:16 *I've 17:28:54 it looks nice, nickm 17:29:09 * sysrqb looks 17:31:16 nickm: that schedule looks reasonable 17:31:50 ok. So an rc on the 25th gives you enough time to put it in the alpha that you're doing on the 26th? 17:32:59 i see. probably not, i was thinking that would go into the alpha version on 2021-02-05 17:33:23 ok, so how much lead time do you need between our release and yours? 17:33:24 we start building a3-4 days before the release date 17:33:32 3-4 days 17:33:58 working days or calendar days? 17:34:32 * nickm adjusts the page 17:34:34 for an alpha, roughly calendar days 17:34:45 ok. i've edited the page. does it look workable for you now? 17:35:05 we usually begin building stable on Wednesday, when the release is scheduled on the following tuesday 17:35:39 we can work with 22nd 17:36:12 thanks 17:36:14 cool 17:36:27 man i have lost my tabs 17:36:47 ok! we hvae no new "team" tickets 17:37:08 sysrqb: thanks to you; and looking forward to an era of actually planning our stuff on the network team :) 17:37:16 we got tor#40228 from the anti-censorship team 17:37:37 it's under s30, but there is a workaround iirc 17:37:43 ya 17:37:45 so not urgent 17:37:56 sysrqb: (this means fwiw that there is a tor rc coming out tomorrow, so please try to get it in your next alpha?) 17:38:10 sysrqb: (if we miss one of your alphas it disrupts our testing) 17:38:36 ok, we have the usual reminders, nothing new there. we talked about the new "Reviewer" field that we all have to get used to on gitlab 17:38:55 i see nothing in bold. anything we need to discuss that we have missed/forgotten? 17:39:39 nickm: understood, that sounds good. 17:39:59 ahf: not from me :) 17:40:08 * dgoulet is good 17:40:35 okay! good to be back with everybody, looking forward to get 2021 started with tor things <3 17:40:39 let's chat in the other channels 17:40:43 #endmeeting