Friday, 2025-11-14

opendevreviewDmitriy Rabotyagov proposed openstack/releases master: Release OpenStack-Ansible Epoxy  https://review.opendev.org/c/openstack/releases/+/96716909:21
opendevreviewDmitriy Rabotyagov proposed openstack/releases master: Release OpenStack-Ansible Dalmatian  https://review.opendev.org/c/openstack/releases/+/96717009:23
noonedeadpunkhey folks. I was wondering on what to do with https://review.opendev.org/c/openstack/releases/+/96629809:24
noonedeadpunkshould we instead just do a normal release of Caracal?09:24
elodillesnoonedeadpunk: it wouldn't make any difference. the issue is that 2024.1 Caracal is marked as Unmaintained already. I haven't got there yet to add the exemption case to cycle-trailing typed deliverables in the validator09:53
elodillesthe workaround we did previously a couple of times was to simply mark Caracal as active temporarily09:54
noonedeadpunkwhich kinda sucks, as this is a patch for roles. and then we need to merge some other change and propose for integrated repo10:20
noonedeadpunkbut got it...10:20
opendevreviewBartosz Bezak proposed openstack/releases master: EOL Kolla Antelope  https://review.opendev.org/c/openstack/releases/+/96721713:51
ttx#startmeeting releaseteam14:00
opendevmeetMeeting started Fri Nov 14 14:00:05 2025 UTC and is due to finish in 60 minutes.  The chair is ttx. Information about MeetBot at http://wiki.debian.org/MeetBot.14:00
opendevmeetUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:00
opendevmeetThe meeting name has been set to 'releaseteam'14:00
ttxPing list: release-team elod14:00
ttxAgenda at https://etherpad.opendev.org/p/gazpacho-relmgt-tracking#L8614:00
elodilleso/14:01
ttxHi!14:01
ttx#topic Review R-20 task completion14:01
ttx- Ensure that all trailing projects have been branched for the previous series. (elod)14:01
elodillesso, i've run the script to check the state14:02
elodillesand kayobe and OSA were the projects that haven't released yet14:02
elodillesi did not propose release patches but pinged the PTLs and they confirmed that they are working on the releases14:03
ttxshould we add a task to cheeck on them in a coming week?14:03
elodillesyes, maybe that's OK14:04
ttxok task added14:05
ttx- Propose autoreleases for cycle-with-intermediary libraries which did not release since the previous release. (elod)14:05
elodilleswe have a task on R-17 about the final release patches, but probably would be better to have the RC1 and stable/2025.1 branch cuts prior that14:05
elodilles#link https://review.opendev.org/q/topic:gazpacho-milestone-114:05
elodillesthe release patches ^^^14:05
elodillesaround 1/3rd have landed already14:06
elodilleswe have 2 requests to wait for some patches to merge14:06
ttxShould we post a message on them saying we'll approve them Monday if nobody says -114:06
elodillesquestion is whether we want to force-release the rest, or should we just abandon them14:06
ttxoh right, milestone-114:07
ttxprobably simpler to drop them14:07
ttxteach them a lesson!14:07
elodilles:)14:07
ttxLet's abandon them with "no feedback from release liaison, abandoned"14:08
elodillesmost of the release patches don't have serious content, to be honest14:08
ttx(on Monday)14:08
elodillesthough we have already caught some breaking release: oslo.service made heat code to break o:)14:08
ttxI can add a task for that14:08
elodilles+114:09
ttx- Catch if there are acl issues in newly created repositories (ttx)14:10
ttxno issues found14:10
ttx- Send weekly email (ttx)14:10
elodilles\o/14:10
ttxto be done shortly14:10
fungiwe haven't been creating that many new repos in openstack lately14:10
ttx#topic Assign R-19 and R-17 week tasks14:11
ttxI think they are all assigned14:11
ttx#topic Review weekly countdown email14:11
ttx#link https://etherpad.opendev.org/p/relmgmt-weekly-emails14:11
* elodilles clicks14:11
elodillesLGTM14:13
ttxWill send when meeting ends14:13
ttx#topic Open Discussion14:13
ttxAnything to cover?14:14
ttxgoing once...14:15
elodillesmaybe worth to mention the cycle-trailing projects' transitioning issue: OSA is about to move its stable/2024.1 to Unmaintained14:15
ttxhow is that an issue?14:16
elodillesyepp, validator does not allow that to happen14:16
elodillesand last cycles we did the workaround to mark the Unmaintained/EOL'd series as 'open' temporarily14:16
elodillesbut i promised to adapt the code of the validator14:16
elodillesjust haven't proposed a solution yet14:17
ttxwe can do the workaround again, I guess...14:17
elodillesthe problem is that makes it uncomfortable to OSA is that it has to branch OSA-roles first,14:17
fungiwhat's missing for validation there?14:17
elodillesthen do another release of OSA project itself14:18
fungiah, ordering of repos in the transition i guess14:18
elodillesfungi: not missing, but the validator does not allow to release anything beyond 'stable'14:18
fungioh it's that they need a tag on unmaintained?14:18
fungithat's definitely a little weird14:19
elodillesfungi: cycle-trailing projects do their releases after everything else got released, this is their request, which completely makes sense,14:19
elodillesand the same applies when we move to Um/EOL14:19
elodillesrelmgt granted the exception to them, so that they can prepare their final releases AFTER everything else have branched14:20
fungimaybe i'm misunderstanding. they want to tag releases on unmaintained/2024.1, or they still have stable/2024.1 and want to release on that after the eom deadline?14:21
elodillesbut we don't want to keep e.g. 2024.1 Caracal to linger weeks as 'maintained' while it is already unmaintained14:21
elodillesfungi: they still have stable/2024.114:21
fungiokay, that makes more sense, thanks14:21
elodillesthis is how we did that in the last couple of cycles14:21
elodillesanyway, it's just a heads up, that i'm planning to propose a patch for that,14:22
fungiso the exception would be for releasing past the deadline, not releasing from an unmaintained/* branch14:22
elodillesand if we running out of time, then we have to do the workaround :/14:22
elodillesfungi: yes: to allow cycle-trailing modelled projects to release in Unmaintained state from their stable branch14:23
ttxok... anything else?14:23
elodillesttx: nothing else from me14:23
fungiand policy-wise it seems fine that cycle-trailing projects could have a later deadline for eom transition too, the release tooling just doesn't support that yet14:23
elodillesfungi: exactly14:24
ttxok then...14:24
ttxhave a great weekend!14:24
elodillessame to you o/14:24
fungiyou too!14:24
ttx#endmeeting14:24
opendevmeetMeeting ended Fri Nov 14 14:24:34 2025 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:24
opendevmeetMinutes:        https://meetings.opendev.org/meetings/releaseteam/2025/releaseteam.2025-11-14-14.00.html14:24
opendevmeetMinutes (text): https://meetings.opendev.org/meetings/releaseteam/2025/releaseteam.2025-11-14-14.00.txt14:24
opendevmeetLog:            https://meetings.opendev.org/meetings/releaseteam/2025/releaseteam.2025-11-14-14.00.log.html14:24
opendevreviewPierre Riteau proposed openstack/releases master: Kayobe 2025.2 Flamingo RC1 and stable branch cut  https://review.opendev.org/c/openstack/releases/+/96722416:50
opendevreviewMerged openstack/releases master: Add stephenfin as release liaison for sdk deliveries  https://review.opendev.org/c/openstack/releases/+/96641516:52
mnasiadkaelodilles: 967224 waiting :)17:04
*** tmazur_ is now known as tmazur21:27

Generated by irclog2html.py 4.0.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!