15:30:54 #startmeeting Pulp Triage 2020-11-17 15:30:54 !start 15:30:54 #info fao89 has joined triage 15:30:54 Meeting started Tue Nov 17 15:30:54 2020 UTC. The chair is fao89. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:30:54 Useful Commands: #action #agreed #help #info #idea #link #topic. 15:30:54 The meeting name has been set to 'pulp_triage_2020-11-17' 15:30:54 fao89: fao89 has joined triage 15:30:58 #info daviddavis has joined triage 15:30:58 !here 15:30:58 daviddavis: daviddavis has joined triage 15:30:59 #info ggainey has joined triage 15:30:59 !here 15:31:00 ggainey: ggainey has joined triage 15:31:28 https://hackmd.io/@pulp/triage/edit 15:32:15 not likely to have too many ppl today 15:32:21 #info x9c4 has joined triage 15:32:21 !here 15:32:21 x9c4: x9c4 has joined triage 15:32:24 I think we don't have quorum even for open floor 15:33:05 #info dalley has joined triage 15:33:05 !here 15:33:05 dalley: dalley has joined triage 15:33:15 now we have it 15:33:18 heh 15:33:21 topic: 3.10 release timeframe? 15:33:32 mid-December (eg Dec 21) or early January? 15:33:59 early January 15:34:06 so I think early-Jan is better - releasing at the end of Dec is just asking for not having the right ppl available to push all the buttons, and/or ppl working over holidays to fix problems 15:34:11 releasing right before the holidays is a recipe for badness 15:34:13 +1 15:34:19 bad things 15:34:22 that works for me 15:34:39 maybe jan 7th is good 15:34:46 agreed 15:34:52 sure 15:34:54 I imagine we'll also have the go/no-go meeting in january 15:35:20 yeah - maybe the 4th? 15:35:23 +1 15:35:55 didn't we have two checkins last time? 15:36:14 how about the release owner? should we wait for the next open floor? 15:36:15 could see having something in mid-Dec? 15:36:23 I'd wait 15:36:37 yea let's wait 15:36:40 #info mikedep333 has joined triage 15:36:40 !here 15:36:40 mikedep333: mikedep333 has joined triage 15:36:57 I do remember there being 2 go/no-go meetings but I don't remember why 15:37:05 I was only planning on having one for 3.9 15:37:18 +1 15:37:22 #info bmbouter has joined triage 15:37:22 !here 15:37:22 bmbouter: bmbouter has joined triage 15:37:25 well, if you have one and the answer is no-go, you'll eventually have a second :) 15:37:30 haha yea 15:37:38 we are getting more mature about go/no-go, I think we can try just 1 15:37:44 coolio 15:37:48 sounds good 15:37:58 I thought it was like still-go/no-go and then go/no-go 15:38:46 hmm ok 15:39:04 Not saying that i _want_ two. 15:39:27 ther's time - maybe wait til we have a release-manager, and let them make the call? 15:39:38 +1 15:39:40 +1 15:39:43 +1 15:39:50 I'll ask for a release manager at our next pulpcore meeting 15:39:53 coolio 15:40:05 next topic: Completely drop support of Travis from plugin_template? 15:40:23 yes, the question is when 15:40:26 once everything is running on actions? 15:40:34 no... Let's not make it "no way back" until we are there. 15:40:51 We can disinclude it from all. 15:41:06 +1 15:41:13 I think we can drop it now. No plugins that use Travis will be able to use it for very long. 15:41:29 good point! 15:41:37 I would prefer to wait 15:41:48 Travis is not going to change the way it's going to be used. 15:42:06 yea, wait until everything's running on GHA and then drop it 15:42:07 And we should not force community plugins to move right now. 15:42:08 maybe we don't have the wait option, we don't know when travis will change our plan 15:42:11 if we hit a showstopper w/github, we *could* continue with Travis - we'd just have to hold bake-sales to pay for it for a while :) 15:42:26 ha yea 15:42:27 xactly 15:42:43 to be clear 15:42:52 so my $0.02US is wait till we're up and running on actions 15:42:55 I guess some community plugins will use so few minutes, they'll be OK. 15:42:55 if you look at dalley's pr his changes live alongside Travis files 15:43:09 But we can also count our community plugins with one hand. 15:43:18 agreed 15:43:21 aye 15:43:30 I just want to make sure github actions is up and running before we drop travis support 15:43:31 what happens if travis change our plan tomorrow? 15:43:38 I mean potential ones we don't know about. 15:43:47 that don't live in the pulp org 15:43:48 fao89: then we have an emergency 15:43:58 we use 8000 minutes week 15:44:16 fao89: to be clear we're not delaying moving to github actions 15:44:23 we're just not dropping the travis code until we've moved 15:44:38 gotcha! 15:44:41 until then and a bit 15:44:44 +1 15:44:57 +1 15:45:16 +1 15:45:31 +1 15:45:45 +1 15:45:52 +1 15:45:55 I'll start triage, unless someone wants to bring another topic 15:46:29 !next 15:46:30 #topic https://pulp.plan.io/issues/7838 15:46:31 fao89: 3 issues left to triage: 7838, 7836, 7796 15:46:32 RM 7838 - mdellweg - NEW - file publication reports wrong manifest if custom manifest is used 15:46:33 https://pulp.plan.io/issues/7838 15:46:55 #idea Proposed for #7838: Leave the issue as-is, accepting its current state. 15:46:55 !propose accept 15:46:55 fao89: Proposed for #7838: Leave the issue as-is, accepting its current state. 15:47:01 oo, interesting 15:47:12 +1 15:47:20 +1 15:47:38 #agreed Leave the issue as-is, accepting its current state. 15:47:38 !accept 15:47:39 fao89: Current proposal accepted: Leave the issue as-is, accepting its current state. 15:47:39 #topic https://pulp.plan.io/issues/7836 15:47:40 fao89: 2 issues left to triage: 7836, 7796 15:47:41 RM 7836 - ggainey - NEW - Import fails when ArtifactResource.json has blank checksums 15:47:42 https://pulp.plan.io/issues/7836 15:47:50 oh right 15:48:00 found this while testing fips/checksum workflows 15:48:16 +1 15:48:27 #idea Proposed for #7836: accept and add to sprint 15:48:27 !propose other accept and add to sprint 15:48:27 fao89: Proposed for #7836: accept and add to sprint 15:48:34 we're mtg this afternon if anyone is interested 15:48:38 yes please 15:48:44 +1 15:49:09 #agreed accept and add to sprint 15:49:09 !accept 15:49:09 fao89: Current proposal accepted: accept and add to sprint 15:49:10 #topic https://pulp.plan.io/issues/7796 15:49:10 fao89: 1 issues left to triage: 7796 15:49:11 RM 7796 - tosif.meman@kindredgroup.com - NEW - Pulp Version 2.20 - Mongod and pulp_celerybeat failing randomly 15:49:12 https://pulp.plan.io/issues/7796 15:49:28 close out? 15:49:36 or wait longer? 15:50:04 I'll close it out 15:50:05 we have nothing from the user, it's an old version of pulp2, and it's "when mongo breaks things get odd" - I'd close 15:50:08 yeah 15:50:11 ok 15:50:25 #idea Proposed for #7796: close out 15:50:25 !propose other close out 15:50:25 fao89: Proposed for #7796: close out 15:50:26 yup 15:50:29 #agreed close out 15:50:29 !accept 15:50:30 fao89: Current proposal accepted: close out 15:50:31 fao89: No issues to triage. 15:50:45 #endmeeting 15:50:45 !end