Tuesday, 2026-11-03

*** ykarel__ is now known as ykarel04:19
opendevreviewElod Illes proposed openstack/releases master: [horizon] Transition 2025.1 Epoxy to Unmaintained  https://review.opendev.org/c/openstack/releases/+/101096608:25
elodillesokay, it seems that one of the recent two tox releases fixed the gate issue. \o/ I'll continue the Epoxy transition09:06
opendevreviewMerged openstack/releases master: [horizon] Transition 2025.1 Epoxy to Unmaintained  https://review.opendev.org/c/openstack/releases/+/101096609:26
opendevreviewElod Illes proposed openstack/releases master: [keystone] Transition 2025.1 Epoxy to Unmaintained  https://review.opendev.org/c/openstack/releases/+/101095510:17
opendevreviewMerged openstack/releases master: [trove] Transition 2025.1 Epoxy to Unmaintained  https://review.opendev.org/c/openstack/releases/+/101094010:23
opendevreviewMerged openstack/releases master: [cloudkitty] Transition 2025.1 Epoxy to Unmaintained  https://review.opendev.org/c/openstack/releases/+/101092910:44
opendevreviewMerged openstack/releases master: [freezer] Transition 2025.1 Epoxy to Unmaintained  https://review.opendev.org/c/openstack/releases/+/101095110:44
opendevreviewMerged openstack/releases master: [vitrage] Transition 2025.1 Epoxy to Unmaintained  https://review.opendev.org/c/openstack/releases/+/101097010:44
opendevreviewMerged openstack/releases master: [masakari] Transition 2025.1 Epoxy to Unmaintained  https://review.opendev.org/c/openstack/releases/+/101096010:44
opendevreviewMerged openstack/releases master: [magnum] Transition 2025.1 Epoxy to Unmaintained  https://review.opendev.org/c/openstack/releases/+/101094910:54
opendevreviewMerged openstack/releases master: [barbican] Transition 2025.1 Epoxy to Unmaintained  https://review.opendev.org/c/openstack/releases/+/101096310:58
opendevreviewMerged openstack/releases master: [glance] Transition 2025.1 Epoxy to Unmaintained  https://review.opendev.org/c/openstack/releases/+/101096411:05
opendevreviewMerged openstack/releases master: [OpenStackSDK] Transition 2025.1 Epoxy to Unmaintained  https://review.opendev.org/c/openstack/releases/+/101095711:05
opendevreviewMerged openstack/releases master: [kolla] Transition 2025.1 Epoxy to Unmaintained  https://review.opendev.org/c/openstack/releases/+/101095411:14
opendevreviewElod Illes proposed openstack/releases master: [requirements] Transition 2025.1 Epoxy to Unmaintained  https://review.opendev.org/c/openstack/releases/+/101096211:30
elodillesfrickler: i don't see any other open new-release patch for stable/2025.1 so I presume requirement's 2025.1 can move to Unmaintained, right? ^^^11:32
opendevreviewMerged openstack/releases master: [keystone] Transition 2025.1 Epoxy to Unmaintained  https://review.opendev.org/c/openstack/releases/+/101095511:32
fricklerelodilles: yes, it was only the km bump11:33
elodillescool, thanks o/11:40
elodilleslater today i'm planning to run the EOM cleanup script to delete the stable/2025.1 branches11:46
elodillesnote that the vitrage related release job failures are because vitrage is retired, so we don't need to do anything if i'm not mistaken11:59
elodilles(and yepp. probably could have been moved to EOL directly, too... :S)12:00
opendevreviewMerged openstack/releases master: [Quality Assurance] Transition 2025.1 Epoxy to Unmaintained  https://review.opendev.org/c/openstack/releases/+/101094612:03
opendevreviewMerged openstack/releases master: [requirements] Transition 2025.1 Epoxy to Unmaintained  https://review.opendev.org/c/openstack/releases/+/101096212:04
*** haleyb|out is now known as haleyb13:03
elodillesokay, all projects have branched to unmaintained/2025.1 so I'm gonna run the EOM cleanup script now14:17
*** haleyb is now known as haleyb|out14:39
elodillesand there is the list of the deleted stable/2025.1 branches: https://paste.opendev.org/show/b1se506GVyi9F8872zuQ/ 15:04
opendevreviewElod Illes proposed openstack/releases master: Set 2025.1 Epoxy state to Unmaintained  https://review.opendev.org/c/openstack/releases/+/101391815:18
fricklerrelease-team: there was a discussion about the treatment of stable and eom branches for retired projects in the TC meeting just now. maybe you want to read it up and possibly share some thoughs or also historical context18:10
frickler(this relates to the venus and vitrages issues noticed earlier, too)18:11
fungioh did we also end up with failures for vitrage? (i know both got retired last cycle but only heard about the failure for venus)18:16
frickleryes, the failures are because the reno jobs run on master, and the master branch got emptied18:17
fungiah, the failure that was brought to my attention is where git-review failed to push an automated change to the new unmaintained/2025.1 branch after it was created18:19
fungiso we have multiple related failure modes18:19
frickleroh, indeed. so two more reasons not to do the eom transition for those18:34
elodillesyepp, we got to the conclusion to move to EOL directly instead of Unmaintained in the past, I just simply forgot that when i approved the patches on Friday :/ it probably have to be documented somewhere to not to forget next time :S20:22
elodillesi'll read back the meeting logs when i get back on Thursday, but now i'm switching to PTO for tomorrow20:23
elodillesbtw, i'd appreciate a 2nd core review on this patch o:) https://review.opendev.org/c/openstack/releases/+/101391820:24
elodillessee you the day after tomorrow o/20:24
*** elodilles is now known as elodilles_pto20:24
fungiapproved it just now, thanks again for all the hard work!20:26
opendevreviewMerged openstack/releases master: Set 2025.1 Epoxy state to Unmaintained  https://review.opendev.org/c/openstack/releases/+/101391820:51

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