14:00:05 <hberaud> #startmeeting releaseteam
14:00:05 <opendevmeet> Meeting started Fri Mar 22 14:00:05 2024 UTC and is due to finish in 60 minutes.  The chair is hberaud. Information about MeetBot at http://wiki.debian.org/MeetBot.
14:00:05 <opendevmeet> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
14:00:05 <opendevmeet> The meeting name has been set to 'releaseteam'
14:00:10 <hberaud> Ping list: elod frickler armstrong
14:00:15 <hberaud> https://etherpad.opendev.org/p/caracal-relmgt-tracking
14:00:33 <hberaud> Welcome everyone, we are now at R-2 (line 386)
14:00:37 <elodilles> o/
14:00:37 <frickler> we should add release-team to the ping list ;)
14:00:40 <frickler> \o
14:01:05 <hberaud> lets wait 1 min before we go
14:01:12 <armstrong> o/
14:01:26 <elodilles> frickler: added ;)
14:01:55 <hberaud> good idea
14:02:01 <hberaud> lets go!
14:02:07 <hberaud> #topic Review task completion
14:02:13 <hberaud> 1) Process any standing RC1 deadline exceptions (all)
14:02:19 <hberaud> if I'm right, there is no exception https://review.opendev.org/q/topic:caracal-rc1-deadline+status:open
14:02:42 <hberaud> 2) Gracefully release tempest plugins with latest changes available (elod)
14:02:51 <hberaud> https://review.opendev.org/q/topic:caracal-tp-latest
14:03:28 <hberaud> a couple of patches still need a second approval
14:04:20 <elodilles> yeah, i've tried to review the leftovers, please review them, too, and let me know if i need to update any of them (version, hash)
14:04:41 <hberaud> ok, will do that after the meeting
14:04:49 <elodilles> ACK, thanks in advance o/
14:04:56 <hberaud> not sure why you left a comment about yoga
14:05:22 <elodilles> you mean the yoga-last patches?
14:05:30 <hberaud> yop
14:06:05 <elodilles> so usually yoga-last marks the last valid and tested state on tempest plugins,
14:06:19 <hberaud> ok
14:06:34 <elodilles> and usually also cut a release on recent cycle
14:06:50 <hberaud> ok, thanks for detals
14:07:15 <elodilles> so some of the caracal-tp-latest patches would match the yoga-last patch
14:07:25 <hberaud> I see
14:07:32 <elodilles> 3 of them actually
14:07:58 <elodilles> besides, i think it would be better to PTL-Approve+1 all the yoga-last patches and merge them
14:08:11 <hberaud> do we want to force patches without respones today? e.g https://review.opendev.org/c/openstack/releases/+/913549
14:08:12 <elodilles> if we don't find any issue with them
14:08:35 <hberaud> ok
14:08:48 <elodilles> hberaud: there was enough time to reply on the patches, so i think we should process them
14:08:55 <hberaud> wfm
14:09:05 <elodilles> (they were proposed in February)
14:09:13 <hberaud> indeed
14:09:24 <hberaud> ok next task
14:09:33 <hberaud> 3) On Monday, generate stable branches for all cycle deliverables that are still missing one (ttx)
14:09:53 <hberaud> there is a couple of comments
14:10:23 <hberaud> lets check the current state
14:12:59 <hberaud> 2 first comments seems now done
14:15:40 <hberaud> Only the ironic and the requirements points seems still pending
14:15:55 <hberaud> so I think we are good with that task
14:16:32 <hberaud> 4) After all the projects enabled in devstack by default have been branched, we can engage with the (elod)
14:17:17 <hberaud> so all teams have been pinged
14:17:41 <elodilles> (for 3: yepp we are ironic deliverables all released and branched)
14:18:09 <hberaud> ack thanjs
14:18:11 <hberaud> thanks
14:18:14 <elodilles> yes, i've pinged QA, ianychoi (I18n SIG) and req team
14:18:21 <hberaud> thanks elodilles
14:18:42 <elodilles> though i think there are new-release patches that might need to merge before we branch requirements
14:18:53 <elodilles> * still open new-release patches
14:19:02 <hberaud> yes
14:19:29 <hberaud> 5) Ensure that all projects that are publishing release notes have the notes link included in their deliverable file (elod)
14:19:45 <hberaud> https://review.opendev.org/q/topic:caracal-releasenotes
14:20:52 <hberaud> another round of links addition can be done next week if some are missing
14:21:01 <elodilles> yeah
14:21:12 <elodilles> definitely there are some that are missing
14:21:21 <elodilles> as usually
14:21:24 <hberaud> :)
14:21:40 <elodilles> people tend to forget about merging reno patches o:)
14:21:57 <hberaud> 6) Let cycle-with-rc projects iterate on RCs as needed. The final release candidate for each project needs to be prepared at least one week before the final release date (all)
14:22:25 <elodilles> yepp, this is kind of a reminder
14:22:30 <elodilles> to us
14:22:51 <hberaud> I don't find RC2 open patches
14:22:59 <elodilles> neither do i
14:23:01 <hberaud> so lets wait
14:23:19 <hberaud> ok, next topic
14:23:27 <hberaud> #topic Assign next week tasks
14:23:30 <elodilles> as we discussed today here, probably we can expect an rc2 for watcher
14:23:47 <elodilles> though the 'team' is quite inactive... so we'll see
14:24:01 <frickler> trove is having similar issues
14:24:06 <hberaud> we have a task for last minute RC2 at the end of R-1
14:24:14 <frickler> but at least there the ptl seems to be working on them
14:24:22 <elodilles> frickler: \o/
14:24:49 <hberaud> (one day before the deadline)
14:25:18 <hberaud> so if they merge things on their side, we will see it
14:27:18 <hberaud> everything is now assigned, thanks guys
14:27:32 <elodilles> thanks too
14:27:35 <hberaud> #topic Review countdown email
14:27:45 <hberaud> https://etherpad.opendev.org/p/relmgmt-weekly-emails
14:29:29 <frickler> do we want to mention the open reno patches?
14:29:40 <hberaud> can't hurt
14:30:00 <elodilles> yepp, that can be added
14:30:13 <frickler> like https://review.opendev.org/q/topic:%22reno-2024.1%22+status:open
14:31:13 <elodilles> i added some explanation to the renolink patch, too, that's also helps as far as i remember :)
14:31:31 <hberaud> thanks
14:31:42 <hberaud> the addition lgtm
14:31:53 <elodilles> mail LGTM
14:32:15 <hberaud> thanks
14:32:44 <elodilles> (i've removed the %22s from the link, sorry, my OCD... :))
14:33:22 <frickler> ok
14:34:58 <hberaud> sent
14:35:04 <elodilles> \o/
14:35:21 <hberaud> #topic Open Discussion
14:35:26 * armstrong the email looks good to me
14:35:28 <hberaud> elodilles: the floor is yours
14:35:36 <elodilles> yeah
14:35:36 <hberaud> armstrong: thanks
14:35:51 <elodilles> just wanted to ask:
14:35:52 <elodilles> next week's release meeting (March 29; Good Friday?)
14:36:02 <armstrong> hmmm
14:36:13 <elodilles> so i don't know whether it's a bank holiday for any of you?
14:36:21 <frickler> for me it is
14:36:47 <hberaud> not for me
14:37:02 <elodilles> for me, too, but i can be around, but if you want we can move the meeting maybe 1 day earlier?
14:37:33 <elodilles> what do you think?
14:37:46 <hberaud> yes, we are close from the final dance, so I'd suggest moving the meeting
14:37:47 <frickler> Thursday would be fine for me, I likely wouldn't be around on Friday
14:38:14 <elodilles> OK, so Thursday 14:00 UTC?
14:38:15 <hberaud> Thursday would be fine for me too
14:38:25 <frickler> +1
14:38:27 <hberaud> wfm
14:38:56 <elodilles> then let's have the meeting on Thursday!
14:39:07 <hberaud> thanks
14:39:14 <hberaud> anything else to add?
14:39:23 <elodilles> nothing from my side
14:39:28 * frickler has a review request
14:39:47 <frickler> #link https://review.opendev.org/c/openstack/releases/+/905154
14:40:04 <elodilles> #agreed next week's release meeting will be at March 28th, Thursday, 14:00 UTC
14:40:13 <frickler> it is about the election schedule, which is already past, but still good to finish this up
14:40:50 <frickler> oh, sorry, I read that as "any other open discussion topic to add"
14:43:28 <hberaud> all duplications seems not addressed, isn't?
14:43:52 <elodilles> there was an answer that that was intentional
14:43:58 <JayF> I just want to note for you all for open disucssion, I will be out of town and out of pocket the first week of April.
14:43:59 <elodilles> if i'm not mistaken
14:44:05 <elodilles> +2+W'd it
14:44:18 <JayF> It's unclear if I will still be tc chair at that time; but if so, please look to rosmaita for anything you may need that release week.
14:44:39 <hberaud> d-election-voting seems still duplicated, but indeed, Ian's comment suggest that it is intentional
14:44:57 <elodilles> JayF: ACK, from ironic point of view there are multiple release liaisons, so shouldn't be a problem :) thanks for the heads up :)
14:45:22 <JayF> elodilles: I was more thinking from a tc side. I don't think there's anything to do, but I wanted to ensure folks knew rather than me disappearing during the release week unexplained :)
14:45:41 <elodilles> JayF: ACK, thanks :)
14:46:01 <hberaud> Anything else that you want to discuss?
14:46:13 <elodilles> nothing else from me
14:46:52 <frickler> nope
14:46:55 <hberaud> ok
14:47:09 <hberaud> then, thanks everyone for joining
14:47:17 <hberaud> #endmeeting