13:00:00 <elodilles> #startmeeting releaseteam
13:00:00 <opendevmeet> Meeting started Fri Jul 26 13:00:00 2024 UTC and is due to finish in 60 minutes.  The chair is elodilles. Information about MeetBot at http://wiki.debian.org/MeetBot.
13:00:00 <opendevmeet> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
13:00:00 <opendevmeet> The meeting name has been set to 'releaseteam'
13:00:14 <elodilles> Ping list: release-team elod
13:00:20 <frickler> \o
13:00:23 <elodilles> #link https://etherpad.opendev.org/p/dalmatian-relmgt-tracking
13:00:24 <elodilles> o/
13:00:50 <elodilles> we are way down at line 239
13:01:26 <elodilles> let's go through quickly on the agenda
13:01:53 <elodilles> #topic Review R-12 and R-10 week task completion
13:02:22 <elodilles> R-12 week's tasks are @ L223
13:02:41 <elodilles> 1st task: '    Review any remaining milestone-2 exceptions. (all)'
13:02:49 <elodilles> https://review.opendev.org/q/topic:dalmatian-milestone-2
13:03:17 <elodilles> no open patches, so this looks OK te me \o/
13:03:24 <frickler> ack
13:03:48 <elodilles> 2nd task: '    Plan the next release cycle schedule. (elod)
13:03:51 <elodilles> '
13:04:03 <elodilles> #link https://review.opendev.org/c/openstack/releases/+/924671
13:04:27 <elodilles> sorry for proposing this quite late :S
13:04:32 <frickler> I saw that you updated it, but will need to look again
13:04:49 <elodilles> yepp, according to your comments
13:04:57 <elodilles> nothing else
13:05:05 <elodilles> anyway, it's a 26 weeks long schedule,
13:05:20 <elodilles> release day at April 2nd
13:05:28 <elodilles> Wednesday as usual
13:05:43 <frickler> sounds fine in general
13:06:00 <elodilles> the generated page from the patch: https://storage.bhs.cloud.ovh.net/v1/AUTH_dcaab5e32b234d56b626f72581e3644c/zuul_opendev_logs_efa/924671/2/check/openstack-tox-docs/efad2f3/docs/epoxy/schedule.html
13:06:20 <elodilles> it's way before Easter
13:06:31 <elodilles> one day after fools day :)
13:06:40 <frickler> yes, I saw that easter is late next year
13:07:21 <elodilles> the only concern maybe CubeCon Europe 2025 is just at that week as far as i saw, but i don't know how problematic that is
13:08:15 <frickler> doesn't matter to me, and I don't think we can avoid conflicts with everything
13:08:38 <elodilles> it would be good to get feedback from ttx from foundation point of view before we advertise this to PTLs/teams/community
13:09:20 <fungi> i can also ask
13:09:38 <fungi> (ttx is often quite busy these days)
13:09:39 <elodilles> fungi: ACK, thanks in advance
13:09:45 <frickler> we'll need more reviews anyway before we can announce this
13:09:54 <elodilles> he is travelling this week i know,
13:10:19 <elodilles> but one or two days delay shouldn't be a problem
13:11:15 <elodilles> so yes, reviews are welcome :)
13:12:13 <elodilles> okay, let's move on with the tasks for now
13:12:27 <elodilles> these two were the tasks of R-12
13:12:42 <elodilles> now comes R-10 week's tasks:
13:12:53 <elodilles> L243
13:13:18 <elodilles> 1st task: '    Generate a list of intermediary-released service deliverables that have not done a release in this cycle yet and propose release model change for them if applicable. (elod)
13:13:26 <elodilles> the list of deliverables without any release:
13:14:06 <elodilles> bifrost, ironic-prometheus-exporter, ironic-python-agent-builder, ironic-ui, networking-baremetal, networking-generic-switch, python-openstackclient, swift
13:14:23 <elodilles> (elod) these are the usual ones. and we haven't suggested release model change for these over the past cycles, so i guess we can skip now as well
13:14:58 <elodilles> let me know if you think differently
13:15:17 <frickler> osc has at least proposed a release, though it is not quite ready for it yet
13:15:33 <elodilles> frickler: +1
13:15:52 <frickler> but I'm fine with keeping things as they were
13:15:59 <elodilles> +1
13:16:50 <elodilles> yepp. so, anyway, nothing new that would worth a release model change. moving on.
13:17:02 <elodilles> 2nd task: '    Propose convenience releases for 2023.1 Antelope to ease the transition of Antelope to Unmaintained and avoid rush and broken releases when the transition deadline is coming. (elod)'
13:18:05 <elodilles> i didn't get there to propose these releases this week, but planning to do that next week, when i'll be back in (home) office
13:18:39 <elodilles> so this is still pending, i'm adding a reminder to next meeting's agenda
13:18:46 <frickler> ack, doesn't seem to be too urgent and ptls will mostly take their time to respond anyway
13:19:06 <elodilles> exactly o:)
13:19:53 <elodilles> so these were the tasks from R-12 and R-10 weeks, moving on to next topic:
13:20:03 <elodilles> #topic Assign R-8 week tasks
13:20:38 <elodilles> well, that's a calm week, too, only 1 task (beyond the weekly mail)
13:20:46 <elodilles> and i can handle that
13:21:34 <elodilles> so 'all' tasks taken :)
13:21:51 <elodilles> #topic Review countdown email for week R-9
13:21:59 <elodilles> ok, this will be tricky
13:22:11 <elodilles> so here we have the template:
13:22:16 <elodilles> #link https://etherpad.opendev.org/p/relmgmt-weekly-emails
13:22:29 <elodilles> and I've crossed out the non-relevant parts
13:22:52 <elodilles> and actually i think this time we can skip to send this mail
13:23:34 <elodilles> the only content will be the proposed 2025.1 Epoxy schedule
13:23:44 <frickler> yes, I would have suggested not to include the build link that will soon expire
13:23:58 <elodilles> afair we skipped this last cycle, too
13:23:59 <frickler> but omitting the mail completely is likely the better solution
13:24:34 <elodilles> frickler: yes, it really depends if the schedule is in a mostly-final state or still evolving :)
13:25:56 <elodilles> i think we can skip the mail for now and early next week, when we have more feedback from foundation and release team, i can send a mail to advertise the proposed schedule to PTLs/community
13:26:12 <frickler> +1
13:27:32 <elodilles> ACK, move on to next topic then!
13:27:41 <elodilles> #topic Open Discussion
13:27:55 <elodilles> anything to discuss?
13:28:21 <fungi> sorry if it came up already, but is there anything specific the skyline team needs to do to be officially included in 2024.2/dalmatian now that the tc has graduated them out of emerging/tech preview state? or will they need to wait for 2025.1/epoxy since this happened after the membership freeze deadline?
13:28:59 <frickler> afaict they already did get "official" releases before
13:29:22 <frickler> so nothing will have to change?
13:29:32 <fungi> they're official releases, just not clear whether they were considered part of the coordinated release or merely an official project making releases at the same time
13:30:13 <elodilles> skyline-apiserver and skyline-console is listed under deliverables/dalmatian/
13:30:17 <ttx> Hi! sorry I just got back
13:30:19 <fungi> though i guess they're included in https://releases.openstack.org/caracal/ for example, so maybe it's just the openstack-map that needs them added
13:30:37 <fungi> and nothing for the release team to worry about
13:30:50 <frickler> +1
13:31:13 <elodilles> fungi: yepp, they are considered to be part of the coordinated release of 2024.2 Dalmatian :)
13:31:22 <frickler> I have just one review request that I mentioned earlier https://review.opendev.org/c/openstack/releases/+/924954
13:31:31 <ttx> will review the release schedule but I suspect it will be fine.
13:31:40 <elodilles> ttx: thanks in advance! \o/
13:31:44 <fungi> oh, skyline did get added to the map too looking at https://www.openstack.org/software/
13:31:55 <elodilles> cool \o/
13:35:27 <elodilles> frickler: i commented on the patch
13:36:21 <elodilles> 'requests' is a new (direct) dependency there, so probably we should bump MINOR version (6.7.0)
13:36:55 <frickler> hmm, I'm pretty sure that it is an indirect dependency already, but 6.7.0 should be fine anyway
13:37:15 <frickler> waiting for gtema and stephenfin to respond
13:37:16 <elodilles> frickler: yepp, i have the same feeling
13:38:33 <elodilles> (we should avoid new dependencies (at least beyond openstack libraries) on stable branches anyway, but 'requests' seems fine to me)
13:39:02 <gtema> damn, I am getting insane from all those direct and indirect upgrades
13:40:26 <elodilles> (and 2.14.2 as a lower req is well beyond stable/2024.1's upper constraint: 2.31.0, so should be fine)
13:41:25 <elodilles> (s/well beyond/well under/)
13:41:49 <elodilles> anything else to discuss?
13:41:54 <frickler> just a matter of perspective ;)
13:42:00 <elodilles> :]
13:44:24 <frickler> seems like that's it o/
13:44:46 <elodilles> #info next weekly meeting is in 2 weeks - Aug 9th
13:44:56 <elodilles> thanks ttx for chairing that one o/
13:45:07 <elodilles> Okay, if nothing else to discuss, then thanks everyone for participating and see you next week o/
13:45:12 <elodilles> #endmeeting