14:30:42 #startmeeting Pulp Triage 2021-05-04 14:30:42 #info daviddavis has joined triage 14:30:42 !start 14:30:42 Meeting started Tue May 4 14:30:42 2021 UTC. The chair is daviddavis. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:30:42 Useful Commands: #action #agreed #help #info #idea #link #topic. 14:30:42 The meeting name has been set to 'pulp_triage_2021-05-04' 14:30:42 daviddavis: daviddavis has joined triage 14:30:58 #info ipanova has joined triage 14:30:58 !here 14:30:58 ipanova: ipanova has joined triage 14:31:42 #info ttereshc has joined triage 14:31:42 !here 14:31:42 ttereshc: ttereshc has joined triage 14:31:55 #info gerrod has joined triage 14:31:55 !here 14:31:55 gerrod: gerrod has joined triage 14:32:15 Open floor agenda: https://hackmd.io/@pulp/triage/edit 14:32:30 Topic: 3.13 proposed release date and lead 14:32:34 #info bmbouter has joined triage 14:32:34 !here 14:32:34 bmbouter: bmbouter has joined triage 14:33:07 I think we proposed may 12 and looks like dalley will be the lead 14:33:10 here's the milestone https://pulp.plan.io/versions/188 14:33:55 any feedback is welcome 14:34:34 +1 14:34:55 we took on a bunch of items today, hopefully they can all be completed before may 12 14:35:09 yea, agreed 14:35:10 I do not remember if dalley released it before but I wonder if we have or need any checklist for the release lead, like sending schedule emails, scheduling go/no-go, etc 14:35:46 we have a release checklist but it doesn't cover sending schedule emails, go/no-go etc 14:35:48 maybe it should? 14:36:03 pre-release checklist :) 14:36:04 that's more like a 'pre-release checklist' 14:36:09 heh 14:36:16 +1 14:36:29 whatever it is called :) 14:36:46 anyone interested in taking a stab at it? 14:37:09 I can add steps to the existing release checklist in redmine 14:37:29 where would we keep it? directly on the template? 14:37:50 +1 14:37:55 i guess that should be ok 14:38:12 +1 14:39:06 anything else related to 3.13? 14:39:43 we should probably have a go/no go meeting ...on friday? 14:40:20 or thursday, but basically this week 14:40:26 +1 14:40:34 #info ggainey has joined triage 14:40:34 !here 14:40:35 ggainey: ggainey has joined triage 14:41:20 ok, on to triage? 14:42:01 +1 14:42:04 !next 14:42:05 daviddavis: 3 issues left to triage: 8687, 8679, 8678 14:42:05 #topic https://pulp.plan.io/issues/8687 14:42:06 RM 8687 - dalley - NEW - DeclarativeVersion API doesn't accomodate metadata mirroring use cases 14:42:07 https://pulp.plan.io/issues/8687 14:42:32 I wasn't sure how to classify this 14:43:08 it could probably be a refactor or a story 14:43:37 +1 story 14:43:45 +1 to a story 14:43:47 because it will include net-new changes we couldn't put into z release 14:43:50 +1 14:43:56 +1 story 14:44:36 +1 14:44:42 #idea Proposed for #8687: convert to story 14:44:42 !propose other convert to story 14:44:42 daviddavis: Proposed for #8687: convert to story 14:44:49 #agreed convert to story 14:44:49 !accept 14:44:49 daviddavis: Current proposal accepted: convert to story 14:44:50 #topic https://pulp.plan.io/issues/8678 14:44:50 daviddavis: 1 issues left to triage: 8678 14:44:51 RM 8678 - gerrod - NEW - Provide 'view_name' warning when using the all in one container 14:44:52 https://pulp.plan.io/issues/8678 14:45:01 the UI students ran into this too 14:45:22 add to sprint? or just accept? 14:45:34 accept? 14:45:37 add to the sprint? 14:45:41 :D 14:45:42 should be an easy fix 14:45:46 sure 14:45:47 and it's user facing 14:45:56 #idea Proposed for #8678: accept and add to sprint 14:45:56 !propose other accept and add to sprint 14:45:56 daviddavis: Proposed for #8678: accept and add to sprint 14:45:59 +1 14:46:04 users might be worried that something is off 14:46:14 yeah zacly 14:46:19 #agreed accept and add to sprint 14:46:19 !accept 14:46:19 daviddavis: Current proposal accepted: accept and add to sprint 14:46:20 daviddavis: No issues to triage. 14:46:23 #endmeeting 14:46:23 !end