Friday, 2026-07-24

*** haleyb is now known as haleyb|out00:27
*** ykarel_ is now known as ykarel|away12:06
elodillesweekly meeting in ~30 mins13:30
elodillesreminder: ^^^ :)13:31
* fungi is around13:38
elodilles#startmeeting releaseteam14:00
opendevmeetMeeting started Fri Jul 24 14:00:24 2026 UTC and is due to finish in 60 minutes.  The chair is elodilles. 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
elodilleso/14:00
elodilles#link https://etherpad.opendev.org/p/hibiscus-relmgt-tracking14:00
fungiheyhey14:00
elodilleshi o/14:01
frickler\o14:01
elodilleswe are at line 22714:01
elodilleslet's start!14:01
elodilles#topic Review R-11 / R-10 task completion14:01
elodilles- Ensure that all new-release patches in requirements repository for the milestone-2 releases are merged. (all)14:01
elodilles#link https://review.opendev.org/q/project:openstack/requirements+branch:master+is:open+topic:new-release14:02
elodilleshmmm, we have one that is lingering there for more than a week O.o14:02
elodilleshttps://review.opendev.org/c/openstack/requirements/+/99752714:02
elodillesoslo.config14:02
elodillesokay, we need to ping oslo team about this ^^^14:03
elodillesi'm not sure if the gate job failure (openstacksdk-functional-devstack) is related to the release itself, but it more than suspicious to me14:04
elodillesi'll ping the team after the meeting14:04
fungii have a feeling openstacksdk-functional-devstack may have broken separately14:05
elodillesoh, is it?14:05
fungithough it does seem to be passing recently, so maybe it was a one-off14:05
fungior maybe oslo.config 10.6 is really breaking heat14:06
fungii guess it needs deeper investigation14:06
elodillesyes, some investigation is definitely needed here14:06
fungiyeah, seems like it failed the same way after a recheck too14:07
elodilles#action elod to ping Oslo team to check the broken openstacksdk-functional-devstack job on oslo.config's version bump patch14:07
elodillesfungi: yepp, that was what i saw too14:08
fungii've rechecked it again to get another data point for now14:08
elodilles+114:08
elodilleswe'll see14:08
elodillesthen let's move on14:08
elodilles- Propose convenience releases for 2025.1 Epoxy to ease the transition to Unmaintained and avoid rush and broken releases when the transition deadline is coming. (elod)14:08
elodilleshttps://review.opendev.org/q/topic:epoxy-stable14:09
elodillesa lot have been released already \o/14:09
elodillesi'll wait some time and abandon the leftovers14:10
elodilleswe still have time till the transition of 2025.1 Epoxy to Unmaintained14:10
elodilleslet's see week R-10's tasks list:14:11
elodilles- Generate a list of intermediary-released service deliverables that have not done a release in this cycle yet. (elod)14:11
elodilles    (elod) the following cwi deliverables haven't released in this cycle yet:14:11
elodilles    ironic-prometheus-exporter14:11
elodilles    ironic-python-agent-builder14:11
elodilles    ironic-ui14:11
elodilles    networking-baremetal14:11
elodillessomewhat the usual ^^^14:11
elodillesso the purpose of the task is originally to identify the deliverables and propose release model change14:12
elodillesto cycle-with-rc14:12
elodillesbut in the past we ended up with these that the patches got rejected14:13
elodillesby the team14:13
elodillesand actually the "weekly mail" was originally about this to highlight the patches14:14
elodilles(see: https://releases.openstack.org/reference/process.html#between-milestone-2-and-milestone-3 )14:14
elodillesbut I think maybe a simple heads-up mail to ironic team on ML would be enough14:15
elodillesso instead of the weekly mail, i'd rather send this14:16
elodilleshttps://etherpad.opendev.org/p/relmgmt-weekly-emails14:16
elodillesif no objection14:16
fungiseems fine to me, draft looks okay14:16
elodillescool14:17
elodillesthen i'll send the mail after the meeting14:18
elodillesnext topic then!14:18
elodilles#topic Assign R-8 week tasks14:18
elodilles1 single task and the weekly mail, so i've added my name to it14:19
elodilles(and maybe that 1 task is even less if the Indri schedule will be merged by that time o:))14:20
elodilles#topic Final approval of Indri schedule14:20
elodillesthe patch:14:20
elodilles#link https://review.opendev.org/c/openstack/releases/+/99680814:20
elodillesso there is a couple of things to mention here14:21
elodilleswe agreed to merge this by next week's Friday14:21
elodillesright?14:21
elodillesas I've sent a mail to ML to advertise this to folks14:21
elodilles#link https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack.org/thread/V772GUTDPIOIFUVR6SGX7Q33WTWCQXWF/14:22
fungiyes, a week from today14:22
elodillesyepp14:23
fungigouthamr had some feedback on the exact dates14:23
elodillesand we got some review comment from gouthamr 14:23
fungiand i agree it's never perfect regardless of when we set milestone dates et cetera14:23
elodillesyes, unfortunately14:23
elodillesi've commented my opinion there14:24
fungialso at least shifting the final release around has some additional risks, for example the openinfra marketing folks would prefer it not land on top of kubecon-na14:24
fungi(which it currently doesn't)14:24
fungier, eu not na14:24
elodillesfungi: good to know that +114:24
elodillesprobably Hibiscus-2 can move forward 1 week14:25
fungilooks like kubecon-eu is march 15-1814:25
elodilleshmmm, that is just before the release :/14:25
fungiyes, if we shifted it up by a week it would be a problem because of that14:26
fungiso right now it's sandwiched between kubecon and easter14:26
elodillestrue14:26
elodillesso again, maybe we can move Hibiscus-2 one week forward, but probably we should keep the release date14:27
elodillesokay, i'll mention this discussion on the comment, and hopefully we can decide there the way forward within a couple of days,14:30
fungii would be okay with that if there's a strong preference for it14:30
elodillesas we need to finalize this patch by next friday14:30
fungiyes14:30
elodillesokay, let's wait for further comments14:31
elodillesand move on for now14:32
elodilles#topic Review weekly countdown email14:32
elodilleswe've done this already in previous topic o:)14:32
elodillesso I'll send the agreed mail to ML to Ironic folks14:33
fungithanks!14:33
elodilles#topic Open Discussion14:33
fungigood that it's only their deliverables lagging, at least14:33
elodillesanything else to talk about?14:33
fungieasier to deal with one team than many14:33
elodillesfungi: yepp, sometimes there were others as well, but mostly some of the many ironic small deliverables that are forgotten14:34
fungiright14:35
fricklerwhat do we do with ttx and the DPL reset? IIUC either we propose a patch that drops him or we'll have a PTL election coming up14:35
fungiit's already taken care of14:36
fungia patch merged today making me the security liaison14:36
fungiand the dpl reset patch was then abandoned14:36
elodillesthanks fungi for adding your name as contact there o/14:36
elodillessounds good14:37
fricklerhmm, I don't understand, how this works, then, but however14:37
fungino worries, that liaison role doesn't really serve much of a purpose in our case since we don't have release deliverables of our own14:37
fungi#link https://review.opendev.org/c/openstack/governance/+/998472 Update security liaison for release team14:38
fungionce that landed, all current liaisons had objected to the reset change14:38
elodillesah, just wanted to copy the link, but you were faster fungi :)14:38
fungii also commented on the reset change pointing to that when i proposed it yesterday, just for clarity14:39
fricklerwell ttx is still listed as release liaison14:39
fricklerso formally this isn't correct IMO14:39
fungioh, hah i missed that14:39
fungiyeah, i guess i or another of us should take that one too14:40
fungithough the release liaison for the release team is even less necessary than the security liaison ;)14:40
fungii think technically all of us are release liaisons to ourselves14:40
elodillesfungi: it mostly means the DPL role in this case if i'm not mistaken14:41
fungiour case is somewhat special in that we're the only official project team which needs liaisons from other project teams, so the release liaison for the release team is sort of self-referential14:42
fungiit may be that the qualifying criteria from governance is that each liaison role needs at least one active volunteer to object14:43
fungirather than all the volunteers for the same role14:43
fungiand since there are two other release liaisons who objected, the requirement was fulfilled14:44
elodillesfungi: i still think that 'release liaison' for a team with DPL leadership type is more like a "list of people who distribute the PTL role"14:44
fungiyes, i agree14:44
elodillesso maybe we could ask for clarification from ttx when he'll be back, if he wants to be listed there in the next cycle as well14:45
fungibut that particular role exists because the release team needs project teams to have someone responsible for approving release requests and such14:45
frickleriiuc all involved persons need to -1, to avoid stale records for people who are no longer around14:45
fricklerbut I'm fine with delaying this until ttx is back14:46
fungi"All current liaisons are recording their -1 vote against the change to reset the leadership model. Once all liaisons have recorded -1 vote, the TC will not reset the DPL model and will consider continuing the DPL model for the next cycle as well."14:47
fungithat seems to match your understanding yes14:47
fungi#link https://governance.openstack.org/tc/reference/distributed-project-leadership.html#dpl-model-liaison-duration14:47
elodilles+114:47
elodillesthen everyone is on the same page o:)14:47
fungiso i agree the reset change probably shouldn't have been abandoned without removing ttx from the list of release team release liaisons14:48
elodilleslet's get back to this when ttx is here14:48
fungibut yes, it can wait, for sure14:48
fungithe tc doesn't seem concerned that we're leaderless14:48
fungii don't foresee us needing to switch to ptl model in time for the indri election cycle14:48
fungithis is now just a bookkeeping exercise14:49
elodillesfungi: neither do i14:49
elodillesokay, anything else?14:49
fungii didn't have anything else14:50
fungilooks like frickler noted some updates needed on the indri release schedule draft too14:50
elodilleshmmm, date format. I really just re-used the format we have since ages o:)14:52
elodillesbut I can update14:53
fungiif we're painting that bikeshed, i'm partial to iso-8601 date formatting14:53
elodilles:)14:53
elodillesthat's what we use in my country, so i can relate to that as well o:)14:54
fungiit's what all reasonable individuals (i.e. computer systems engineers) use in my country too ;)14:55
elodilles:]14:55
fricklerI wouldn't object to that format, either14:56
elodillesokay, will update the patch based on the comments :) let's end this now14:56
elodillesthanks both of you for being here o/14:56
fungithanks!14:56
elodilles#endmeeting14:56
opendevmeetMeeting ended Fri Jul 24 14:56:43 2026 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:56
opendevmeetMinutes:        https://meetings.opendev.org/meetings/releaseteam/2026/releaseteam.2026-07-24-14.00.html14:56
opendevmeetMinutes (text): https://meetings.opendev.org/meetings/releaseteam/2026/releaseteam.2026-07-24-14.00.txt14:56
opendevmeetLog:            https://meetings.opendev.org/meetings/releaseteam/2026/releaseteam.2026-07-24-14.00.log.html14:56
opendevreviewElod Illes proposed openstack/releases master: Proposed 2027.1 Indri release schedule  https://review.opendev.org/c/openstack/releases/+/99680815:29
opendevreviewElod Illes proposed openstack/releases master: Proposed 2027.1 Indri release schedule  https://review.opendev.org/c/openstack/releases/+/99680815:43
gouthamrreads like i jumped the gun on abandoning https://review.opendev.org/c/openstack/governance/+/99716718:32
gouthamrttx can be dropped from the liaisons list if you folks prefer.. thanks for flagging/discussing it18:33
fungiunless there's urgency from governance, i think we can wait to decide until he's home18:34
fungidocumented process aside, there's at least one volunteer for every required dpl liaison role so no need to worry about reverting to ptl model in time for the next election anyway18:34
fungi(and the release management liaison role for the release management team is, as we discussed, sort of nonsense anyway)18:35
gouthamryes18:36
gouthamragreed on all points, i'll document this on gerrit for transparency18:36
fungithanks for bveing flexible!18:36
*** gibi_ is now known as gibi18:40
gouthamrdid i hold up https://review.opendev.org/c/openstack/releases/+/996808 ? :D 18:50
gouthamri meant to get the PTG dates in the calendar, apart from the M-2 to M-3 time issue.. you folks deliberated the time issue, and elodilles explained the problems just fine18:50
gouthamrbut the PTG dates still don't show up in the table.. a minor concern compared to publishing the schedule18:51
gouthamrso i'll remove my objections :) 18:51
elodillesgouthamr: ah, you are right, let me add the PTG to the yaml as well o:)18:52
gouthamr\o/ ty elodilles 18:53
elodillesgouthamr: you didn't hold up, btw, we advertised the deadline as next Friday (31 July) :]18:54
gouthamrAH! 18:54
gouthamri famously have the problem of thinking i'm pbkac for all of openstack 18:55
fungiat least not this time!18:55
gouthamr:'D18:55
elodillesgouthamr: btw, thank you for reviewing the schedule!18:56
gouthamr++ you're welcome18:57
opendevreviewElod Illes proposed openstack/releases master: Proposed 2027.1 Indri release schedule  https://review.opendev.org/c/openstack/releases/+/99680819:03
elodillesthat will hopefully render the ptg on the schedule ^^^19:04
*** zseguin_ is now known as zseguin22:00

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