14:00:27 #startmeeting releaseteam 14:00:27 Meeting started Fri Jan 14 14:00:27 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:27 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:00:27 The meeting name has been set to 'releaseteam' 14:00:35 Ping list: hberaud ttx armstrong 14:00:40 o/ 14:00:40 o/ 14:00:44 o/ 14:00:50 #link https://etherpad.opendev.org/p/yoga-relmgt-tracking 14:01:01 we are at line 183 14:01:49 Better :) 14:02:00 the mask is off! 14:02:05 :] 14:02:09 It is. 14:02:13 It was diablo all along 14:02:24 It is I! 14:02:51 it was like superman with his glasses :-o 14:03:28 ok, so, let's start with the topics 14:03:45 #topic Review task completion 14:04:08 1st task was: 14:04:17 Reach out to project teams that have never-released deliverables 14:04:30 and it was on me 14:04:48 so let's go one by one 14:05:27 barbican-ui: according to barbican PTL it is in alpha, they are not planning to release it in yoga 14:06:20 rbd-iscsi-client: it's also not release-ready, but it is aimed to be an independent deliverable 14:06:57 and now comes my question: do we have to do anything about these? for example adding something in governance repository? 14:08:00 no 14:08:09 we can wait 14:08:20 ack, cool 14:08:28 For the Yoga release it's good to know in advance what we should track as patr of it 14:08:37 i guess we will revisit them in next cycle if not sooner 14:08:37 but independent things can take their time 14:08:41 ++ 14:08:53 ok 14:09:09 so next one: venus teams deliverables 14:09:21 (venus, venus-dashboard, python-venusclient and venus-tempest-plugin) 14:09:44 o/ sorry to be late 14:09:55 hberaud: o/ 14:09:58 no problem 14:10:48 so venus team: an "empty" patch was proposed, but they are not ready to release yet as they have CI problems 14:11:46 (the patch https://review.opendev.org/c/openstack/releases/+/824394 ) 14:12:36 we discussed with ttx that it would be good to release something as soon as possible to catch release issues as early as possible 14:12:58 yeah like, not wait yoga-3 crush 14:13:15 and i'll ping with this info the team ASAP 14:13:25 ack 14:13:32 Sounds like a good plan to me 14:13:35 though from the last info they might not be ready soon :S 14:13:52 anyway, we will see 14:14:44 last deliverable: ansible-collection-kolla (kolla), same as venus: empty patch proposed 14:15:06 https://review.opendev.org/c/openstack/releases/+/824032 14:15:37 and i'll ping them too to prepare a release 14:16:05 that's all[4~ for this task, any comment? 14:16:42 Seems like it's all in hand :) 14:16:54 :] 14:17:09 next task 14:17:21 Plan the next release cycle schedule 14:17:42 no Z release name specified yet, so schedule is planned under the codename 'Zen' 14:17:50 https://review.opendev.org/c/openstack/releases/+/824489 14:18:33 Zen++ 14:18:52 afaik 26 week long should be the target, however i've created a 27 weeks long cycle, as it felt like most fitting 14:19:03 A good follow up to yoga 14:19:09 inded 14:19:12 indeed 14:19:46 yes, it's also among the proposed names, so we will see what will become the official name :) 14:20:18 by the way, you can propose names here: https://wiki.openstack.org/wiki/Release_Naming/Z_Proposals 14:20:21 :) 14:20:37 Fingers crossed! 14:21:32 of course i'll update the patch as soon as we have the official name, which we can expect around... 14:22:11 early february 14:22:49 according to the release naming process patch ( https://review.opendev.org/c/openstack/governance/+/824201 ) 14:22:55 A bit behind but not awful 14:23:55 we got already feedback that it's OK from Ubuntu point of view 14:24:20 who else should i contact? 14:25:07 is that OK if I send a mail to ML with this patch asking for feedbacks? 14:25:41 (i mean, the schedule) 14:28:48 yes 14:28:58 ++ 14:29:05 always good to get many eyes on it 14:29:07 +1 14:30:47 so that's it for this task 14:31:02 next topic then 14:31:15 #topic Skipping next week meeting? 14:31:56 since we don't have tasks for next week, i guess it's OK to skip it 14:32:26 anyone objecting? :) 14:32:37 nop 14:32:49 ++ 14:33:43 Nope. 14:33:59 ++ 14:34:15 cool, thanks, then let's move to the next topic 14:34:26 #topic Assign R-9 week tasks 14:34:43 there are 2 tasks, so not so many, 14:34:54 and i've assigned them to myself 14:35:09 * Generate a list of intermediary-released service deliverables that have not done a release in this cycle yet 14:35:16 * Send countdown email 14:35:27 Thanks elodilles ! 14:35:49 Thank you! 14:36:11 no problem 14:37:07 i think we can move on 14:37:27 ykarel added a stable support related question, 14:37:53 but i've already answered that directly on the patch 14:38:25 so the last, general topic: 14:38:32 #topic Open Discussion 14:38:58 anything that we missed? anything to share? anyone? 14:39:26 there's a project rename maintenance tentatively scheduled for a week from monday, to move the skyline repos into the openstack namespace 14:39:27 nothing here 14:39:35 great! 14:39:50 i'll give folks in here a heads up before we start, though it should be brief 14:40:03 Oh yay! 14:40:08 Next week is like the last skip before we enter the release tunnel 14:40:22 so enjoy the release meet skip! 14:40:23 fungi: thanks for the info & thanks in advance! 14:40:37 no problem 14:41:12 we'll probably also have a zuul restart some time in the next few days, but it should be a rolling restart with no downtime/impact 14:42:16 thanks fungi 14:42:21 ack 14:43:17 so one week rest and then we will have more and more tasks as the weeks passes, as ttx said :) 14:43:36 hope the renaming will not affect any pointers to the project 14:43:48 yepp 14:44:19 cool. if nothing else, then let's end the meeting 14:44:28 thanks elodilles ! 14:44:44 thanks everyone for joining && see you in 2 weeks! 14:44:51 #endmeeting