15:03:19 #startmeeting Pulp Triage 2021-03-02 go/no-go for 3.11.0 release 15:03:19 #info ipanova has joined triage 15:03:19 !start go/no-go for 3.11.0 release 15:03:19 Meeting started Tue Mar 2 15:03:19 2021 UTC. The chair is ipanova. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:03:19 Useful Commands: #action #agreed #help #info #idea #link #topic. 15:03:19 The meeting name has been set to 'pulp_triage_2021-03-02_go/no-go_for_3.11.0_release' 15:03:19 ipanova: ipanova has joined triage 15:03:50 #info ggainey has joined triage 15:03:50 !here 15:03:50 ggainey: ggainey has joined triage 15:04:10 #info ttereshc has joined triage 15:04:10 !here 15:04:10 ttereshc: ttereshc has joined triage 15:04:13 #info x9c4 has joined triage 15:04:13 !here 15:04:13 x9c4: x9c4 has joined triage 15:04:21 https://pulp.plan.io/versions/174 we have 8 issues in new/assigned state. 15:04:27 #info daviddavis has joined triage 15:04:27 !here 15:04:27 daviddavis: daviddavis has joined triage 15:05:07 #info bmbouter has joined triage 15:05:07 !here 15:05:07 bmbouter: bmbouter has joined triage 15:05:10 I think we can remove this issue from 3.11? https://pulp.plan.io/issues/8204 15:05:43 I agree I'm not familiar with that one 15:05:45 sure, this does not look like a blocker 15:05:50 should i move it to 3.12? 15:06:06 def not a blocker for 3.11 - 3.12 sounds fine 15:06:10 +1 15:06:10 #info mikedep333 has joined triage 15:06:10 !here 15:06:10 mikedep333: mikedep333 has joined triage 15:06:17 ok 15:06:22 +1 15:06:29 ipanova: RE https://pulp.plan.io/issues/7915 - what actually wants to happen here? just the RemoteArtifacts check in settings.py? 15:06:55 yes I believe so 15:07:04 I added the remote artifact check in settings 15:07:10 so if that's it, we can close it out 15:07:12 yes I agree 15:07:16 dis is done 15:07:16 +1 15:07:20 * ggainey cheers wildly 15:07:21 yes 15:07:34 the under discussion part decided to be not implemented 15:07:39 aka the command to handle RA 15:07:44 so closed-complete? 15:07:47 daviddavis: ^? 15:08:04 +1 15:08:10 coolio 15:08:13 * ipanova closing 15:08:16 here's the RA command https://pulp.plan.io/issues/7986 15:08:26 I'd be willing to move 8231 to 3.12 15:08:29 RE https://pulp.plan.io/issues/8231 - is this a 3.11 blocker? 15:08:31 propose moving* 15:08:31 ha! 15:08:35 bmbouter: gmta :) 15:09:05 I was suggesting to take 8231, but i can do that still for 3.12 15:09:17 +1 to move to 3.12 15:09:25 +1 15:09:31 +1 15:09:49 who is clicking the buttons for these changes? 15:10:04 me 15:10:15 great 15:10:30 x9c4: if you wanted to take one, maybe take https://pulp.plan.io/issues/8167 ? 15:10:48 I have as assigned and some code already but it's not done and it's nothing you couldn't do readily anyway (I think) 15:11:03 just a thought, not really go-no go specific if we want to move on 15:11:22 bmbouter, let's talk about that later. 15:12:00 :) 15:12:21 sounds good 15:12:31 I wanted to check on the tech preview remaining items 15:13:15 we have left 3 FIPS stories in new/assigned state 15:13:20 in looking at these I think we did get acks from users/stakeholders on each of them so maybe we're good 15:14:03 I talked to partha a couple days ago about import-checks and he was a little unsure about removing tech preview from it 15:14:25 I'd suggest waiting one more release on removing tech preview from import/export 15:14:26 cool we can bump one more release then 15:14:29 +1 15:14:31 kk 15:14:35 daviddavis: ack 15:14:42 +1 15:15:06 I removed the tech preview label on correlation id after confirming with katello 15:15:16 great, that makes sense, ty 15:16:03 I thought 8258 was going to assigned by gerrod 15:16:16 but that was last thursday, I missed yesterday's fips checkin 15:17:57 can anyone from installer team speak up for this issue? mikedep333 fao89 ^ 15:18:40 which issue? 15:18:52 https://pulp.plan.io/issues/8258 15:18:53 he gave an update on it yesterday 15:19:02 maybe he forgot to assign it to himself 15:20:33 was this the issue mikedep333 passed to me? 15:20:48 having just updated two issues to assign them to myself, I def feel that pain 15:20:51 I think this was one gerrod was handling 15:21:51 I think it's safe to assume this is ASSIGNED 15:22:04 is it time to move into the go/no-go part? 15:22:39 +1 to move on 15:22:59 bmbouter: sure, what is the feeling of releasing 3.11 in a week? 15:23:27 so I think we need to actually timebox the 3.11 release probably 15:23:34 only one issue at new at this point 15:23:37 because we know 3.12 needs to come at the end of march 15:23:43 daviddavis: will there be anyone able to get to 'what-if scenario'? https://pulp.plan.io/issues/7986 15:24:09 I don't know. we can probably check at thursday's fips check in 15:24:27 daviddavis: sounds good 15:24:28 are we thinking about 7986 as an extension of handle-content-checksums? like a --dry-run option? 15:24:58 yea, it should also report what on-demand contnet will be impacted 15:25:12 kk, cool 15:25:15 I'll add a comment 15:25:55 ggainey: it should all be there 15:26:27 bmbouter: agreed to timebox the 3.11 release. let's checkin on friday? and keep the tentative release date march 9? 15:26:39 imo we should aim for march 9 and then fallback to march 11 15:26:42 +1 15:26:45 +1 15:26:46 yeah I think that'll work 15:26:57 +1 15:27:00 I believe our absolute last day would be the 16th 15:27:09 daviddavis: RE 7986 - I mean to call out specifically that it's an addition to handle-content-checksums, not a new command 15:27:12 concur 15:27:15 alright i will schedule a meeting on friday march 5 15:27:23 +1. also I want to point out that by the number's we're looking pretty good, but there are a few things unrepresented here 15:27:26 so far we are go for March 9 release 15:27:31 +1 15:27:40 +1 15:27:58 the worker timeout is in POST but it's got a varierty of unfinished work and it's not easy 15:28:24 also I think we need closure on the auto-distriute planning w/ dalley, daviddavis 15:28:27 are there any PRs the need to reviews? 15:28:32 bmbouter, I agree 15:28:47 to be reviewed * 15:29:44 bmbouter, personal opinion: I think we should move forwards w/ my plan, but I actually agree now that long-term, we should transition models. I don't think it's possible to do that in any kind of short timeframe 15:30:19 alright, we are out of time. the resolution is go for 3.11 march 9, i will schedule a checkin meeting march 5 15:30:22 #endmeeting 15:30:22 !end