14:00:58 <ttx> #startmeeting releaseteam
14:00:58 <opendevmeet> Meeting started Fri Jan 17 14:00:58 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:58 <opendevmeet> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
14:00:58 <opendevmeet> The meeting name has been set to 'releaseteam'
14:01:03 <elodilles> o/
14:01:18 <frickler> \o
14:01:18 <ttx> Ping list: release-team armstrong
14:01:41 <ttx> Agenda at https://etherpad.opendev.org/p/epoxy-relmgt-tracking#L209
14:01:58 <ttx> #topic Review task completion
14:02:18 <ttx> - Review any remaining milestone-2 exceptions (all)
14:02:46 <ttx> #link https://review.opendev.org/q/topic:%22epoxy-milestone-2%22
14:02:55 <armstrong> o/
14:03:19 <ttx> Looks like we are left with two
14:03:20 <ttx> https://review.opendev.org/c/openstack/releases/+/938583
14:03:30 <ttx> and https://review.opendev.org/c/openstack/releases/+/938780
14:04:22 <ttx> oslo-metrics I just approved
14:04:48 <elodilles> actually 3 as we have metalsmith as well: https://review.opendev.org/c/openstack/releases/+/938574
14:04:58 <ttx> python-freezerclient we should probably wait until https://review.opendev.org/c/openstack/governance/+/938938 is done
14:05:27 <elodilles> +1 for wait for python-freezerclient governance patch ^^^
14:05:27 <ttx> posted +2 on the metalsmith one
14:06:00 <ttx> If someone lese can review https://review.opendev.org/c/openstack/releases/+/938574
14:07:40 <ttx> Added a tracker task for the freezer one
14:09:04 <elodilles> +2+W'd the metalsmith release
14:09:24 <ttx> perfect, task completed then
14:09:30 <elodilles> \o/
14:09:37 <ttx> - Now that we are past MembershipFreeze, we should check if the OpenStack map will need to be updated (ttx)
14:09:57 <ttx> I did a quick check, the map looks accurate, we should change it if Freezer is revives though
14:10:05 <ttx> revived*
14:10:08 <elodilles> +1
14:11:02 <ttx> also added a tracker task for that for next week
14:11:16 <ttx> - Plan the next release cycle schedule (elod)
14:11:36 <fungi> i'm trying to keep an eye on the freezer situation as well
14:11:56 <fungi> hoping to have a resolution quickly
14:12:09 <ttx> #link https://storage.bhs.cloud.ovh.net/v1/AUTH_dcaab5e32b234d56b626f72581e3644c/zuul_opendev_logs_f2d/939528/2/check/openstack-tox-docs/f2d53f7/docs/flamingo/schedule.html
14:12:39 <elodilles> i've added it as 26 weeks long
14:12:52 <elodilles> release @ Oct 1st
14:13:10 <elodilles> and a bit shaky Flamingo-1 at July 3rd :S
14:14:06 <ttx> flamingo-3 milestone collides with open source summit EU but I guess we can survive that
14:14:27 <elodilles> hmmm, that too then :S
14:14:41 <elodilles> but yeah, probably these are OK
14:15:27 <ttx> I'll give it some extra thought and review it
14:15:35 <ttx> Thanks for working on it!
14:15:49 <elodilles> we could maybe make the cycle 1 week longer, with that shift 1 week every milestone and the release
14:16:01 <elodilles> but meh, maybe 26 weeks are enough
14:16:12 <elodilles> it's not even a slurp release ;)
14:16:29 <elodilles> ttx: ACK & np
14:16:53 <ttx> #topic Assign R-10 week tasks
14:17:14 <ttx> Looks like they are all assigned?
14:17:28 <elodilles> yepp, thx o:)
14:17:34 <opendevreview> Merged openstack/releases master: Release oslo.metrics for Epoxy-2 milestone  https://review.opendev.org/c/openstack/releases/+/938583
14:17:37 <ttx> and no email to send this week, so nothing to review
14:17:41 <ttx> #topic Open Discussion
14:18:19 <ttx> should we force-merge those 2023.1-last things?
14:19:22 <elodilles> yeah, they need to be reviewed and then force-merge if no answer from team
14:19:27 <elodilles> i can work on it on Monday
14:19:29 <ttx> other topic: are we ready to approve https://review.opendev.org/c/openstack/releases/+/938510 so that it unblocks that pbr release?
14:19:42 <frickler> force-merge as in ptl-override or is CI failing?
14:19:53 <ttx> ptl-overrids, i mean
14:19:55 <elodilles> frickler: PTL-override
14:21:08 <ttx> also elodilles  I think frickler needs https://review.opendev.org/c/openstack/releases/+/939322 reviewed
14:21:13 <frickler> ok
14:21:42 <frickler> for 938510 did someone look into skipping the u-c bump proposal?
14:22:04 <ttx> frickler: not me
14:22:27 <elodilles> ttx frickler : can we add a 'set antelope status to unmaintained' patch on top of the puppet + osa patches?
14:22:33 <frickler> 939322 should only be merged when osa and python are also reviewed and ready, so that we can restore it right away after that, I'd think
14:22:52 <ttx> elodilles: also please review https://review.opendev.org/c/openstack/releases/+/938400 if you can
14:23:00 <frickler> elodilles: gerrit does allow the revert only after it is merged, but could create one manually I guess
14:23:34 <opendevreview> Merged openstack/releases master: Release metalsmith for Epoxy-2 milestone  https://review.opendev.org/c/openstack/releases/+/938574
14:24:06 <elodilles> ttx: murano patch +2+W'd
14:24:32 <fungi> frickler: i looked into the uc bump situation for pre-releases
14:25:07 <fungi> we have in the past proposed pre-releases and in some cases merged them
14:25:13 <elodilles> frickler: ah, OK, well, i'm OK with reverting the revert after things are done o:) i just don't want antelope to linger as 'maintained' for too long time :)
14:25:38 <fungi> you can find some rc1 references in the upper-constraints.txt git history from recent cycles
14:26:32 <frickler> fungi: for independent releases? I think it may be a different situation for stuff like neutron
14:26:33 <fungi> i expect that's intentional, so presumably we wouldn't want to start skipping them
14:27:05 <fungi> frickler: not for independent releases, no, because independent model projects haven't ever been allowed to tag pre-releases
14:28:08 <fungi> but also in the specific case of pbr, we'd want to propose a constraints bump anyway at least to get back test results
14:28:34 <frickler> ah, right. well ok we can still handle this by abandoning the bump in reqs if we really do not want one, so ok to proceed for me
14:30:03 <ttx> alright, anything else to cover?
14:30:41 <fungi> also we have release managers reviewing these requests, so are free to set a high bar for rationale and after-merge care for pre-release requests if desired
14:31:20 <frickler> elodilles: how are you progressing with the eom keepalive things?
14:31:54 <elodilles> frickler: i've pushed multiple gate fixes recently, but we will see how far i'll get
14:32:34 <elodilles> maybe around end of next week i can update the patch
14:32:54 <frickler> I think it would be good if you could document your intended update even if the fixes aren't done yet
14:33:09 <elodilles> frickler: ACK
14:33:16 <frickler> so we can agree on what still remains to be done
14:33:25 <elodilles> +1
14:34:46 <ttx> ok... anything else befroe we close?
14:36:07 <elodilles> -
14:36:29 <fungi> negatory
14:37:39 <ttx> #endmeeting