14:00:23 #startmeeting releaseteam 14:00:23 Meeting started Fri Mar 4 14:00:23 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:23 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:00:23 The meeting name has been set to 'releaseteam' 14:00:33 Ping list: hberaud ttx armstrong damani 14:00:37 o/ 14:01:10 #link https://etherpad.opendev.org/p/yoga-relmgt-tracking 14:01:39 we are way down @ line 313 14:01:45 o/ 14:02:20 o/ 14:03:47 sorry, let's start :] 14:04:04 #topic Review task completion 14:04:23 1st task: "Process any remaining client library freeze exception." 14:04:31 well, there were none, 14:04:59 though on the yoga stable branch creating patch for ironic i got a response, 14:05:14 that they are planning to release ironic-lib and sushy: https://review.opendev.org/c/openstack/releases/+/831277/1#message-a8e40b21499c81074ac148fd449b3d25ad7145ee 14:06:02 i commented that they need RFE for that, but best is to avoid 14:07:11 ++ 14:07:40 though i haven't got reply so far 14:08:42 the deadline has passed right? 14:08:51 armstrong: yes 14:09:07 2nd task: "Freeze all cycle-based library releases except for release-critical bugs." 14:09:50 only non-client libraries remained: http://lists.openstack.org/pipermail/openstack-discuss/2022-March/027481.html 14:09:56 I'd say that's related :) 14:10:36 ttx: how do you mean? 14:11:50 it's best to avoid releasing ironic-lib and sushy since we freeze libs 14:12:44 oh, i see, yes, that's right 14:14:29 so actually kuryr and keystoneauth should have been released in R-6 14:15:13 that's why I wrote the RFE mail for them, 14:15:36 also added oslo.context as we have issues with that deliverable as well :/ 14:16:20 so these 3 needs requirements freeze exceptions 14:17:11 kuryr is released already, but keystoneauth is not, but i guess we should force-approve its release patch 14:17:52 ok 14:18:04 regarding oslo.context: 14:18:44 if i'm not mistaken the last breakage was fixed recently, so i've started a 'recheck' there, and we will see 14:19:20 i'll check with requirements team these things 14:19:53 any question or comment for this? 14:20:07 nope 14:20:11 ++ 14:20:16 thanks 14:20:37 3rd task: "Propose stable/yoga branch creation for all client and non-client libraries that had not requested it at freeze time." 14:20:51 patches: https://review.opendev.org/q/topic:yoga-stable-branches 14:21:13 more than half have merged, 14:21:44 since we reached the deadline i'll force-merge the rest after the meeting 14:22:06 ++ 14:22:14 +1 14:22:24 though i'd appreciate reviews on them before i merge them o:) 14:23:17 4th task: "List cycle-with-intermediary deliverables that have not been refreshed in the last 2 months." 14:23:35 mail was sent to ML: http://lists.openstack.org/pipermail/openstack-discuss/2022-March/027495.html 14:24:00 i've got response from QA and patrole is released 14:25:25 but no response for tempest and python-openstackclient 14:27:04 were there changes? 14:27:19 for python-openstackclient there were quite many 14:27:31 but maybe it is the same as with openstacksdk 14:28:12 for openstacksdk they had lots of unreleased changes on master (after the last released yoga version), 14:28:49 but thay cannot release them as they have issues 14:29:08 so they decided not to release those for yoga 14:29:12 hmm ok 14:29:24 i suspect that could be the case with python-openstackclient as well, 14:29:33 but haven't got any response yet 14:31:27 anyway, I'll ping the sdk team on IRC maybe 14:32:05 regarding tempest: do we need it now, too? I was a bit unsure 14:32:38 we don;t need it as much, it's a bit of a corner case 14:32:45 Usually gmann knows when to release it 14:33:10 it was last time released in November, 14:33:37 so i guess it would be good to release 14:33:52 anyway, i'll ping gmann :) 14:34:06 next task then 14:34:30 well, next topic, as there are no more tasks for now 14:34:46 #topic Assign R-3 week tasks 14:35:13 actually, i've added my name on the tasks and I see armstrong also volunteered :) 14:35:23 yes :) 14:35:31 so we are OK with this :) 14:35:33 thanks! 14:35:40 perfect :) 14:35:49 #topic Review countdown email contents 14:36:08 #link https://etherpad.opendev.org/p/relmgmt-weekly-emails 14:36:15 please review ^^^ 14:37:45 looks good, just added a mention since people were quite good at release highlights already 14:38:31 yepp, thanks, last section seemed a bit off to me as highlights were proposed already :) 14:38:35 LGTM! 14:38:44 thanks! 14:38:48 do we already have a name for the Z series ? 14:38:59 zed 14:39:10 armstrong: as fungi says ^^^ 14:39:44 OK thanks @fungi 14:40:13 let's move to the last topic 14:40:17 #topic Open Discussion 14:40:38 'PTG participation' 14:40:46 that's a good topic :) 14:40:51 yeah I was wondering if you discussed it while i was unavailable 14:41:05 ttx: not yet 14:41:15 There is still time to apply 14:41:25 i saw the mail but haven't apply yet 14:41:31 We could just place a one-hour meeting on our regular meeting slot 14:41:49 so that we talk more directly to each other and potentially recruit 14:41:54 ttx: 1 hr looks OK to me 14:42:13 14UTC on Friday 14:42:24 that could also work for me 14:42:30 elodilles: maybe reply to the survey and fill the ethercalc? 14:42:46 ttx: yepp, i will do that! 14:43:06 see "April 2022 Team Signup" email 14:43:18 ++ 14:43:23 I don;t think we need more than one hour 14:43:37 we can always go overtime in some other room 14:43:48 yepp, we usually fit in the 1 hour timeslot 14:44:22 ttx: and that we can do as well :) 14:44:39 i'll sign up the team after the meeting 14:45:12 any other topic for now? 14:46:43 Nothing from me 14:47:12 nope 14:47:12 Marios Andreou proposed openstack/releases master: Release final TripleO stable/ussuri https://review.opendev.org/c/openstack/releases/+/820244 14:47:51 I'll be mostly unavailable next week 14:47:51 okay, thanks everyone for participating! 14:47:56 thanks 14:48:02 #endmeeting