15:30:15 #startmeeting Pulp Triage 2020-11-30 15:30:16 !start 15:30:16 Meeting started Mon Nov 30 15:30:15 2020 UTC. The chair is daviddavis. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:30:16 Useful Commands: #action #agreed #help #info #idea #link #topic. 15:30:16 The meeting name has been set to 'pulp_triage_2020-11-30' 15:30:16 #info daviddavis has joined triage 15:30:16 daviddavis: daviddavis has joined triage 15:30:39 3.9 issues https://pulp.plan.io/projects/pulp/issues?fixed_version_id=152&set_filter=1&status_id=o 15:30:47 #info bmbouter has joined triage 15:30:47 !here 15:30:47 bmbouter: bmbouter has joined triage 15:31:08 #info ipanova has joined triage 15:31:08 !here 15:31:08 ipanova: ipanova has joined triage 15:31:39 one issue is at NEW: https://pulp.plan.io/issues/6671 15:32:07 is someone able to work on this in the next couple days and if not, should it block 3.9? 15:32:10 #info mikedep333 has joined triage 15:32:10 !here 15:32:10 mikedep333: mikedep333 has joined triage 15:32:21 I think I'll be able to work on this 15:32:36 ok great 15:32:43 #info ttereshc has joined triage 15:32:43 !here 15:32:43 ttereshc: ttereshc has joined triage 15:32:57 looks like there are also a number of issues at POST 15:32:57 #info fao89 has joined triage 15:32:57 !here 15:32:57 fao89: fao89 has joined triage 15:33:09 5 issues 15:33:51 should we go through them? 15:34:35 yes please 15:34:43 https://pulp.plan.io/issues/7710 is being worked on by x9c4 but he's out until release day 15:34:50 #info ppicka has joined triage 15:34:50 !here 15:34:50 ppicka: ppicka has joined triage 15:34:56 we probably should find reviewers for all of them 15:35:21 i think this is redy for review, since it is not longer a draft 15:35:36 +! 15:35:37 +1 15:35:46 looks like bmbouter started to review it. bmbouter, can you re-review it? 15:35:51 yes I can 15:35:56 and I'll test it 15:36:12 I can be a second reviewer 15:36:33 great 15:36:41 next up is https://pulp.plan.io/issues/7696 (ggainey) 15:37:04 there is 1 approval and some requested changes form bmbouter 15:37:04 and ggainey is not in this channel 15:37:05 #info ggainey has joined triage 15:37:05 !here 15:37:05 ggainey: ggainey has joined triage 15:37:12 ah nm 15:37:14 I can't type 15:37:29 hello :) 15:37:40 ggainey: is this ready for re-review? https://github.com/pulp/pulpcore/pull/1027 15:38:32 daviddavis: looks like bmbouter answered my/your question(s) last week - I will make the required/requested changes and repush 15:38:38 (so, 'no', right this second) 15:38:52 ok great 15:38:57 ggainey: whenever it pushes feel free to ping and I can re-review lgtm 15:39:05 bmbouter++ 15:39:05 daviddavis: bmbouter's karma is now 310 15:39:06 bmbouter: will do, thanks 15:39:13 bmbouter++ 15:39:13 ggainey: bmbouter's karma is now 311 15:39:14 indeed 15:39:24 next up is https://pulp.plan.io/issues/7561 (ipanova) 15:39:48 this one is blocked https://github.com/pulp/pulpcore/pull/1008#issuecomment-733903624 15:39:57 oh shiz yeah I gotta look into that also 15:40:22 i poked around but did not find anything reasonable 15:40:53 this is on my today list, but with meetings my today list is probably 3 days long 15:41:07 still though this is very important and I hope to investigate today 15:41:33 bmbouter: and ipanova will followup on this the int following days 15:41:39 +1 15:41:48 I do believe this needs to be a blocker still 15:42:00 yeah 15:42:44 I agree we should get this into 3.9 15:43:11 I guess my question then is what is the 3.9 GA date atm and when is our next go/no-go checkin? 15:43:29 dec 7 is ga date 15:43:34 dec 7 is the ga date and our next go/no-go would be wed or thurs I think 15:43:39 so we can check back in then 15:43:42 great 15:43:47 +1 15:44:01 next issue is this https://pulp.plan.io/issues/6559 (me) 15:44:15 this is pretty much ready for review but I notice there's no changelog so I need to update that 15:44:25 I promised to review this one 15:44:32 will do but we needa asecond reviewer 15:44:33 +1 thank you. ggainey could you also review? 15:44:48 kk, will do 15:44:52 thank you 15:45:03 last is correlation id https://pulp.plan.io/issues/4689 15:45:17 this is ready for review 15:45:39 I'm tempted to hold it given that we're at the end of the release cycle and this affects many different parts of pulp 15:45:47 originally I wanted to get this into 3.9 15:45:49 thoughts? 15:46:01 I don't think this should block the release 15:46:09 but I don't have concerns about adding in features at the end 15:46:29 it's upstream releasing early finding a problem and fixing it in a later release is actually a positive outcome 15:46:43 I think it's smart to merge it right after release and use it for some time in our dev env if you are concerned that it might break things 15:47:14 I agree. normally I wouldn't mind merging features that are isolated but this seems higher risk. I don't have a strong opinion though. 15:47:55 my hope for upstream is that it strongly favors change 15:48:16 and that differentates against products which strongly favor stability 15:48:30 we can get it off the blocker list in the first place and see if we get to review it 15:48:53 removing the blocker status I think makes sense 15:49:12 I also want to favor change upstream but I don't want to do a disservice to our upstream users by merging risky features at the last minute 15:49:26 I'll remove it from the blocker list 15:49:55 ok, anything else issue wise before we move onto the state of our CD? 15:50:41 so for our CD, I think we still have some work to do 15:50:52 fao89: ^ 15:51:10 it sounds like we need the rubygem key for one thing 15:51:16 we need the environment variables, the RUBY one for example 15:51:25 I have the pypi key 15:51:31 yeah I only have pypi 15:51:44 and we also need the docs key 15:51:45 i have the rubygem key 15:51:52 for "simple" plugins I believe only the variables are blocking 15:51:53 #info dkliban has joined triage 15:51:53 !here 15:51:53 dkliban: dkliban has joined triage 15:52:06 I have only ttereshc key 15:52:16 :) 15:52:27 but plugins that have additional jobs, like performance tests we need to work more on it 15:52:39 yea, I have tickets for that under the epic 15:53:00 I think the other piece is the docs job. I don't think it works but we need the key to move that forward 15:53:01 pulp_rpm needs the CDN certs which i believe that i have 15:54:00 dkliban: so would you be able to set these keys taht you have in the pulp org (ruby, docs, etc)? 15:54:11 yes, that's what i am saying 15:54:19 ok, just confirming 15:54:24 is there anything else then? 15:54:56 next go/no-go on wednesday? 15:55:14 +1 15:55:19 +1 and thank you 15:55:28 sorry for joining so late 15:55:29 +1 15:55:34 I assume the installer team is ready to go btw? 15:55:42 dkliban: no worries 15:55:45 Yes 15:56:02 great. alright see you all on wednesday. 15:56:12 #endmeeting 15:56:12 !end