14:02:22 #startmeeting Pulp Triage 2021-03-23 go/no-go 3.12 release 14:02:22 !start go/no-go 3.12 release 14:02:22 #info ipanova has joined triage 14:02:22 Meeting started Tue Mar 23 14:02:22 2021 UTC. The chair is ipanova. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:02:22 Useful Commands: #action #agreed #help #info #idea #link #topic. 14:02:22 The meeting name has been set to 'pulp_triage_2021-03-23_go/no-go_3.12_release' 14:02:22 ipanova: ipanova has joined triage 14:03:45 #info ttereshc has joined triage 14:03:45 !here 14:03:45 ttereshc: ttereshc has joined triage 14:03:50 the milestone is https://pulp.plan.io/versions/182 14:04:24 #info ggainey has joined triage 14:04:24 !here 14:04:24 ggainey: ggainey has joined triage 14:05:00 we can take this off 3.12 https://pulp.plan.io/issues/8048 14:05:38 this one we can keep for 3.12 but not treat as blocker https://pulp.plan.io/issues/7316 14:05:41 thoughts? :0 14:05:42 #info mikedep333 has joined triage 14:05:42 !here 14:05:42 mikedep333: mikedep333 has joined triage 14:06:55 people, talk to me :) 14:07:01 +1 14:07:03 for both 14:07:05 ipanova: sorry, I'm trying to read the issues ;) 14:07:14 #info bmbouter has joined triage 14:07:14 !here 14:07:14 bmbouter: bmbouter has joined triage 14:07:40 fwiw, I'm looking at the query here https://pulp.plan.io/projects/pulp/issues?query_id=173 14:07:42 um, ok - 8048 has a PR but there's a problem with it, is that why we want to move it off of 3.12? 14:07:53 it's harder to see statuses on the milestone view 14:08:07 yeah same 14:08:17 yup 14:08:33 so we need to obviously get through this work, but in terms of having the right list, I think this is the right list 14:08:36 ttereshc: you can just then click on the milestone issues :) 14:08:39 except 8048 can come off 3.12 14:08:54 ggainey, yes, there is a problem that we are trying to understand why the objects can't be represented 14:08:56 ggainey: what's the deal with this issue https://pulp.plan.io/issues/7904 ? 14:09:03 checking 14:09:45 ipanova: I don't have an answer yet, but it's entirely reproduceable. I'm planning on picking that up since I've bee inside the importer-code most recently 14:09:58 ggainey: ack 14:10:18 as a side note rhui has confirmed we can deliver this release after Esater 14:10:30 import does repos in parallel, I'm guessing its an artifact of appstream depending on base causing an unexpected reserved-resource problem 14:10:34 kk 14:10:37 should we decide to release on April 6 instead of March 30th 14:10:54 anyway, RE 8048 and 7316, I'm ok w/the suggestions 14:11:06 30MAR seems pretty risky 14:11:13 April timeline looks more viable to me 14:11:23 mikedep333: any installer insights/problems? 14:12:00 ggainey: to be honest if we release march 30, who's gonna use it anyway people will be on holiday 14:12:13 heh also true 14:12:37 ipanova: no 14:12:43 sweet 14:12:57 so given all this work on our list, are we go April 6th? 14:13:30 that would be suggestion, aye 14:14:09 I'm ok w/ either of these 14:14:34 my last working day to contribute is Apr 1 and I plan to be done with my items for 3.12 by then (and merged) 14:15:12 so it seems it will give you couple more days if we release in April 14:15:17 I think we should go ahead and move 7316 off 3.12 so we can focus on the things we need to get done for 3.12 14:15:18 sweet 14:15:27 ttereshc: yeah I was planning to be done earlier but yeah 14:15:34 bmbouter: concur RE 7316 14:15:37 having more time is ok with me tho! 14:15:43 ;) 14:16:47 ok i can take 7316 off 14:17:06 well, i moved it to 3.13 14:17:10 +1 14:17:15 ty 14:18:10 i am bout to declare this meeting adjourned, last call? 14:18:17 +1 14:19:08 #endmeeting 14:19:08 !end