14:00:47 <ttx> #startmeeting releaseteam
14:00:47 <opendevmeet> Meeting started Fri Jul 11 14:00:47 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:47 <opendevmeet> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
14:00:47 <opendevmeet> The meeting name has been set to 'releaseteam'
14:00:59 <ttx> Ping list: release-team elod
14:01:07 <ttx> Our agenda is down at:
14:01:18 <ttx> https://etherpad.opendev.org/p/flamingo-relmgt-tracking#L205
14:03:00 <elodilles> o/
14:03:28 <ttx> #topic Review task completion
14:03:42 <ttx> - Review any remaining milestone-2 exceptions (all)
14:03:57 <ttx> #link https://review.opendev.org/q/topic:flamingo-milestone-2+is:open
14:04:21 <elodilles> one open patch waiting for a 2nd core review :]
14:04:27 <ttx> Just approved
14:04:32 <ttx> all set then!
14:04:34 <elodilles> nice \o/
14:04:53 <ttx> - Ensure that all new-release patches in requirements repository for the milestone-2 releases are merged (all)
14:05:07 <ttx> #link https://review.opendev.org/q/project:openstack/requirements+branch:master+is:open+topic:new-release
14:05:12 <elodilles> empty list \o/
14:05:31 <ttx> - Propose convenience releases for 2024.1 Caracal to ease the transition of Caracal to Unmaintained and avoid rush and broken releases when the transition deadline is coming. (elod)
14:05:45 <ttx> #link https://review.opendev.org/q/topic:caracal-stable
14:05:58 <elodilles> sorry for proposing them late,
14:06:08 <elodilles> i did not have time before i went to vacation
14:06:11 <ttx> It's not super time-sensitive
14:06:23 <ttx> looks like we are on track for approvals
14:06:29 <elodilles> yes
14:06:36 <elodilles> some already merged
14:06:54 <ttx> - Now that we are past MembershipFreeze, we should check if the OpenStack map will need to be updated to reflect future final release contents (ttx)
14:06:57 <elodilles> and usually there are some that will be abandoned due to lack of response
14:07:21 <ttx> I have looke dinto it with fungi and we don't think any change is needed compared to the Epoxy map
14:07:32 <fungi> yeah, afaik the same projects are in this release as were in the last one
14:07:50 <ttx> There is a new component in telemetry but it's not a "servcie", more of a conduit
14:07:52 <fungi> i couldn't find any evidence to the contrary anyway
14:08:13 <elodilles> sounds good
14:08:14 <ttx> (Aetos)
14:08:29 <ttx> - Plan the next release cycle schedule (2026.1 Gazpacho) (ttx)
14:08:49 <fungi> there's also a new thing called grian
14:08:49 <ttx> I did post a very standard 26-week version that ends on April 1st for fun
14:08:59 <ttx> grian-ui, right?
14:09:12 <ttx> It's just a Horizon dashboard component
14:09:15 <fungi> yeah
14:09:22 <ttx> so it does not require its own mention on the map either
14:09:29 <elodilles> hmm, i did not see grian-ui patch yet
14:09:37 <opendevreview> Merged openstack/releases master: Release oslo.messaging for Flamingo-2 milestone  https://review.opendev.org/c/openstack/releases/+/953628
14:09:38 <ttx> #link https://review.opendev.org/c/openstack/releases/+/954614
14:09:41 <fungi> i'm double-checking it
14:09:41 <elodilles> i mean, as a deliverable
14:10:03 <fungi> also part of telemetry anyway
14:10:04 <elodilles> will grian-ui be part of 2025.2 Flamingo?
14:10:20 <ttx> #link https://419f00805ecb0abaedd3-f6495af2602100b34baeae26a45cd2d3.ssl.cf5.rackcdn.com/openstack/2dd191e8df9c4ca599ad70dec8a475e3/docs/gazpacho/schedule.html
14:10:22 <elodilles> should we have a deliverable file for it?
14:10:50 <ttx> elodilles: they are planning on filing one
14:10:55 <ttx> see last week meeting notes
14:11:15 <elodilles> ttx: ACK, good to know that, so that it won't surpise us then :)
14:11:21 <ttx> Please post comments / issues with the Gazpacho recipe on the review
14:11:30 <fungi> but from a map perspective, i think it's still not a separate enough thing that it warrants its own callout
14:11:45 <frickler> isn't it a bit too late for new deliverables?
14:11:49 <elodilles> about the 2026.1 Gazpacho schedule: i had a quick glance only yet, i added one minor comment
14:12:13 <ttx> frickler: it's in reaction to our recent outreach
14:12:16 <elodilles> otherwise 26 weeks long April 1st fun looks good to me :]
14:12:35 <ttx> The deliverable was declared in governance but not yet in releases
14:12:46 <ttx> Agree the sooner the better
14:12:59 <ttx> #topic Assign R-10 week tasks
14:13:17 <ttx> Looks like they are all assigned, thanks elodilles !
14:13:34 <ttx> #topic Open Discussion
14:13:39 <elodilles> frickler: well, in the past release team liked things to settle until milestone-2, so yes, we are 1 week late (expecting the patch will arrive soon for grian-ui)
14:14:11 <ttx> In an ideal world we'd have them all before milestone-2 to get two releases runs before final
14:14:29 <ttx> But as long as they appear before milestone-3 we can make it work
14:14:40 <elodilles> +1
14:14:56 <elodilles> (and no topic from me to open discussion)
14:15:00 <ttx> Anything we should be discussing?
14:19:02 <ttx> Guessing that's a no
14:19:11 <ttx> #endmeeting