14:00:13 <elodilles> #startmeeting releaseteam
14:00:13 <opendevmeet> Meeting started Fri May 12 14:00:13 2023 UTC and is due to finish in 60 minutes.  The chair is elodilles. Information about MeetBot at http://wiki.debian.org/MeetBot.
14:00:13 <opendevmeet> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
14:00:13 <opendevmeet> The meeting name has been set to 'releaseteam'
14:00:20 <ttx> o/
14:00:23 <elodilles> Ping list: elodilles armstrong
14:00:24 <elodilles> o/
14:00:38 <elodilles> #link https://etherpad.opendev.org/p/bobcat-relmgt-tracking
14:01:07 <elodilles> we are @ L94
14:02:12 <elodilles> let's start!
14:02:17 <elodilles> #topic Review task completion
14:02:35 <elodilles> 1st task: 'Ensure that all trailing projects have been branched for the previous series (ttx) (armstrong)'
14:02:47 <elodilles> ttx: anything to report here?
14:03:06 <ttx> So the script needs to be adapted to work with 2023.1 style branches, but I ran a frankenversion of it
14:03:17 <elodilles> :-o
14:03:26 <elodilles> oh, nice...
14:03:28 <ttx> the outcome is that we ahve a number of deliverables that have not released yet for Antelope
14:03:48 <ttx> ansible-collection-kolla -- no releases yet... (full message at <https://matrix.org/_matrix/media/v3/download/matrix.org/yciuLNVeBWmpqhJaRZbjpBdD>)
14:04:00 <ttx> so branching them is a bit too early
14:04:48 <ttx> we should reach out and ask them for their plans?
14:05:15 <elodilles> ttx: note that your multi-line message does not appear on IRC
14:05:22 <ttx> ah oops
14:05:44 <ttx> ansible-collection-kolla, kayobe, kolla-ansible, kolla, openstack-ansible
14:05:45 <fungi> for those not on matrix, the full list was: ansible-collection-kolla, kayobe, kolla-ansible, kolla, openstack-ansible
14:05:56 <ttx> those deliverables have no release yet in Antelope 2023.1
14:06:11 <elodilles> anyway, what i see that the list is the same as our reminder mail from last week: https://lists.openstack.org/pipermail/openstack-discuss/2023-May/033536.html
14:06:14 <ttx> I'm still confused with what goes through and what does not
14:06:31 <ttx> ok so that is covered
14:06:47 <fungi> ttx: it goes through in a sense, but as a url to see the full multi-line message on matrix.org
14:06:49 <ttx> i think we can move on to next task :)
14:06:57 <elodilles> (except cinderlib that has been released and branched)
14:07:23 <elodilles> ttx: thanks for the update! we need to look at the trailing projects in the coming weeks :)
14:07:49 <elodilles> 2nd task: 'On Tuesday, force-approve xena-em patches without PTL+1 (ttx)'
14:08:03 <ttx> I approved the ones that did not ave -1s
14:08:17 <ttx> https://review.opendev.org/q/topic:xena-em+is:open
14:08:25 <ttx> we have a few left though
14:09:10 <elodilles> yes, i think heat can be processed, there was a late release, but now we have had some safety buffer time after the release :)
14:09:26 <ttx> the heat one I left out because there are a bunch of pending releases
14:09:55 <ttx> https://review.opendev.org/q/topic:xena-em+is:open
14:09:58 <elodilles> I'll ping OpenStackAnsible and Puppet Openstack teams (trailing projects, with special release metadata handling)
14:09:58 <ttx> oops
14:10:05 <ttx> https://review.opendev.org/c/openstack/releases/+/870575
14:10:09 <ttx> https://review.opendev.org/c/openstack/releases/+/870711
14:10:20 <ttx> should we approve those before tagging xena-em?
14:10:34 <elodilles> ttx: i think if we haven't got any response from those heat releases, we should abandon those
14:11:04 <ttx> and approve the xena-em patch instead? Works for me
14:11:12 <ttx> I'll do that
14:11:28 <elodilles> also, as i double check now the patches in the releases they are not really relevant changes
14:11:53 <elodilles> so i think: yes approve the transition patch instead and abandon the release patches
14:12:11 <ttx> done
14:12:19 <elodilles> \o/
14:12:19 <elodilles> thx
14:12:22 <ttx> that leaves two late exceptions
14:12:24 <elodilles> one step closer :)
14:12:31 <ttx> almost there!
14:13:11 <elodilles> so as i said, i'll ping them
14:13:30 <elodilles> and hopefully we can mark Xena as EM in the coming days
14:13:51 <elodilles> anything to add?
14:14:13 <ttx> no
14:14:20 <elodilles> cool
14:14:31 <elodilles> 3rd task: 'Propose autoreleases for cycle-with-intermediary libraries which did not release since the previous release. (elod) (armstrong)'
14:14:56 <elodilles> armstrong had some environment issue, so i've proposed the patches: https://review.opendev.org/q/topic:bobcat-milestone-1
14:15:28 <elodilles> some of them have been merged already
14:15:36 <ttx> I'll do a pass on them
14:15:38 <elodilles> some are waiting a 2nd +2
14:16:07 <elodilles> mostly oslo deliverables are without response (as hberaud was on vacation o:))
14:16:40 <ttx> that should get solved soon
14:17:09 <elodilles> should we wait for Monday and merge where we get PTL-Approved?
14:17:55 <ttx> let's wait for hberaud's review
14:18:05 <elodilles> ACK
14:18:55 <elodilles> 4th task: 'To catch if there are acl issues in newly created repositories, run tools/aclissues.py to detect potential leftovers in Gerrit ACLs (ttx)'
14:19:00 <ttx> the aclissues check reported two issues: one around ironic deliverables as they are using a non-standard ACL since https://opendev.org/openstack/project-config/commit/c319997bf732be20a54b73c30a12fcc94a184089
14:19:06 <ttx> the other around openstack/ovn-bgp-agent (recently added to neutron) that was fixed in https://review.opendev.org/c/openstack/project-config/+/882676
14:19:15 <ttx> so I would consider this task done
14:19:38 <elodilles> awesome, thanks! \o/
14:20:05 <elodilles> 5th task: 'Check on Antelope-inactive projects (patrole, os-win, sahara, monasca...) and see if they were removed by the TC (elod)'
14:20:36 <elodilles> - patrole is retired & removed: https://review.opendev.org/c/openstack/releases/+/880229
14:20:56 <elodilles> - os-win: deprecation is still discussed on ML
14:21:37 <elodilles> - sahara, monasca and vitrage got new PTLs appointed
14:22:11 <elodilles> so from our point of view now only os-win needs some decision
14:22:38 <elodilles> i suggested 'before Bobcat-1' to TC if i remember correctly,
14:22:45 <ttx> yes... and there is time between now and bobcat-2 to figure it out
14:23:07 <elodilles> but our documentation somewhere says 'before Milestone-2' :)
14:23:15 <elodilles> so yes, we still have some time
14:23:18 <fungi> the "membership deadline" on the schedule is at milestone 2, yes
14:23:35 <elodilles> fungi: that's it, yes, thanks!
14:23:47 <fungi> it's perhaps a somewhat confusing term
14:24:13 <fungi> but no need to bikeshed alternative wording right now
14:24:19 <elodilles> so we will see
14:24:19 <ttx> yeah, we could rename it
14:25:15 <elodilles> i'm open for new names, but i can't think of any better one currently :)
14:27:30 <elodilles> anyway, feel free to propose doc update if you figured out some new fancy name
14:28:04 <elodilles> 6th and final task: 'Check on progress over PTG tasks at https://etherpad.opendev.org/p/march2023-ptg-os-release (elod)'
14:28:22 <elodilles> "are we close to job timeout values for long running jobs at final release?"
14:28:22 <opendevreview> Merged openstack/releases master: [Glance] Bobcat milestone 1 release  https://review.opendev.org/c/openstack/releases/+/882974
14:28:25 <opendevreview> Merged openstack/releases master: Release glance-store for Bobcat-1 milestone  https://review.opendev.org/c/openstack/releases/+/882606
14:28:27 <opendevreview> Merged openstack/releases master: Release os-brick for Bobcat-1 milestone  https://review.opendev.org/c/openstack/releases/+/882580
14:28:36 <elodilles> * no, it seems we are well below the timeout values (gate jobs!): https://etherpad.opendev.org/p/release-job-timeouts
14:28:54 <elodilles> * tox-validate job timeout fix: https://review.opendev.org/c/openstack/releases/+/881229
14:29:07 <elodilles> this was for the check queue ^^^
14:29:25 <elodilles> so i think this topic is covered
14:29:50 <ttx> agreed
14:30:11 <elodilles> i haven't proposed yet though the timing update for the process
14:31:12 <elodilles> i'm planning to do it next week
14:31:30 <elodilles> i forgot about that, sorry :/
14:32:16 <ttx> it's ok, no urgency!
14:32:25 <elodilles> o:)
14:32:44 <elodilles> anything else that we should address from PTG discussion?
14:33:47 <ttx> not from me
14:34:36 <elodilles> i also see now the duplicated release notes issue, i'll look into that next week and we will see
14:35:13 <elodilles> anyway, that was about the tasks, let's move on to the next topic
14:35:28 <elodilles> #topic 'Assign R-20 and R-19 tasks'
14:35:31 <elodilles> done
14:36:13 <elodilles> as 'Review any remaining milestone-1 exceptions' is for everyone i think
14:36:51 <elodilles> and the other task was again about trailing projects, for which i added my name
14:37:07 <ttx> thanks!
14:37:11 <elodilles> np
14:37:12 <elodilles> #topic Review countdown email
14:37:25 <elodilles> #link https://etherpad.opendev.org/p/relmgmt-weekly-emails
14:37:43 <ttx> looks good to me, once you remove the strikeout text
14:38:06 <elodilles> done
14:38:22 <elodilles> will send it later today then. thanks for the review!
14:38:46 <elodilles> #topic Open Discussion
14:39:04 <ttx> nothing from me... I'll be a lot less available starting Thursday
14:39:14 <ttx> and basically until the summit :)
14:39:33 <elodilles> ack, thanks for the info :)
14:40:26 <elodilles> also worth to note that #openstack-release channel will be deserted on Thursday and Friday as all 3 of us will be 'out of office' / PTO
14:40:33 <fungi> starlingx is apparently having a hard time with projects eol'ing stable/train
14:41:08 <elodilles> fungi: :-o what is their problem with the EOL'ing?
14:41:29 <fungi> there's a ml, thread, just a sec...
14:41:44 <elodilles> oh, i missed that :S
14:42:00 <fungi> #link https://lists.openstack.org/pipermail/openstack-discuss/2023-May/033637.html "Train EOL"
14:43:09 <elodilles> thanks
14:43:38 <elodilles> as i read they have problem with neutron and heat projects' EOL'd train branches disappeared for them
14:43:59 <elodilles> thanks for calling my attention to it, i'll read & reply on the ML
14:45:52 <fungi> hopefully JayF and i have covered the main points in our replies already
14:46:24 <elodilles> fungi: cool, thanks :)
14:46:37 <elodilles> okay, anything else before we close the meeting?
14:47:58 <elodilles> looks not
14:48:07 <elodilles> then thanks for participating!
14:48:13 <elodilles> #endmeeting