13:00:32 <elodilles> #startmeeting releaseteam
13:00:32 <opendevmeet> Meeting started Fri Aug 16 13:00:32 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:32 <opendevmeet> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
13:00:32 <opendevmeet> The meeting name has been set to 'releaseteam'
13:00:48 <elodilles> Ping list: release-team elod
13:01:04 <elodilles> #link https://etherpad.opendev.org/p/dalmatian-relmgt-tracking
13:01:55 <elodilles> we are around line 289
13:02:07 <elodilles> o/
13:02:36 <elodilles> and let's just wait a bit, maybe folks will join :)
13:02:48 <elodilles> (thanks frickler for the heads up :))
13:07:48 <elodilles> time is ticking, so let's start, people can read the logs anyway
13:08:07 <elodilles> #topic Review task completion
13:08:11 <frickler> o/
13:08:20 <frickler> sorry for the delay
13:08:20 <elodilles> o/
13:08:24 <elodilles> no problem :)
13:08:41 <elodilles> 1st task was: 'Oslo library freeze (elod)'
13:09:27 <elodilles> the countdown mail contained a section about this,
13:10:04 <elodilles> and i've had a chat with damani , one of Oslo's release liaison,
13:10:27 <elodilles> and he also sent out a reminder about this: https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack.org/thread/5O4YTNIYJVMLV54UZSNH4MQ7BLKPXHG6/
13:11:27 <elodilles> 2nd task was: Notify the Infrastructure team to generate an artifact signing key (but not replace the current one yet), and begin the attestation process (ttx)
13:11:43 <fungi> yeah, i'll hopefully get to that in the next week
13:11:47 <elodilles> according to notes: fungi acked the request
13:11:51 <fungi> indeed
13:11:54 <elodilles> fungi: ACK-ACK :)
13:12:07 <elodilles> thanks in advance o/
13:12:17 <fungi> of course
13:12:22 <elodilles> 3rd task was:
13:12:29 <elodilles> 'Check with the Technical Committee (ttx)'
13:12:48 <elodilles> * to make sure Python runtimes have been determined for the next development cycle https://review.opendev.org/c/openstack/governance/+/926150
13:12:59 <elodilles> so there is the patch ^^^
13:13:13 <elodilles> * Zuul job templates have been created to include those runtimes https://review.opendev.org/c/openstack/openstack-zuul-jobs/+/926153
13:13:17 <elodilles> ditto ^^^
13:13:34 <elodilles> so this is also on track
13:13:54 <elodilles> 4th task: 'Propose DNM changes on repositories where no patches merged recently to check that tests are still passing with the current set of dependencies (libraries, client libraries). (elod)'
13:14:03 <elodilles> patches proposed: https://review.opendev.org/q/topic:release-health-check-cwi-dalmatian
13:14:14 <elodilles> only cought 4 broken gates \o/
13:14:45 <elodilles> i'll ping the teams to look at the failures
13:15:16 <elodilles> (might be some of the gate failures are just temporary issues, we'll see)
13:15:31 <frickler> might also be worth looking at py312 failures
13:15:48 <frickler> just to be prepared for the next cycle
13:16:02 <elodilles> frickler: i saw that there are more py312 failures, but those are non-voting so far
13:16:21 <elodilles> and i hope that teams are aware of that :)
13:16:53 <frickler> I really wouldn't count on that for most teams, but yeah, not really a release team issue
13:17:08 <elodilles> i saw py312 related patches in multiple projects, so hopefully teams are mostly on track with that
13:17:53 <elodilles> but yepp, a couple of weeks, and py312 jobs will be voting on master branch
13:18:35 <elodilles> and that's all about the 'Review task completion' topic
13:18:43 <elodilles> next one:
13:18:58 <elodilles> #topic Assign R-6 week tasks
13:19:13 <elodilles> there's only one task
13:19:23 <elodilles> note that i'll be off on Mon-Tue
13:19:41 <elodilles> so i can take the task, but can only propose patches by Wednesday
13:19:59 <frickler> is there some tool for that task?
13:20:28 <frickler> I could take a look then, but maybe also not earlier then Wednesday
13:20:33 <elodilles> tools/process_auto_releases.sh
13:20:38 <elodilles> this is the script ^^^
13:21:17 <frickler> o.k., I'll take a look and bug you if I can't make progress
13:21:55 <elodilles> frickler: and here is the task description in the Release process: https://releases.openstack.org/reference/process.html#r-6-week-final-library-release-deadline
13:22:06 <elodilles> frickler: thanks in advance o/
13:22:44 <elodilles> if you are unsure in something, then we can look at the task on Wednesday
13:23:22 <frickler> ty
13:23:56 <elodilles> move on then!
13:24:03 <elodilles> #topic Review countdown email for week R-6
13:24:18 <elodilles> #link https://etherpad.opendev.org/p/relmgmt-weekly-emails
13:24:22 <elodilles> please review ^^^
13:25:00 <elodilles> i'll send it later on today if it looks fine for you
13:26:19 <frickler> long one, but lgtm
13:27:04 <elodilles> yepp. we are closer and closer to final release, so there will be more things to take care by PTLs & teams o:)
13:27:20 <elodilles> thanks then!
13:27:27 <elodilles> #topic Open Discussion
13:27:33 <elodilles> anything to discuss?
13:27:47 <frickler> I have a patch open to update the update-constraints job https://review.opendev.org/c/openstack/project-config/+/926405
13:27:58 * elodilles clicks
13:28:18 <frickler> since it is difficult to test this ahead of time, it will need some care with the next release after it is merged
13:28:45 <frickler> the most risky part is switching from focal to noble I think
13:29:23 <elodilles> yepp, that's quite a jump :X
13:29:45 <elodilles> otherwise it sounds like a plan
13:29:53 <frickler> yes, but I didn't think that going to jammy would be much less risky, and this way we can skip one jump
13:30:25 <elodilles> +1
13:30:41 <elodilles> when do you plan to merge and check?
13:30:50 <frickler> so I guess I'll W-1 this until wednesday, so that we can make a release in time after merging it
13:31:04 <elodilles> frickler: sounds good to me!
13:31:11 <frickler> because doing this now before the weekend doesn't sound useful
13:31:38 <elodilles> yepp, not a typical 'before weekend' task :]
13:32:40 <frickler> and that's already all I had
13:32:41 <elodilles> mostly the py312 (default in noble) could cause issues, i guess
13:32:54 <elodilles> but fingers crossed
13:33:28 <elodilles> we can do test release with 'release-test' deliverable
13:33:28 <frickler> it should be easy to create the reqs patch manually if it fails and then fix the job or worst case revert
13:33:38 <elodilles> true
13:33:45 <frickler> release-test isn't in u-c, or is it?
13:34:02 <elodilles> hmmm, you are right, i think it isn't
13:34:36 <elodilles> anyway, as you said, should be easy to handle the fail case
13:34:56 <elodilles> OK, if no more topics,
13:35:03 <elodilles> then let's close the meeting!
13:35:14 <elodilles> thanks for participating o/
13:35:18 <frickler> \o
13:35:22 <elodilles> #endmeeting