13:02:24 <elodilles> #startmeeting releaseteam
13:02:24 <opendevmeet> Meeting started Fri Aug 30 13:02:24 2024 UTC and is due to finish in 60 minutes.  The chair is elodilles. Information about MeetBot at http://wiki.debian.org/MeetBot.
13:02:24 <opendevmeet> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
13:02:24 <opendevmeet> The meeting name has been set to 'releaseteam'
13:02:36 <elodilles> Ping list: release-team elod
13:02:44 <elodilles> #link https://etherpad.opendev.org/p/dalmatian-relmgt-tracking
13:03:10 <elodilles> we are down at line 328
13:08:56 <elodilles> i'm feeling a bit alone :( but let's just walk through the agenda, and people can read the logs later.
13:09:08 <elodilles> #topic Review task completion
13:09:10 <armstrong> Hello
13:09:16 <elodilles> hi armstrong o/
13:09:35 <elodilles> 1st task was: 'Process any remaining library freeze exception (all)'
13:09:50 <elodilles> #link https://review.opendev.org/q/topic:dalmatian-final-non-client-libs+is:open
13:11:12 <elodilles> as you can see we still have 3 open patches, that should be merged as soon as possible
13:11:46 <armstrong> Ok I will look at them soon
13:11:48 <frickler> o/
13:13:38 <frickler> I'm not sure about the kuryr release, but maybe we can just release these three, don't think it should hurt much
13:14:34 <armstrong> The patches don’t yet have PTL approval ?
13:15:04 <elodilles> yeah, i just realised that i forgot to answer Artem on openstacksdk patch, now i've answered and +2'd the patch. we could release that, yepp.
13:15:43 <frickler> usually we would override ptl approval after having waited so long
13:16:13 <elodilles> frickler: yepp
13:16:45 <elodilles> about kuryr: gmann commented that Zun team is responsible now, but as you said, since we are over the deadline, let's merge and release that, too
13:17:40 <frickler> the handover isn't official yet, but one can assume that the intention is to keep doing releases
13:19:05 <elodilles> ACK
13:19:48 <elodilles> i've +2'd all 3 patches now, frickler would you mind reviewing them and +W them if you think they are OK?
13:20:33 <elodilles> (could happen after the meeting if you have time)
13:21:47 <frickler> will do
13:21:57 <elodilles> thx!
13:22:06 <elodilles> let's move on then
13:22:09 <elodilles> 2nd task was:
13:22:17 <elodilles> 'Propose autoreleases for cycle-with-intermediary client libraries. (frickler)'
13:22:26 <elodilles> #link https://review.opendev.org/q/topic:dalmatian-milestone-3
13:22:49 <elodilles> half of them have merged already
13:23:03 <frickler> elodilles did these, thx for that
13:23:09 <elodilles> the rest should be merged now, as the deadline have passed
13:23:38 <elodilles> yepp, no problem, had some time on monday, so took over the task o:)
13:24:20 <frickler> so we're going to override ptls for these, too, I assume?
13:24:37 <frickler> over do some more pings and give them until monday?
13:24:41 <elodilles> i'll continue reviewing the generated patches after the meeting, and either today, or early next week we should merge all the release patches if they are OK
13:25:16 <elodilles> frickler: yepp, PTL-Approved+1 will be necessary, so let's override them
13:25:58 <elodilles> we should have ping teams already as the deadline was Thursday
13:26:09 <frickler> ok, I'll look at that and also add those to the "name-and-shame" list
13:26:10 <elodilles> so let's just override them for now :/
13:26:22 <elodilles> thx again o/
13:26:49 <elodilles> 3rd task was:
13:26:58 <elodilles> 'Evaluate any non-client libraries that did not have any change merged over the cycle to see if it is time to transition them to the independent release model if applicable. (elod)'
13:27:24 <elodilles> i did a quick check, and actually found only (kuryr and) client libs:
13:27:41 <elodilles> python-adjutantclient,     python-venusclient,     python-watcherclient
13:28:19 <frickler> watcher is going to be leaderless, so that was maybe to be expected
13:28:36 <frickler> the others are also not known to be super active
13:29:06 <elodilles> yeah, maybe these will be the next retired projects :S
13:29:25 <elodilles> so i'll propose release patches for these three, but won't initiate model change as they are tightly coupled with their service deliverables afaik
13:29:43 <frickler> +1
13:29:57 <elodilles> at least their gate were passing recently :X
13:30:11 <elodilles> move on then
13:30:15 <elodilles> 4th task:
13:30:27 <elodilles> 'List cycle-with-intermediary deliverables that have not been released yet and send a separate email targeted to teams with such unreleased deliverables to remind them that they need to release before $rc1-deadline (ttx)'
13:31:15 <frickler> ttx wanted to do that last Friday, but I'm not sure whether there were any such deliverables
13:31:36 * elodilles is quickly looking at openstack-discuss
13:31:56 <frickler> ah, found it https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack.org/message/OY4F6A3UHNLAOJ74A2C6CGPNWS2LQBTJ/
13:32:03 <frickler> swift + ironic
13:32:27 <elodilles> yepp, that's it
13:32:36 <elodilles> #link https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack.org/message/OY4F6A3UHNLAOJ74A2C6CGPNWS2LQBTJ/
13:32:53 <elodilles> and i remember i've seen ironic releases
13:33:15 <frickler> yes, just need to check whether they did all of them
13:33:29 <elodilles> so swift is the last one that needs a release
13:33:38 <frickler> and timburke also missed the PTL candidacy, so doing another ping here ;-D
13:34:43 <elodilles> all ironic deliverables have a release, so we should be covered :]
13:35:14 <frickler> ack
13:35:39 <elodilles> we will have another checkpoint afair, so let's move on then :)
13:35:58 <elodilles> 5th task was:
13:36:02 <elodilles> 'On Friday, remind the requirements team to freeze changes to openstack/requirements by applying -2 to all open patches. Ensure that reviewers do not approve changes created by the proposal bot, but do approve changes for new OpenStack deliverable releases. (frickler)'
13:36:29 <frickler> left a note in the reqs channel this morning. also added -2 to all relevant patches
13:36:34 <elodilles> i've seen you did that on #openstack-requirements :)
13:37:05 <elodilles> on the other hand all new-release patches should be merged ASAP :S
13:37:20 <elodilles> maybe we could have a quick check there
13:37:39 <frickler> yes, some of them were failing CI. the one for osc even was abandoned
13:37:58 <elodilles> #link https://review.opendev.org/q/project:openstack/requirements+topic:new-release+branch:master+is:open
13:38:49 <elodilles> frickler: osc? you mean the released version couldn't be used? :-o
13:39:47 <frickler> yes, they broke some column naming and some quota commands in certain scenarios
13:40:07 <elodilles> that sounds like we need a new osc release then :S
13:40:32 <elodilles> with a RFE (Requirements Freeze Exception) :S
13:41:19 <frickler> yes
13:41:44 <frickler> well ... does the RFE hold for bugfix releases?
13:42:09 <frickler> also oslo.policy is still waiting for fixed in horizon and maybe other projects https://review.opendev.org/c/openstack/requirements/+/925464
13:42:30 <elodilles> yes, as RFE is not FFE (feature freeze exception) and we need to bump the upper constraints when it gets released
13:43:33 <frickler> heatclient seems to have dropped py3.8 support so that patch needs manual amending, I'll do that in a bit https://review.opendev.org/c/openstack/requirements/+/927456
13:43:51 <elodilles> let's hope then that oslo.policy won't be this cycle's library that causes last minute churns :S fingers crossed
13:44:22 <elodilles> thanks for updating heatclient
13:45:24 <frickler> well gmann was pretty optimistic when I check with him two weeks ago ;)
13:45:37 <elodilles> #info osc and oslo.policy library releases had failed cross-check jobs, so release team needs to keep an eye on them to sort out the problems as soon as possible
13:45:50 <elodilles> ^^^
13:46:01 <elodilles> that's good then :)
13:46:58 <elodilles> OK, that were all the tasks for this week
13:47:12 <elodilles> let's move on then to the next topic!
13:47:22 <elodilles> #topic Assign R-4 week tasks
13:47:52 <elodilles> ttx will travel all week, and might be back in time for the meeting,
13:48:22 <elodilles> so i'll chair the meeting then, just to be sure we'll have one :)
13:49:22 <frickler> is there a script for the branch proposal patches? (I assume yes, but want to be sure before taking this task)
13:49:25 <elodilles> i've added my name to the tasks, but feel free to hijack any if you'll have time
13:49:34 <frickler> although I think it is the same as earlier?
13:49:43 <elodilles> frickler: as far as i remember, there is
13:50:21 <elodilles> but feel free to take it, and if you have any issue just ping me and either we check it together or i can do it o:)
13:50:31 <frickler> ok
13:51:00 <elodilles> frickler: 4th task in the R-4 week tasks in the process page: https://releases.openstack.org/reference/process.html#r-4-week
13:51:19 <frickler> yes, already took it
13:51:25 <elodilles> cool, thanks o/
13:51:46 <elodilles> #topic Review countdown email for week R-4
13:51:55 <elodilles> #link https://etherpad.opendev.org/p/relmgmt-weekly-emails
13:51:59 <elodilles> please review ^^^
13:53:55 <frickler> rc1 on friday the 13th, nice ;)
13:54:00 <frickler> lgtm overall
13:54:02 <elodilles> :D
13:54:58 <opendevreview> Merged openstack/releases master: Release final kuryr for 2024.2 (Dalmatian)  https://review.opendev.org/c/openstack/releases/+/926761
13:55:21 <elodilles> yeah, to be honest, i like better the Thursday deadlines, even for RC1 and final RCs, but ttx usually argues that these can be Fridays as we usually talk about 'week of XY' for these o:)
13:55:45 <elodilles> in the past i advertised Thursdays as deadlines for these RCs as well o:)
13:56:35 <frickler> in general I agree, but this one is cool
13:56:58 <elodilles> (had to fix the dates in the mail proposal as well as at first i added the Thursday deadlines this time as well, but it came into my mind that ttx wrote Fridays in his mail last week o:))
13:57:16 <elodilles> yeah, it's not a big deal anyway o:)
13:57:23 <frickler> ah, ok
13:58:17 <elodilles> good-good. so if the mail looks OK to you then i'll send it after the meeting later today
13:58:25 <frickler> ack
13:58:39 <elodilles> #topic Open Discussion
13:58:59 <elodilles> we have 1 minute to discuss any other topic if anyone has one :)
13:59:21 <elodilles> (i don't have any)
14:00:58 <elodilles> looks not, so let's end the meeting! thanks armstrong and frickler for participating!
14:01:01 <elodilles> #endmeeting