14:00:05 #startmeeting releaseteam 14:00:05 Meeting started Fri Jul 15 14:00:05 2022 UTC and is due to finish in 60 minutes. The chair is elodilles. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:00:05 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:00:05 The meeting name has been set to 'releaseteam' 14:00:20 Ping list: armstrong ttx hberaud diablo_rojo_phone 14:00:24 o/ 14:00:33 #link https://etherpad.opendev.org/p/zed-relmgt-tracking 14:01:28 we are @ line 226 14:01:41 i mean... 14:01:49 line 209 14:01:52 R-12 14:02:14 o/ 14:04:29 let's start as time is running 14:04:43 #topic Review task completion 14:04:49 1st task was: 14:05:03 'Generate release requests for all cycle-with-intermediary libraries which had changes, but did not release since milestone-1. (elod)(armstrong)' 14:05:10 o/ 14:05:36 sorry armstrong , i created the patches myself in european time frame o:) 14:05:51 hberaud: o/ 14:05:57 https://review.opendev.org/q/topic:zed-milestone-2 14:06:52 only two remained open due to -1 signals from PTLs 14:07:00 elodilles: No problem 14:07:17 os-brick & python-manilaclient 14:07:35 hopefully we can merge them soon 14:08:09 otherwise i think we are good with this task 14:08:35 2nd task was: 14:08:42 'To catch if there are acl issues in newly created repositories, run tools/aclissues.py to detect potential leftovers in Gerrit ACLs allowing official deliverables to be directly tagged or branched without going through openstack/releases. (ttx)' 14:09:03 ttx is on PTO but left comment that 'Done, no ACL issues reported' 14:09:06 \o/ 14:09:28 3rd task was: 14:09:32 ok 14:09:35 'ping teams listed in R-13's consistency check task (elod)' 14:10:08 i've added the details to R-13 Tasks 14:10:21 but let's go through them one by one 14:10:36 neutron-fwaas, neutron-fwaas-dashboard 14:10:59 patch is created, needs review: https://review.opendev.org/c/openstack/releases/+/849865 14:11:16 * needs 2nd core review, actually 14:11:31 i've suggested beta releases ASAP (cycle-with-rc) to catch release issues early 14:12:03 * hberaud look 14:12:13 let me know in case we need something else ^^^ 14:12:54 next pack of deliverables were: 14:12:58 venus, venus-dashboard, python-venusclient, venus-tempest-plugin 14:13:14 mail was sent to PTL yesterday, 14:13:31 so we need to wait a bit for this 14:14:06 next ones: 14:14:12 skyline-apiserver, skyline-console 14:14:25 patch was created to Yoga, now added comment to update it to Zed if needed 14:14:46 and patch is ready to review: https://review.opendev.org/c/openstack/releases/+/831134 14:15:25 (this also needs a 2nd core review :)) 14:16:06 next: 14:16:12 rbd-iscsi-client (cinder) 14:16:21 team was contacted via IRC 14:16:42 independent release model is aimed for this deliverable, but CI is still not passing yet 14:16:51 so they are not planning yet to release 14:17:00 maybe next cycle 14:17:21 next is: 14:17:28 barbican-ui 14:17:39 PTL was pinged on IRC, got the answer that "still no work on that repo" so won't be part of Zed 14:18:11 and the last item was: 14:18:22 'panko, python-pankoclient, puppet-panko: marked deprecated in xena, should be removed from governance at some point' 14:18:34 i've created a patch to mark the repos as retired: https://review.opendev.org/c/openstack/governance/+/850005 14:18:43 do we need something else for this? (beyond reaching out to PTL) 14:20:20 hberaud: do you think this patch is enough? ^^^ 14:20:50 yes 14:21:07 ack, cool, thx \o/ 14:21:32 then i'll remove the WIP 'tag' from it 14:21:56 any comment for this task? 14:22:49 nope 14:22:55 if nothing, then let's move on to the next topic 14:23:05 #topic Assign R-11 tasks 14:23:44 i've added 'all' to this one: 'Review any remaining milestone-2 exceptions' 14:24:35 i'll try to plan the next release cycle (last task) but i'll definitely need reviews for that :) 14:24:49 I am available to help 14:25:08 and the fun part will be to contact the Foundation about the next series name 14:25:11 I will also like to know how you generate the schedule 14:25:30 armstrong: sure, let's try to do it together 14:26:12 let's choose some time slot when you'll be available next week, after the meeting 14:28:09 armstrong: added your name as well to the task then 14:28:30 also added my name to ' Reach out to project teams that have never-released deliverables and ask if they are ready to be included in Zed (or prefer to wait, or should be dropped)' 14:28:51 and actually that's all 14:29:25 #topic Review countdown email contents 14:29:41 #link https://etherpad.opendev.org/p/relmgmt-weekly-emails 14:29:45 please review ^^^ 14:32:29 LGTM! Also, dates are well aligned 14:33:11 cool, thanks, will send it after the meeting then! 14:33:54 #topic Open Discussion 14:34:05 LGTM 14:34:12 hberaud: thx! 14:34:32 so we have passed Zed-2 14:34:43 time is going fast 14:35:15 release naming update from this week's foundation newsletter: "Help us name the next OpenStack release! Community voting for the A release name finalists begins on Monday, July 18th with a deadline of July 20th at 11:59pm PT (July 21st 6:59 UTC). A link will be sent out via the openstack-discuss mailing list on Monday with a link to vote." 14:35:17 https://superuser.openstack.org/articles/openinfra-newsletter-46/ 14:35:53 (highlighting here since i know not everyone reads the newsletter) 14:36:27 fungi: oh, i missed that! thanks for sharing it now! 14:37:00 yw 14:37:36 anyway, that means we won't have a name for next week 14:38:13 and probably for some more weeks, due to legal things, i guess 14:38:33 they front-loaded the trademark search, i believe 14:38:51 so we will use 'aa' or something like that for the schedule planning 14:39:26 fungi: oh, awesome! so the process will be quicker then! 14:39:40 the process was: staff brainstormed a bunch of options and weeded out the obvious problem ones, then checked the results with legal, and are holding a poll the first half of next week to get the community to choose between those, with the idea of having it chosen for thursday i think 14:40:07 * fungi is not 100% sure of the accuracy of his summary 14:40:49 fungi: still, it sounds more secure to have a quick result :) 14:41:38 here's hoping 14:42:32 then our task is to vote next week :) 14:43:01 thanks again for the info 14:43:09 anything else to discuss? 14:43:50 * fungi has nothing else of relevance 14:44:01 nothing from me 14:44:11 neither have i 14:45:21 okay, thanks everyone for joining! 14:45:32 #endmeeting