14:33:54 #startmeeting Pulp Triage 2020-04-03 14:33:54 !start 14:33:54 #info fao89 has joined triage 14:33:54 Meeting started Fri Apr 3 14:33:54 2020 UTC. The chair is fao89. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:33:54 Useful Commands: #action #agreed #help #info #idea #link #topic. 14:33:54 The meeting name has been set to 'pulp_triage_2020-04-03' 14:33:54 fao89: fao89 has joined triage 14:34:03 #info daviddavis has joined triage 14:34:03 !here 14:34:03 daviddavis: daviddavis has joined triage 14:34:06 #info ttereshc has joined triage 14:34:06 !here 14:34:06 ttereshc: ttereshc has joined triage 14:34:08 !next 14:34:10 #topic https://pulp.plan.io/issues/6443 14:34:10 fao89: 4 issues left to triage: 6443, 6438, 6437, 6434 14:34:10 #info dkliban has joined triage 14:34:10 !here 14:34:11 RM 6443 - daviddavis - NEW - Remove documentation that S3 is in tech preview 14:34:12 https://pulp.plan.io/issues/6443 14:34:13 dkliban: dkliban has joined triage 14:34:24 accept and add to sprint 14:34:25 #info bmbouter has joined triage 14:34:25 !here 14:34:25 this is a task but I wonder if we should add to sprint/3.3 milestone? 14:34:26 bmbouter: bmbouter has joined triage 14:34:29 #idea Proposed for #6443: accept and add to sprint 14:34:29 !propose other accept and add to sprint 14:34:29 fao89: Proposed for #6443: accept and add to sprint 14:34:35 +1 14:34:41 +1 14:34:54 #agreed accept and add to sprint 14:34:54 !accept 14:34:55 fao89: Current proposal accepted: accept and add to sprint 14:34:55 #topic https://pulp.plan.io/issues/6438 14:34:56 fao89: 3 issues left to triage: 6438, 6437, 6434 14:34:57 RM 6438 - binlinf0 - NEW - Pulp 3.2.1 not able to sync to redhat 14:34:58 https://pulp.plan.io/issues/6438 14:35:11 accept and add to sprint, blocks 3.3 release 14:35:14 +1 14:35:17 #idea Proposed for #6438: accept and add to sprint 14:35:17 !propose other accept and add to sprint 14:35:17 fao89: Proposed for #6438: accept and add to sprint 14:35:20 +1 14:35:25 +1 14:35:25 #agreed accept and add to sprint 14:35:25 !accept 14:35:25 fao89: Current proposal accepted: accept and add to sprint 14:35:26 #topic https://pulp.plan.io/issues/6437 14:35:26 fao89: 2 issues left to triage: 6437, 6434 14:35:27 RM 6437 - daviddavis - NEW - Generating bindings fails if my server isn't at localhost:24817 14:35:28 https://pulp.plan.io/issues/6437 14:35:43 accept 14:35:47 can we wait to fix this? 14:35:53 +1 14:35:57 +1 to just accept 14:35:58 it's super low priority 14:35:59 #idea Proposed for #6437: Leave the issue as-is, accepting its current state. 14:35:59 !propose accept 14:35:59 fao89: Proposed for #6437: Leave the issue as-is, accepting its current state. 14:36:19 #agreed Leave the issue as-is, accepting its current state. 14:36:19 !accept 14:36:19 fao89: Current proposal accepted: Leave the issue as-is, accepting its current state. 14:36:20 #topic https://pulp.plan.io/issues/6434 14:36:20 fao89: 1 issues left to triage: 6434 14:36:21 RM 6434 - mdepaulo@redhat.com - NEW - ansible-pulp does not ensure that a full Unicode locale is installed 14:36:22 https://pulp.plan.io/issues/6434 14:36:32 accept and add to sprint 14:36:43 #idea Proposed for #6434: accept and add to sprint 14:36:43 !propose other accept and add to sprint 14:36:43 fao89: Proposed for #6434: accept and add to sprint 14:36:58 #agreed accept and add to sprint 14:36:58 !accept 14:36:58 fao89: Current proposal accepted: accept and add to sprint 14:36:59 fao89: No issues to triage. 14:37:15 Open Floor! 14:37:42 https://pulp.plan.io/issues/6347 14:37:50 i think this issue needs to block 3.3 release 14:38:31 +1, I think we agreed on that 14:38:48 +1 14:38:56 we need that to be fixed for 3.3 14:39:04 +1 14:39:13 how do we formally block it? 14:39:16 +1 14:39:30 tag? or blocks_release? 14:39:34 add it to the 3.3 milestone I think 14:39:51 yes add to the mielstone, those will block the release 14:39:53 https://tinyurl.com/create.php?source=indexpage&url=https%3A%2F%2Fpulp.plan.io%2Fissues%3Futf8%3D%25E2%259C%2593%26set_filter%3D1%26f%255B%255D%3Dfixed_version_id%26op%255Bfixed_version_id%255D%3D%253D%26v%255Bfixed_version_id%255D%255B%255D%3D83%26f%255B%255D%3D%26available_columns%255B%255D%3Dfixed_version%26c%255B%255D%3Dproject%26c%255B%255D%3Dtracker%26c%255B%255D%3Dstatus%26c%255B%255D%3Dpriority%26c% 14:39:55 255B%255D%3Dcf_5%26c%255B%255D%3Dsubject%26c%255B%255D%3Dauthor%26c%255B%255D%3Dassigned_to%26c%255B%255D%3Dcf_3%26c%255B%255D%3Dcf_7%26group_by%3Dstatus%26t%255B%255D%3D&alias= 14:40:00 wow 14:40:01 wrong paste https://tinyurl.com/vcrk8gc 14:40:06 eheh 14:40:18 "tiny url" hahaha 14:40:30 exactly 14:40:36 so we need to add a milestone to it? 14:40:41 yes 14:40:48 ok ... i'll do that 14:40:56 also 6438 we need that to block 3.3 also? 14:41:02 yes 14:41:06 https://pulp.plan.io/issues/6438 14:41:24 bmbouter: the milestone is not shared accross projects 14:41:25 I updated 6438 14:41:29 and that issue is on pulp_file now 14:41:33 i am going to move it to pulpcore 14:41:37 cool 14:41:45 +1 to moving it, the fix will occur in pulpcore 14:41:50 maybe pulpcore and pulp_file can share milestones? 14:41:54 and lmjachky fyi ^ ? 14:41:58 they always come together 14:42:15 perhaps they should 14:43:13 it's not very easy though, but one option is to make pulp_file a subproject in redmine of pulpcore 14:43:24 then it owuld be easy because milestones have a "share with subproject" option 14:43:27 https://pulp.plan.io/versions/83/edit 14:43:36 oh I see 14:43:54 I thought one can choose whether to share with a specific ones or all 14:44:25 I don't see this problem happening frequently enough ATM to solve it right now personally 14:44:44 +1 14:44:51 sounds good 14:45:25 i now see 4 issues on the 3.3.0 milestone 14:45:33 is there anything else we should add? 14:45:34 I also do and I think those are the only ones I expected 14:45:39 yes good question, any others? 14:46:19 lgtm 14:46:28 i can't think of any others right now 14:48:20 adjourn? 14:48:29 +1 14:48:34 yep 14:48:39 !friday 14:48:39 ♪ It's Friday, Friday, gotta get down on Friday ♪ 14:48:56 !yadirf 14:48:56 ttereshc: Error: "yadirf" is not a valid command. 14:49:06 pulpbot, you are boring 14:49:06 ttereshc: Error: "you" is not a valid command. 14:49:22 #endmeeting 14:49:22 !end