Friday, 2024-01-12

*** noonedeadpunk_ is now known as noonedeadpunk08:14
elodillesreminder: weekly meeting starts in less than half an hour13:32
opendevreviewElod Illes proposed openstack/releases master: Caracal-2 release for ceilometermiddleware  https://review.opendev.org/c/openstack/releases/+/90491913:59
elodillesit's time!14:01
elodilles#startmeeting releaseteam14:01
opendevmeetMeeting started Fri Jan 12 14:01:30 2024 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
hberaudo/14:01
elodillesPing list: elod14:01
elodilleso/14:01
elodilles#link https://etherpad.opendev.org/p/caracal-relmgt-tracking14:01
elodilleswe are at line 18814:02
elodillesttx is on PTO, so we don't need to wait for him14:02
elodilles#topic Review task completion14:03
elodilles1st task was: 'Follow up with Magnum team re: magnum-capi-helm-charts presence in Caracal release (elod)'14:03
elodillesi've pinged the team on IRC and they discussed it on their weekly meeting and decided that the deliverable is not yet ready to be part of the release14:03
hberaudack14:03
hberaudthx14:03
elodillesmaybe next cycle :)14:04
elodilleswe will see14:04
elodilles2nd task: 'Follow up with TC regarding tripleo "independent" deliverables and whether we should make them release-model:abandoned (fungi)'14:04
elodillesi saw that fungi dropped this to TC meeting14:04
fricklerwill be retired: https://review.opendev.org/c/openstack/governance/+/90514514:04
elodillesand gmann proposed the patch:14:04
elodilles#link https://review.opendev.org/c/openstack/releases/+/90514714:04
elodillesfrickler: ACK, thanks for the info14:05
elodillesso as soon as the governance patch has merged, we can review & merge the patch in releases repo14:05
fricklerboth DPLs seem to have acked the governance patch already, so next up will be emptying the repos14:06
elodilles+114:06
elodillessounds good14:06
elodillesanything else to add?14:06
elodillesOK, let's move on to the next task then14:07
elodilles3rd task was: 'Generate release requests for all cycle-with-intermediary libraries which had changes, but did not release since milestone-1. (elod)'14:08
elodillesand i've generated the patches:14:08
elodilles#link https://review.opendev.org/q/topic:caracal-milestone-214:08
elodilleshalf of them have merged already,14:08
hberaudwill +W the remaining patches after the meeting14:08
elodilleshberaud: thanks in advance o/14:09
hberaudnp14:09
elodillesfor some the only somewhat relevant content is the python classifier update,14:09
hberaudok14:09
elodilles(dropping py36, py37 and adding py310, py311)14:10
elodillesbut maybe it's better to release them anyway14:10
hberaudnp14:10
elodillesand there are no exceptions left,14:10
hberaudack14:10
elodillesteams who signalled that need an update, already updated their release patch and those are released already14:11
elodillesso I think we are OK14:11
hberaudack14:11
elodilles4th task: 'To catch if there are acl issues in newly created repositories, run tools/aclissues.py for review. (elod)'14:11
elodillesi've run the script,14:12
elodillesno ACL issues found by script14:12
hberaudnice14:12
elodillesyepp, it was a bit suspicious now that the ironic repos ACLs didn't printed any warning ;)14:12
elodillesthanks to the fix from the last cycle :)14:13
hberaud\o/14:13
elodillesthe output was too empty :)14:13
hberaud:)14:13
elodillesOK, the tasks are covered, let's move on!14:13
elodilles#topic Assign R-11 tasks14:13
elodillesand this is done :)14:13
hberaudthanks elodilles 14:14
elodillesnp :)14:14
elodillesas I said we don't have milestone-2 exceptions14:14
elodilles(of course, if any team wants to add a late release, then we can process that...)14:15
hberaudwfm14:15
elodillesand i'll try to figure out a schedule, and ask for reviews 1st from the team then from PTLs on mailing list14:15
elodilles* release cycle schedule14:16
elodilles* for 2024.2 'D'14:16
hberaudack14:16
elodilles(btw i will reach out to the Foundation whether they have the name already. I haven't seen a mail yet)14:17
fricklervoting ends today14:17
hberaudI see the vote14:17
elodillesah, good, exciting :)14:17
elodillesthen we'll see :)14:17
elodillesnext topic then \o/14:18
elodilles#topic Review countdown email14:18
elodilles#link https://etherpad.opendev.org/p/relmgmt-weekly-emails14:18
elodillesplease review ^^^14:18
frickler"$other-upcoming-event" is intentional?14:19
elodillesnope, that was a leftover :)14:20
elodillesremoved14:20
elodillesmaybe it's too early anyway, to advertise any event14:20
hberaudmay we can also add the final release in the "upcoming deadlines"...14:20
elodillesyepp, let's do that. adding it in a minute14:21
fricklerwell one could mention that the date for the next ptg has been announced, but might be a bit offtopic14:21
hberaudwe could announce the PTG date in the coming weeks within the upcoming deadlines14:22
elodillesfrickler: we usually add the PTG there, so it's not off-topic at all14:22
elodillesi thought maybe we are too early for that but you are right, let's add it14:22
elodillesany of you has the exact date in front of you? o:)14:23
hberaudnope14:23
frickler8.4. - 12.4.14:23
fricklerI remember because I was puzzled that the days are the same as for the current week14:24
elodilles:)14:24
hberaudvirtual?14:24
fricklerbut that's because we have Feb 29 this year14:24
fricklervirtual, yes14:24
elodillesyepp, leap year14:24
hberaudLGTM14:25
fricklerhttps://openinfra.dev/ptg/ if you want to link to it14:25
elodilleswhat was it? it was said that we don't use the word 'virtual' anymore?14:25
hberaudok14:25
fricklerwell the above site does use it14:25
elodillesahh, but there it is, so then let's use it :)14:25
fricklercool, ack14:26
elodillessomething like that14:26
hberaudLGTM14:26
elodillesthanks i'll send it later today14:27
hberaudthanks14:27
elodilleslast topic then:14:27
elodilles#topic Open Discussion14:27
fricklerI have two questions14:27
elodillesI have one topic after you :)14:27
elodillesso, shoot :)14:27
fricklera) the TC has marked four projects as inactive, iiuc that means they will not be part of the release, but they are still listed in deliverables. what action needs to be taken there?14:28
elodillesfrickler: oh, good topic!14:29
elodillesif they are inactive then i guess we should not relese them, right?14:29
fricklerthat's my understanding, yes14:29
hberaudtag them abandoned? https://releases.openstack.org/reference/release_models.html#abandoned14:29
elodilleswhich are the 4 projects?14:29
fricklermonasca, sahara, freezer, solum14:30
hberaudand I think they will be ignored by our tooling 14:30
fricklergovernance/reference/emerging-technology-and-inactive-projects.rst14:30
elodilles'abandoned' are for cycle independent deliverables,14:30
fricklerI think we wanted to wait one cycle before actually retiring14:31
elodillesso I think we have to remove them from deliverables/caracal/*14:31
hberaudnope14:31
hberaudI think they are for all deliverables14:31
hberaudand as said in the doc they are ignored by the tooling at the next series creation14:31
elodilleshmmm, cool14:32
hberaudat least that's what I understand14:32
elodillesOK, then patches needs to be created with the new flag as 'abandoned'14:32
hberaudwe can also remove files if no release exists for this series, that also work...14:33
elodillesi'll propose then patches against the four projects' deliverables and ask you to review it14:33
elodilleslet me add a task for next week14:34
elodillesto not to forget :)14:34
elodillesthere14:35
fricklerdid a quick check and they all don't have releases this cycle yet14:35
elodilles(i think one of our former task should have caught this, but probably they weren't marked inactive at that time?)14:36
elodillesfrickler: yepp, i'm pretty sure that not even any patches were merged in these repos recently...14:36
fricklersome were marked pretty recently14:36
fricklerbut it would be good to know when your task was happening14:37
fricklerso we (TC) can notify you about late changes14:37
hberaudhttps://github.com/openstack/releases/commit/50a23bb308fa57e45ccc3562290103d635e9409f14:37
hberaudI think we can simply remove the file ^14:37
elodillesbefore Milestone-2 we have tasks that checks things against governance repo14:37
hberaudfiles14:38
elodilleshberaud: ACK, i'll double-check before proposing the patches14:39
hberaudok14:39
fricklerok, so that's covered then I guess14:39
fricklerb) might be actually the same as your topic: unmaintained tooling14:40
elodillesfrickler: i also waited for that to happen (to mark those deliverables as inactive/retired) as we struggle with them for some cycles already14:40
elodillesfrickler: yepp, i wanted to point to the same topic :)14:40
fricklerelodilles: yes, I know, and I'm glad that there was consensus now in the TC to take this step14:40
fricklerso I saw your patches, which need reviews, is that all that is missing currently?14:41
elodillesfrickler: yepp, life will be easier for us, and those who needs those repos anyhow, maybe now realise that something needs to be done14:41
elodillesfrickler: yepp, i think we can move on with the patches:14:42
elodilleshttps://review.opendev.org/q/topic:%22relmgt-unmaintained-state%2214:42
hberaudwill review them after the meeting14:42
elodillesmaybe early next week we can merge them if you haven't find any issue or missing things14:43
fricklerok, I already started looking, but I don't have too much experience with the tools14:43
elodillesthe last two patch will test the tagging and branch cutting14:43
fricklermaybe I should start from the end, then ;)14:43
elodillesi meant the patches against release-test repo o:)14:44
elodillesbut that's easy to start with ;)14:44
frickleranyway that answers what I had in mind, thx14:44
elodillesif anything comes up during testing then we need to fix them anyway14:45
elodillesso, fingers crossed14:45
elodillesOK14:46
elodilleslooking forward to the tesing early next week :)14:46
elodillesany other topic for today?14:47
elodillesi hear silence :) so let's close the meeting then!14:50
elodillesthanks hberaud frickler for participating o/14:50
elodilles#endmeeting14:50
opendevmeetMeeting ended Fri Jan 12 14:50:59 2024 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:50
opendevmeetMinutes:        https://meetings.opendev.org/meetings/releaseteam/2024/releaseteam.2024-01-12-14.01.html14:50
opendevmeetMinutes (text): https://meetings.opendev.org/meetings/releaseteam/2024/releaseteam.2024-01-12-14.01.txt14:50
opendevmeetLog:            https://meetings.opendev.org/meetings/releaseteam/2024/releaseteam.2024-01-12-14.01.log.html14:50
hberaudthanks elodilles 14:51
fricklerthx all14:51
elodilleso/14:51
fungiand yes, the tripleo outcome was a positive one, as far as getting clarity on the release managers being able to just ignore those remaining deliverables14:51
hberaudelodilles: let you double check https://review.opendev.org/c/openstack/releases/+/90494215:04
elodillesfungi: ++15:22
elodilleshberaud: ACK, thanks for the answer there!15:22
hberaudnp15:22
opendevreviewMerged openstack/releases master: [Glance] Caracal milestone 2 release  https://review.opendev.org/c/openstack/releases/+/90521915:23
opendevreviewMerged openstack/releases master: Caracal-2 release for os-brick  https://review.opendev.org/c/openstack/releases/+/90492615:23
opendevreviewMerged openstack/releases master: Caracal-2 release for python-blazarclient  https://review.opendev.org/c/openstack/releases/+/90494515:23
opendevreviewMerged openstack/releases master: Caracal-2 release for python-troveclient  https://review.opendev.org/c/openstack/releases/+/90495615:24
opendevreviewMerged openstack/releases master: Caracal-2 release for keystoneauth  https://review.opendev.org/c/openstack/releases/+/90492215:24
elodilleshberaud: i see that meanwhile another patch has landed in oslo.utils, so if you don't mind then i'll quickly update the hash in the patch15:25
hberaudyeah, np15:25
opendevreviewMerged openstack/releases master: Caracal-2 release for cliff  https://review.opendev.org/c/openstack/releases/+/90492015:25
opendevreviewMerged openstack/releases master: Caracal-2 release for ironic-lib  https://review.opendev.org/c/openstack/releases/+/90492115:25
opendevreviewMerged openstack/releases master: Caracal-2 release for kuryr  https://review.opendev.org/c/openstack/releases/+/90492315:26
opendevreviewMerged openstack/releases master: Caracal-2 release for osc-lib  https://review.opendev.org/c/openstack/releases/+/90492915:26
opendevreviewMerged openstack/releases master: Caracal-2 release for openstacksdk  https://review.opendev.org/c/openstack/releases/+/90492515:26
opendevreviewMerged openstack/releases master: Caracal-2 release for os-vif  https://review.opendev.org/c/openstack/releases/+/90492715:27
opendevreviewMerged openstack/releases master: Caracal-2 release for python-keystoneclient  https://review.opendev.org/c/openstack/releases/+/90495215:27
opendevreviewMerged openstack/releases master: Caracal-2 release for python-zunclient  https://review.opendev.org/c/openstack/releases/+/90495815:27
opendevreviewElod Illes proposed openstack/releases master: Caracal-2 release for oslo.utils  https://review.opendev.org/c/openstack/releases/+/90494215:27
elodilleshberaud: there it is ^^^15:27
hberaudack15:27
opendevreviewMerged openstack/releases master: Caracal-2 release for ceilometermiddleware  https://review.opendev.org/c/openstack/releases/+/90491915:29
opendevreviewMerged openstack/releases master: Caracal-2 release for python-designateclient  https://review.opendev.org/c/openstack/releases/+/90494815:29

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