14:00:04 #startmeeting releaseteam 14:00:04 Meeting started Fri May 26 14:00:04 2023 UTC and is due to finish in 60 minutes. The chair is hberaud. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:00:04 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:00:04 The meeting name has been set to 'releaseteam' 14:00:08 ping: elodilles armstrong 14:00:10 o/ 14:00:19 See you at line 149 => https://etherpad.opendev.org/p/bobcat-relmgt-tracking 14:01:11 #topic Review R-20 and R-19 task completion 14:01:25 1) Review any remaining milestone-1 exceptions 14:01:39 I think we are done with this one 14:02:25 hmmm 14:02:27 https://review.opendev.org/q/topic:bobcat-milestone-1+status:open 14:02:32 2 remains opened 14:02:35 we have 2 open patches 14:02:39 yeah 14:03:03 lets check the first one 14:03:09 nothing relevant code in those releases though 14:03:14 (tosca-parser) 14:03:53 i think we can abandon this really 14:04:04 do we want to abandon them? 14:04:18 we'll still have 2 more milestone to release, perhaps there will be more content to release 14:04:31 as this is M1, I don't think we need to force them 14:04:45 yes, that's my understanding, too 14:04:51 usually we abandoned them 14:05:09 i'll abandon the tosca-parser patch 14:05:14 ok 14:05:34 the python-manilaclient contains response from PTL 14:06:11 yeah either we ask them their status, or we abandon this one too and release their stuffs with M2 14:06:29 i'll comment on the patch about abandoning if not needed 14:06:52 they replied 2 weeks ago so I don't think they are in hurry to release their changes 14:07:06 ok, wfm 14:07:44 ++ 14:07:54 2) Prepare 2023.1 Antelope cycle trailing 14:07:58 thanks elodilles 14:08:37 yepp 14:08:39 this one 14:08:52 I've reminded Kolla and OpenStack Ansible team via IRC 14:09:09 cinderlib and puppet deliverables were released already 14:09:29 the deadline is next week, exact? 14:09:35 so ansible-collection-kolla, openstack-ansible-roles, openstack-ansible and kayobe + kolla-ansible, kolla are missing 14:09:44 yes, next week is the deadline 14:09:47 (the antelope trailing deadline 14:10:01 so I think we need a reminder 14:10:17 ah we already have one 14:10:21 (more or less) 14:11:16 i haven't prepared release patches as the PTLs seemed aware of the deadline, but you are maybe right, i can push release patches to emphasize the deadline :) 14:11:23 will do it after the meeting 14:11:33 as you want, can't hurt 14:11:45 thans 14:11:48 thanks 14:12:05 yeah, reminding them sooner would be good if it's not too much trouble 14:12:18 ++ 14:12:21 sometimes it helps to lead them by the nose a bit since they have a lot of other competing distractions 14:12:55 that's true 14:13:07 and that's all for task completion 14:13:19 #topic Assign next week tasks 14:13:36 everything is now assigned 14:14:03 thanks hberaud :) 14:14:10 np 14:14:16 #topic Review next week's countdown email in advance 14:14:44 https://etherpad.opendev.org/p/relmgmt-weekly-emails 14:14:59 the template used come from => https://releases.openstack.org/reference/process.html#between-milestone-1-and-milestone-2 14:15:28 this email should be sent between M1 and M2, however the next meetings are skipped 14:15:39 3 meetings 14:15:56 hberaud: this topic is for the next week i think 14:16:10 and the M2 is 2 weeks after these 3 skipped meetings 14:16:41 ah yes sorry 14:16:58 but the problem remains the same 14:17:12 and this email should be sent at some point 14:17:26 so maybe we could keep it for the next week? 14:17:44 yepp, at R-17, Friday, June 09 14:18:07 ah good catch, I missed that line 14:18:14 so topic closed 14:18:33 anyway the email content is ready 14:18:37 #topic Open Discussion 14:18:59 from you elod - do we need to change anything regarding this?: pypi is removing gpg support. Pushing those files will still "work" but they will be ignored. Not sure if we do that or rely on it 14:19:26 yes, this warning came to our channel here 14:19:41 I've no idea if that impact us 14:19:49 and i don't know from top off my head whether we need to do anything regarding this 14:20:32 i hoped that either you or Thierry knows this by heart o:) 14:21:29 anyway, we can check our tools 14:21:43 yeah 14:22:01 by reading https://discuss.python.org/t/gpg-signature-support-removed-from-pypi/27014/3 I don't think it impact us 14:23:10 I think we need some updates there => https://opendev.org/openstack/releases/src/branch/master/openstack_releases/tests/fixtures.py#L27 14:23:23 or not... 14:23:56 this code don't seems related to pypi 14:24:33 and we continue to generate gpg however we simply do not use pypi to publish them 14:24:46 that's my understanding 14:24:48 We produce the files but I'm not sure if we upload them to pypi. If we do upload them we should probably stop to prevent breakage when twine or whatever tool inevitably remove support for it 14:25:37 ACK, thanks for the details 14:25:55 ok 14:26:17 i'll add this to my TODO to check this 14:26:28 thanks 14:26:35 Anything else that you want to discuss today? 14:26:38 but i'll appreciate if someone else also looks into it :) 14:26:51 I can double check too 14:26:52 nothing else from me 14:27:01 hberaud: ++ 14:27:02 thx 14:27:18 then I think we are done 14:27:32 thanks everyone for joining 14:27:38 thanks too o/ 14:27:41 #endmeeting