Friday, 2026-09-04

*** sfinucan is now known as stephenfin10:55
elodillesreminder: weekly meeting will start at the top of the hour13:35
opendevreviewElod Illes proposed openstack/releases master: [nova] Create 2026.2 branch for client and non-client libs  https://review.opendev.org/c/openstack/releases/+/100331113:58
opendevreviewMerged openstack/releases master: [freezer] Create 2026.2 branch for client and non-client libs  https://review.opendev.org/c/openstack/releases/+/100332713:59
opendevreviewMerged openstack/releases master: [swift] Create 2026.2 branch for client and non-client libs  https://review.opendev.org/c/openstack/releases/+/100333413:59
opendevreviewMerged openstack/releases master: [zaqar] Create 2026.2 branch for client and non-client libs  https://review.opendev.org/c/openstack/releases/+/100332113:59
opendevreviewMerged openstack/releases master: [trove] Create 2026.2 branch for client and non-client libs  https://review.opendev.org/c/openstack/releases/+/100332013:59
ttxo/14:00
ttxI have ~30minutes for the meeting before I need to run to the airport!14:01
elodilles#startmeeting releaseteam14:01
opendevmeetMeeting started Fri Sep  4 14:01:14 2026 UTC and is due to finish in 60 minutes.  The chair is elodilles. Information about MeetBot at http://wiki.debian.org/MeetBot.14:01
opendevmeetUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:01
opendevmeetThe meeting name has been set to 'releaseteam'14:01
elodillesPing list: release-team14:01
ttxohai14:01
elodilleso/14:01
opendevreviewMerged openstack/releases master: [magnum] Create 2026.2 branch for client and non-client libs  https://review.opendev.org/c/openstack/releases/+/100332614:01
fungiahoy!14:01
elodillesttx: oh, i see, i'll try to be fast, but i can't promise we'll be finished in 30 mins :S14:01
elodilles(as far as i know myself...)14:02
elodilleslet's start then with the agenda14:02
opendevreviewMerged openstack/releases master: [barbican] Create 2026.2 branch for client and non-client libs  https://review.opendev.org/c/openstack/releases/+/100333514:02
elodillesfirst of all14:02
elodilles#link https://etherpad.opendev.org/p/hibiscus-relmgt-tracking14:02
elodilleswe are way down at line 33514:02
elodilles#topic Review task completion14:03
elodilles- Process any remaining client library freeze exception. (all)14:03
elodilleshttps://review.opendev.org/q/topic:hibiscus-milestone-3+is:open14:03
fungiempty!14:03
elodilles\o/14:03
elodillesmove on then14:03
ttxwoohoo14:03
elodilles- Engage with the Tacker team on the opportunity to turn tosca-parser into a cycle-independent deliverable, following low activity in 2026.1 Gazpacho and 2026.2 Hibiscus (elod)14:03
elodillesso, python-tackerclient is force released, as we discussed14:04
elodillesand i've proposed this patch for tosca-parser:14:04
opendevreviewMerged openstack/releases master: [masakari] Create 2026.2 branch for client and non-client libs  https://review.opendev.org/c/openstack/releases/+/100333314:04
elodilleshttps://review.opendev.org/c/openstack/releases/+/100375414:04
elodillesand pinged the team on IRC14:05
elodillesbut no reply yet :(14:05
ttxI don't think we should force it without an answer14:05
fungii don't expect a rapid response14:05
elodillesi've pinged them 26 hrs ago, so not that far away unfortunately14:05
fungibased on how quickly they respond to queries from the vmt14:06
fungiwe could merge it next week right?14:06
ttxIf they don;t respond in a few days should we just release it for this round, and flag team for removal next cycle?14:06
fungiwfm14:06
elodillesshould we force release instead what we have now, and abandon the model change?14:06
ttxelodilles: yes, but let's give it a few days14:06
elodillesttx: ACK, let's do that14:06
fungiand repropose the model change for indri in that case14:07
ttxgiving them a chance to respond :)14:07
ttxright14:07
fungior i guess 1003754 could be revised to do it for indri in order to retain discussion history14:07
elodilles#action force release 'tosca-parser' if the team doesn't respond in the next couple of days14:07
elodillesfungi: good idea14:07
elodilleswill do that14:07
elodilles(btw, note, that i'll be also mostly off next week as I'm flying to Shanghai to the Summit too tomorrow, if everything goes well)14:08
fungii'll be around14:08
fungias in not travelling so can pick up emergency overflow here14:09
elodillesoh, cool, then we all will be there \o/14:09
opendevreviewMerged openstack/releases master: [tacker] Create 2026.2 branch for client and non-client libs  https://review.opendev.org/c/openstack/releases/+/100334014:09
elodillesah, okay, misunderstood :)14:09
fungino worries14:09
elodillesthanks then fungi :)14:09
elodilles- Ensure that all new-release patches in requirements repository for the client library releases are merged. (all)14:10
elodilleshttps://review.opendev.org/q/project:openstack/requirements+branch:master+is:open+topic:new-release14:10
fungiempty! (again!)14:10
elodillesthis is empty, too \o/14:10
fungiwe're on a roll here14:10
elodillesyepp :]14:10
elodilles- Early in the week, email openstack-discuss list to remind PTLs that cycle-highlights are due this week so that they can be included in release marketing preparations. (fungi)14:10
elodilleshttps://lists.openstack.org/archives/list/openstack-discuss@lists.openstack.org/thread/7DGK34RP2YWUKZDZBFCVVYWNYSBJ5P3O/14:10
elodillesthanks fungi o/14:11
elodillesi already reviewed a couple of cycle highlights14:11
fungiyeah, they've been coming in14:11
elodillesdidn't do single+2, so they need a 2nd review, though14:11
elodilles- Freeze all cycle-based library releases except for release-critical bugs. Independently-released libraries may still be released, but constraint or requirement changes will be held until after the freeze period. (all)14:12
elodillesthis was more like a guideline14:12
elodillesand unfortunately we got new library releases :/14:12
elodillesnevertheless, we are mostly good, though14:13
fungii'll apply extra scrutiny to release requests, though expect they're going to be security fixes14:13
elodillesand afair there might be still some arriving :/14:13
elodillesfungi: thanks in advance14:13
fungithankfully it's mostly cycle-with-rc projects that get the bulk of advisories14:13
elodilles:S14:14
elodillessad to hear that 'bulk of advisories' but good that cwr projects, so at least they have some time...14:14
elodilles- Propose stable/$series branch creation for all client and non-client libraries that had not requested it at freeze time. (fungi)14:15
elodilles#link https://review.opendev.org/q/topic:hibiscus-stable-branches14:15
fungiall but 4 have merged14:15
elodilles~half of them got responses and we were able to merge them14:15
elodillesand I've force merged a couple before the meeting14:16
elodillesand yepp, we have some with either a question on them, and/or some merged content, that might be needed for hibiscus (i.e. needs a release), but those need to be negotiated either with their teams or ourselves14:17
elodillesi suggest to move on now with the agenda and get back to this later14:18
fungiagreed14:18
elodillesso that we might be able to cover most of the topics14:18
elodilles- List cycle-with-intermediary deliverables that have not been refreshed in the last 2 months (ttx)14:19
elodillestempest (last released 46.3.0 on May 12)14:19
elodillesanything to add ttx ^^^?14:19
ttxI was assuming tempest might get released later 14:20
ttxmaybe worth raising to QA team?14:20
elodilleslet me check next week's tasks14:20
fungigmaan: ^ regarding tempest release14:21
elodillesi think 2nd task of next week should cover this anyway14:21
fungiyeah, i'll make sure to nudge them when i generate those14:21
elodilles+114:21
elodillescool, thanks again14:21
fungiof course14:21
ttx++14:21
elodillesnext topic then14:21
elodilles#topic Assign R-3 week tasks14:21
fungii took most/all14:22
fungiwondering if there's any point in holding the meeting if it will be just me, but i also don't mind talking to myself14:22
elodillesthanks for this, too. i can't promise i'll be around enough next week14:22
fungiright, i figured the two of you would be unavailable14:23
elodillesyepp14:23
ttxyeah or be around but technically unable to interact well14:23
fungii'd rather not make assumptions about what kind of connectivity you'll have there14:24
elodillesabout the meeting: maybe we can have it together with R-2, or Monday of R-214:24
elodillesoh, but on that week you fungi will be unavailable14:24
fungiyes14:25
fungii'm gone once you're back14:25
elodilles:)14:25
fungiconvenient timing at least14:25
ttxfair :)14:25
elodillesthen just ping us if something needs to be done the week after14:25
elodillesokay, let's move on then to next topic14:26
elodilles#topic Review weekly countdown email14:26
elodilles#link https://etherpad.opendev.org/p/relmgmt-weekly-emails14:26
elodillesplease review ^^^14:26
elodillesand I'll send it later today, if OK14:26
fungiread through it a few minutes ago and it lgtm14:26
elodilles+114:27
ttxlgtm14:27
elodilles#topic Open Discussion14:27
elodillesanything else to discuss?14:27
fungii didn't have anything14:28
ttxnope14:28
elodillesokay14:28
fungioh, minor note14:28
elodillesyes?14:28
fungithere was a brief discussion in the tc channel about automation to propose release requests14:29
fungicardoe was talking about looking into it and trying to figure out what the logic for that should be14:29
elodillesoh, sounds interesting :-o14:29
fungijust wanted to make sure folks here were aware14:29
elodilleswe have a bunch of scripts,14:29
elodillessome minor thing would be i guess to figure out the version bump14:30
fungithis was mostly about making sure teams don't forget to propose new releases once security fixes merge14:30
elodillesi see14:30
fungiyes, we talked about what the challenges would be with figuring out the proper version number, batching, and so on14:30
fungianyway, no need to go into it during the meeting14:31
fungibon voyage!14:31
elodillesreno does something like that, but that would need proper phrasing of commit messages (and using tags properly, etc)14:31
ttxsee you on the other side elod!14:31
elodillesttx: see you o/ safe travel o/14:31
fungieat many soup dumplings14:32
elodilles:)14:32
elodillesokay, let's end the meeting now14:32
elodillesthanks for participating14:32
elodilles#endmeeting14:32
opendevmeetMeeting ended Fri Sep  4 14:32:47 2026 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:32
opendevmeetMinutes:        https://meetings.opendev.org/meetings/releaseteam/2026/releaseteam.2026-09-04-14.01.html14:32
opendevmeetMinutes (text): https://meetings.opendev.org/meetings/releaseteam/2026/releaseteam.2026-09-04-14.01.txt14:32
opendevmeetLog:            https://meetings.opendev.org/meetings/releaseteam/2026/releaseteam.2026-09-04-14.01.log.html14:32
ttxthanks elodilles !14:32
elodilles++14:33
elodillesfungi: about the 4 remaining stable/2026.2 branch cuts: maybe nova can be force-merged14:35
elodillesif you review the patch and looks OK14:35
elodillesthe other 3 has some merged patches after their final releases, if i remember well :/ but maybe we can force merge them as is, if we want to be strict and avoid further lib releases after the lib freeze :/14:39
elodilles(and further requirements bumps...)14:40
fungiyeah, it looked like some had been revised today14:44
opendevreviewBartosz Bezak proposed openstack/releases master: Tag monthly kolla stable releases  https://review.opendev.org/c/openstack/releases/+/100399114:57
gmaanttx: fungi ack, I will release it today. was waiting for one of the glance sec bug's tempest fix for sec bug which is merged yesterday15:39
cardoeelodilles: can you point me at some of the scripts you have?15:39
fungicardoe: utility scripts run manually by release managers can be found at https://opendev.org/openstack/releases/src/branch/master/tools15:40
elodillescardoe: maybe the new-release command [1] and the tools/process_auto_releases.sh [2] are the most relevant ones.15:49
elodilles[1] https://releases.openstack.org/reference/using.html#using-new-release-command15:49
elodilles[2] https://releases.openstack.org/reference/using.html#tools-process-auto-releases-sh15:49

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