14:05:11 <dalley> #startmeeting Pulp Triage 2021-05-11
14:05:11 <dalley> #info dalley has joined triage
14:05:11 <dalley> !start
14:05:11 <pulpbot> Meeting started Tue May 11 14:05:11 2021 UTC.  The chair is dalley. Information about MeetBot at http://wiki.debian.org/MeetBot.
14:05:11 <pulpbot> Useful Commands: #action #agreed #help #info #idea #link #topic.
14:05:11 <pulpbot> The meeting name has been set to 'pulp_triage_2021-05-11'
14:05:11 <pulpbot> dalley: dalley has joined triage
14:06:05 <ipanova> #info ipanova has joined triage
14:06:05 <ipanova> !here
14:06:05 <pulpbot> ipanova: ipanova has joined triage
14:06:08 <daviddavis> #info daviddavis has joined triage
14:06:08 <daviddavis> !here
14:06:08 <pulpbot> daviddavis: daviddavis has joined triage
14:06:26 <dalley> so we discussed in the pulpcore meeting that we can either push the release back a few days, OR drop https://pulp.plan.io/issues/8386
14:06:35 <ggainey> #info ggainey has joined triage
14:06:35 <ggainey> !here
14:06:37 <pulpbot> ggainey: ggainey has joined triage
14:06:57 <ttereshc> #info ttereshc has joined triage
14:06:57 <ttereshc> !here
14:06:57 <pulpbot> ttereshc: ttereshc has joined triage
14:07:25 <dalley> we should probably decide which, and if the former (as I believe we were leaning towards), then what date should we pick?
14:07:29 <ggainey> dalley: what about 8691? (django issue) - do we need to wait for them to release their fix? or does their fix release us from that issue?
14:07:57 <daviddavis> yes, I think we have to wait on them
14:08:15 <ggainey> (I'm good w/ waiting, esp since we want/need to get a pulp_rpm release that is 3.7-compat out before we move to 3.13, yeah?)
14:08:18 <ggainey> daviddavis: kk
14:08:18 <daviddavis> no idea when they'll release 2.2.23
14:08:19 <dalley> if we need to wait anyways then it makes the decision easy :)
14:08:23 <ggainey> yus
14:08:50 <dalley> in my pulp-dev email I mentioned May 18 would probably be a good fallback date. that's next Tuesday
14:08:51 <bmbouter> I think it will be in the next few days
14:08:57 <ggainey> given where we are, and that we're depending on an upstream-release, I'd suggest a week
14:08:58 <ggainey> yeah
14:08:59 <ggainey> that
14:09:00 <ggainey> :)
14:09:03 <x9c4> #info x9c4 has joined triage
14:09:03 <x9c4> !here
14:09:03 <pulpbot> x9c4: x9c4 has joined triage
14:09:18 <ggainey> bmbouter: concur
14:10:20 <ipanova> so what i am hearing we are waiting on django release, should we meet again on monday-ish?
14:10:25 <bmbouter> +1
14:10:27 <ttereshc> I think May 18 sounds fine
14:10:28 <ggainey> w4m
14:10:34 <ggainey> +1
14:10:37 <ttereshc> Friday or Monday
14:10:38 <dalley> +1 Monday
14:10:39 <x9c4> +1
14:10:47 <bmbouter> and for 8386 do we move that to 3.14 and if rpm team says include it we can, but defaults to 3.14?
14:10:48 <daviddavis> we'll probably need a release backup as dalley is out on the 19th
14:10:55 <dalley> actually, I'll pick Friday or Monday based on availability
14:11:11 <bmbouter> I think i'm releasing like 4 releases, I could do 5
14:11:13 <dalley> ie. meetings
14:11:20 <ipanova> bmbouter is going wild :D
14:11:31 <ggainey> ha!
14:12:16 <dalley> everything else is in post except for https://pulp.plan.io/issues/7316
14:12:35 <ipanova> dkliban is the next one after bmbouter and then me, so either of us could help with the release duties
14:12:37 <daviddavis> I moved 8386 to 3.14 after our meeting but I don't have a strong opinion
14:12:53 <bmbouter> daviddavis: sounds good
14:12:57 <mikedep333> #info mikedep333 has joined triage
14:12:57 <mikedep333> !here
14:12:57 <pulpbot> mikedep333: mikedep333 has joined triage
14:13:00 <ipanova> daviddavis: ok
14:13:07 <daviddavis> I don't think 7316 needs to block 3.13 personally
14:13:18 <ttereshc> can we decide on 8386 on the next go/no-go? it will be clearer what to do with it
14:13:26 <ipanova> daviddavis: agree
14:13:33 <x9c4> daviddavis, ok Merging removals early is a good idea anyway.
14:13:34 <daviddavis> ttereshc: +1. I'll add it back to 3.13 then?
14:13:45 <dalley> yes, we can definitely change our minds about 8386 at the next no-go
14:13:46 <ggainey> sure
14:13:52 <ipanova> yeah
14:14:13 <daviddavis> x9c4: I agree. leaning towards 3.14 myself.
14:14:52 <daviddavis> we can discuss at next go/no-go though
14:15:18 <dalley> yeah there is not much harm in simply delaying it to be honest.
14:15:25 <dalley> but we can discuss again
14:15:31 <daviddavis> yup
14:15:42 <dalley> bmbouter, re: 7316, what are your thoughts? I see you had some difficulty reproducing
14:16:40 <bmbouter> yeah the artifacts are fine
14:16:46 <bmbouter> but I need to verify the uploads which I am doing today
14:16:54 <bmbouter> uploadChunks, all that
14:17:33 <bmbouter> I'd say leave it on 3.13 for now and either it'll be in POST/MODIFIED by the next go/no-go or we'll remove it
14:17:45 <dalley> +1
14:17:46 <bmbouter> I think at least we know the severity has gone way down (imo at least)
14:17:54 <daviddavis> +1
14:18:12 <ggainey> +1
14:18:30 <ipanova> +1 to verify upload workflow
14:18:34 <ttereshc> +1
14:18:52 <dalley> great. any other topics to discuss?
14:20:12 <ipanova> any installer issues aligned with 3.13?
14:20:18 <ipanova> mikedep333: ^
14:21:00 <mikedep333> daviddavis: You asked me to implement the private key support for the database.
14:21:03 <mikedep333> Does 3.13 depend on that?
14:21:07 <daviddavis> no
14:21:39 <mikedep333> great
14:21:41 <daviddavis> the pulpcore feature will probably land in 3.14
14:21:43 <daviddavis> yea
14:21:45 <mikedep333> No installer issues blocking 3.13
14:25:19 <daviddavis> triage in 5 min: https://hackmd.io/@pulp/triage/edit https://pulp.plan.io/issues?query_id=143
14:26:34 <ggainey> so I'm hearing "3.13 now on 18-MAY, next go/nogo to be Fri or Mon, bmbouter tentatively sched as dalley-backup next week"?
14:27:35 <dalley> sounds right
14:27:41 <dalley> #endmeeting
14:27:41 <dalley> !end