16:05:40 #startmeeting Pulp Triage 2020-09-18 3.7.0 check-in meeting 16:05:40 #info dkliban has joined triage 16:05:40 !start 3.7.0 check-in meeting 16:05:40 Meeting started Fri Sep 18 16:05:40 2020 UTC. The chair is dkliban. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:05:40 Useful Commands: #action #agreed #help #info #idea #link #topic. 16:05:40 The meeting name has been set to 'pulp_triage_2020-09-18_3.7.0_check-in_meeting' 16:05:40 dkliban: dkliban has joined triage 16:05:50 #info daviddavis has joined triage 16:05:50 !here 16:05:50 daviddavis: daviddavis has joined triage 16:06:03 anyone got a link to the 3.7.0 milestone handy 16:06:15 #info ttereshc has joined triage 16:06:15 !here 16:06:16 ttereshc: ttereshc has joined triage 16:06:32 #info x9c4 has joined triage 16:06:32 !here 16:06:32 x9c4: x9c4 has joined triage 16:06:39 #info bmbouter has joined triage 16:06:39 !here 16:06:40 bmbouter: bmbouter has joined triage 16:07:12 ok so here's the current query: https://tinyurl.com/y6rqlufb 16:07:51 we have 2 items at POST, 3 at ASSIGNED, and 1 at NEW 16:08:14 the one at new we're discussing monday 16:08:15 the new one is for Monday 16:08:19 yup 16:08:23 cool 16:08:29 and it will be easy to PR it then (it'll be small) 16:08:31 7487 should have a pr opened today 16:08:48 7471 I'll have a PR opened today 16:09:01 7411? 16:09:18 * daviddavis eyes dkliban 16:09:38 yes 16:10:01 i will be out the rest of this afternoon but i plan on working on that issue on monday 16:10:29 we really need this for the dev cycle of 3.7 - 3.8 so it shouldn't formally block the release 16:10:32 aka I think that is a fine timeline 16:10:32 i expect to have a PR for the plugin template and pulp_file on Monday 16:10:46 sounds good to me 16:10:51 it's really designed to test the upcoming plugin releases against 3.8.0.dev 16:11:13 I'm fixing up 7413 now and will merge (with its lgtms on it) after my next push 16:11:18 cool 16:11:26 what about 6463 ? 16:11:37 based on lots of PR discussion I don't believe there will be a pulpcore PR for it 16:11:43 and the fix will occur in pulp_rpm only 16:11:48 dalley: ^ ? 16:11:48 ok 16:11:58 dalley: let us know if this is not the case 16:12:17 bmbouter, no, regardless of which strategy is used to fix it both PRs are necessar 16:12:37 actually it's the RPM PR that is necessary only because the code was duplicated both places 16:12:58 so no pulpcore pr then? 16:13:12 yes pulpcore PR :) 16:13:18 oh 16:13:34 what's the timeline. do you think you cna get it merged by monday? 16:13:40 or today? 16:13:52 today is what I was aiming for 16:14:23 I think if that and the other things discussed earlier to happen today happen, we'll be sitting pretty for the release on tuesday 16:14:59 should we remove 7411 from the 3.7.0 milestone? since it's not blocking 16:15:01 great 16:15:05 yea 16:15:08 * bmbouter does it now 16:15:27 done 16:15:34 also, if someone has time to review a docs PR, I have one I'd like to get in https://github.com/pulp/pulp_file/pull/428 16:15:55 yup can do 16:16:00 and anyone else too ^ 16:16:43 it's the one :) the one that caught bugs 16:17:18 truth but docs don't have to happen later 16:17:58 can we hear an all-around for go/no-go on the 22nd release? 16:18:14 I am a 'go' 16:18:17 go 16:18:19 go 16:18:30 go! 16:18:35 I'm go wtih a hoe that 3.8 can be planned better 16:18:39 *hope 16:19:14 Should we create a 3.8.0 milestone right away? 16:19:19 yes we should 16:19:22 yes 16:20:04 call me crazy but we've deliver huge features folks told us about at the last minute (fips and selinux) and even a few days ahead, I'm not sure what better looks like 16:20:46 I'm interested to hear what we want we didn't get in the 3.7 process 16:23:16 let's discuss next week 16:23:24 i don't have an answer for you 16:23:32 but i want to end this meeting 16:23:58 to hear folks aren't happy w/ the release I led but without details is a little unsettling 16:24:08 ttereshc: ^ 16:24:19 but yes let's end the go/no go part at least 16:24:34 I hear go's all around, I'll send out an update w/ that to pulp-dev on thread 16:24:37 #endmeeting 16:24:37 !end