14:00:37 <ttx> #startmeeting releaseteam
14:00:37 <opendevmeet> Meeting started Fri May 16 14:00:37 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:37 <opendevmeet> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
14:00:37 <opendevmeet> The meeting name has been set to 'releaseteam'
14:00:43 <ttx> Ping list: release-team elod
14:00:49 <elodilles> o/
14:02:22 <ttx> #link https://etherpad.opendev.org/p/flamingo-relmgt-tracking#L85
14:02:22 <ttx> #topic Review task completion
14:02:23 <ttx> Our agenda today is at:
14:02:30 <ttx> - Ensure that all trailing projects have been branched for the previous series. (elod)
14:03:19 * frickler is only half here, downstream issues ...
14:03:44 <elodilles> yepp, so
14:03:53 <elodilles> i've created the patches
14:04:08 <elodilles> #link https://review.opendev.org/q/topic:epoxy-cycle-trailing-stable-branch
14:04:51 <elodilles> OSA roles have stable/2025.1
14:05:30 <elodilles> Kayobe and OSA itself are still waiting for finalize their RC patches
14:05:47 <elodilles> but i think we are on track with this
14:06:12 <ttx> - Propose autoreleases for cycle-with-intermediary libraries which did not release since the previous release. (elod)
14:06:27 <elodilles> #link https://review.opendev.org/q/topic:flamingo-milestone-1
14:07:00 <elodilles> i've created release patches where i saw functional code changes ^^^
14:07:28 <elodilles> they are now mostly merged, thanks for the reviews o/
14:07:47 <elodilles> only 2 is waiting for some patches to merge
14:07:59 <ttx> - Catch if there are acl issues in newly created repositories. (elod)
14:08:17 <elodilles> aclissues.py gave empty output, i.e. no ACL issue found
14:09:44 <ttx> it usually is clean at milestone-1
14:10:00 <ttx> - Send weekly email. (ttx)
14:10:08 <ttx> Will do shortly after meeting!
14:10:12 <elodilles> ++
14:10:24 <ttx> #topic Assign R-19 week tasks
14:10:56 <ttx> (also probably ok to start looking at the tasks on the weeks after)
14:11:26 <elodilles> ack
14:11:32 <ttx> since R-19 tasks are mostly (all) tasks
14:11:53 <elodilles> +1
14:12:20 <ttx> elodilles: are you able to do the remaining task on R-17?
14:12:29 <elodilles> note that i'll be off on Monday, Jun 2nd,
14:12:30 <ttx> I'm assuming you will miss next meeting
14:12:53 <elodilles> ttx: yes, very likely i cannot participate
14:12:57 <ttx> ah no. I'll miss it
14:13:15 * ttx is confused
14:13:38 <elodilles> on June 6th?
14:13:54 <ttx> no, ignore me, we still have time
14:13:58 <ttx> I mixed up my weeks
14:14:03 <ttx> #topic Review weekly countdown email
14:14:12 <ttx> #link https://etherpad.opendev.org/p/relmgmt-weekly-emails
14:14:35 <ttx> Please review and let me know if I am clear to send
14:14:39 <elodilles> (so, about R-17 tasks: i'll have a short week, i might be able to handle tasks, but only on Tuesday-Wednesday)
14:14:54 * elodilles clicks
14:16:39 <elodilles> are TC goals up-to-date?
14:16:46 <elodilles> (otherwise LGTM)
14:16:53 <ttx> I checked that there were some listed
14:17:00 <elodilles> ACK
14:17:12 <ttx> Not sure how current they are -- not our job :)
14:17:18 <elodilles> i think it's good to link that
14:17:33 <ttx> OK will send in a few
14:17:42 <elodilles> and there are definitely some goals that are still a thing :)
14:17:47 <ttx> #topic Open Discussion
14:17:52 <ttx> Anything to discuss?
14:19:00 <elodilles> maybe just a note what i already mentioned before the meeting, that we marked 2023.2 Bobcat as End of Life already so our tooling did not process the Kolla 2023.2 Bobcat EOL patch, i.e. there were no 2023.2-eol tags created
14:19:29 <elodilles> being Kolla a cycle-trailing project
14:19:39 <ttx> hmm
14:20:01 <ttx> should we temporarily revert the Bobcat EOL patch to get those in?
14:20:24 <elodilles> yes, that is a solution
14:20:48 <elodilles> definitely something we have to do for OSA when it goes to EOL with its 2023.2
14:22:07 <elodilles> but Kolla is now merged, so probably the easiest solution is to put the 4 2023.2-eol tags manually if someone can do that
14:22:32 <ttx> We could also revert that patch, given no tag was created
14:22:51 <ttx> and then re-apply it
14:22:55 <elodilles> yeah, maybe that's also possible
14:23:07 <ttx> Maybe we should wait for frickler see if he sees a benefit or drawback to this approach
14:23:19 <elodilles> +1
14:23:28 <ttx> he is usually good at spotting potential issues taht we overlook
14:23:37 <elodilles> yepp
14:23:54 <ttx> Also fungi might want to comment
14:24:20 <frickler> I think I'd just push the tags manually, I can do that, though maybe not today
14:24:26 <ttx> They know the infra impact of such tricks better
14:24:42 <ttx> frickler: that works too! No urgency
14:25:14 <elodilles> frickler: thanks, no need to hurry
14:25:18 <ttx> I'll add a task for next week for you to do it -- if you complete it before it's ok
14:25:32 <frickler> ack, thx
14:25:40 <elodilles> thanks \o/
14:26:03 <fungi> seems reaonable for this time
14:26:08 <fungi> reasonable
14:26:43 <elodilles> ACK, so that was all from me :)
14:27:25 <ttx> alright all done
14:27:29 <ttx> Anything else?
14:27:57 <ttx> If not, I'll close this
14:28:04 <ttx> #endmeeting