14:01:07 #startmeeting Pulp Triage 2021-04-07 14:01:07 #info x9c4 has joined triage 14:01:07 !start 14:01:07 Meeting started Wed Apr 7 14:01:07 2021 UTC. The chair is x9c4. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:01:07 Useful Commands: #action #agreed #help #info #idea #link #topic. 14:01:07 The meeting name has been set to 'pulp_triage_2021-04-07' 14:01:07 x9c4: x9c4 has joined triage 14:01:14 #info daviddavis has joined triage 14:01:14 !here 14:01:14 daviddavis: daviddavis has joined triage 14:01:37 Go-NoGo for 3.12 - 8-Apr 14:01:56 #info ggainey has joined triage 14:01:56 !here 14:01:56 ggainey: ggainey has joined triage 14:02:29 Roadmap: https://pulp.plan.io/versions/182 14:02:32 #info ttereshc has joined triage 14:02:32 !here 14:02:32 ttereshc: ttereshc has joined triage 14:03:06 #info dalley has joined triage 14:03:06 !here 14:03:06 dalley: dalley has joined triage 14:03:18 #info ipanova has joined triage 14:03:18 !here 14:03:18 ipanova: ipanova has joined triage 14:03:22 all items seems to be closed 14:03:31 wow 14:04:00 looks good 14:04:15 this might be the first release we weren't merging stuff the day of 14:04:30 daviddavis: same thought :D 14:04:34 hehe 14:04:37 should I merge this? https://github.com/pulp/pulpcore/pull/1235 14:05:05 it's not needed but it wouldn't hurt I don't think 14:05:11 +1 why not 14:05:19 daviddavis: yes 14:05:21 +1 two ACKs 14:05:42 +1 14:05:44 so the motivation for that one, just to make sure I understand, is to just have one special case (the latest version) rather than two (the first and the latest)? 14:06:26 kinda: a repo must have one version 14:06:35 which yea, would be latest at that point 14:06:43 you could delete latest though if there's another version 14:07:05 it makes the version retention feature simpler since it can now cleanup verison 0 14:07:40 instead of having to introduce some weird logic to either skip version 0 etc 14:07:52 and less confusing to the user, since they can say "I want 1 version", and have one version, instead of 2 14:08:00 yea 14:08:25 daviddavis, I think we should try to squeak the resource locking fix in 14:08:38 #info mikedep333 has joined triage 14:08:38 !here 14:08:39 mikedep333: mikedep333 has joined triage 14:08:55 https://github.com/pulp/pulpcore/pull/1228 ? 14:08:55 thanks for the explanation - that makes sense 14:09:04 I agree it would be nice to get https://github.com/pulp/pulpcore/pull/1228 in 14:09:13 but we could backport it since it's a bug fix 14:09:29 I'd like to review it today. 14:09:49 x9c4: that'd be great 14:10:29 let's try to get https://github.com/pulp/pulpcore/pull/1228 into 3.12 but not have it be a blocker. does that sound good? 14:10:35 +1 14:10:39 +1 14:10:40 +1 14:10:59 we need to keep the tradition to merge at last minute 14:10:59 with that, I think we are good for tomorrow? 14:11:08 lg2m 14:11:12 Agreed 14:11:16 yea 14:11:17 ttereshc: hehehe 14:11:35 The new release code is in place too, i have seen. 14:12:26 i mean release automation... 14:12:30 cool 14:12:44 x9c4: yea, I updated the 3.12 checklist too 14:12:53 daviddavis++ 14:12:53 x9c4: daviddavis's karma is now 470 14:12:59 daviddavis++ 14:12:59 dalley: daviddavis's karma is now 471 14:13:08 I used it on pulp_file and it went smoothly so hopefully for pulpcore too 14:13:32 fingers crossed 14:13:34 daviddavis++ 14:13:34 ipanova: daviddavis's karma is now 472 14:14:26 * x9c4 is excited to see it perform in new and unexpected ways. ;) 14:14:35 daviddavis++ 14:14:35 ggainey: daviddavis's karma is now 473 14:14:40 heh 14:14:52 lol 14:14:54 'exciting' is...not what we want, but def what we expect :) 14:15:29 I appreciate, that it is _way_ more resiliant to being restarted. 14:16:15 resilient is a great word, strongly approve 14:17:41 so any last calls for not releasing tomorrow? 14:18:46 nope 14:18:54 3 14:18:56 2 14:19:00 1 14:19:13 shippit! 14:19:13 #endmeeting 14:19:13 !end