14:00:04 <ttx> #startmeeting releaseteam
14:00:04 <opendevmeet> Meeting started Fri Feb  9 14:00:04 2024 UTC and is due to finish in 60 minutes.  The chair is ttx. Information about MeetBot at http://wiki.debian.org/MeetBot.
14:00:04 <opendevmeet> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
14:00:04 <opendevmeet> The meeting name has been set to 'releaseteam'
14:00:12 <ttx> Ping list: elod frickler armstrong
14:00:23 <ttx> #link https://etherpad.opendev.org/p/caracal-relmgt-tracking
14:00:38 <ttx> around line ~260
14:00:52 <elodilles> o/
14:01:17 <elodilles> R-8 shocking :-o
14:01:17 <frickler> \o
14:01:23 <ttx> Time flies !
14:01:34 <ttx> Alright, we have quorum :)
14:01:41 <ttx> #topic Review task completion
14:01:52 <ttx> 1/     Make sure the next development series name has been added to the data/series_status.yaml file (elod)
14:02:37 <elodilles> it's there: https://releases.openstack.org/
14:02:55 <ttx> 2/    Send countdown email (ttx)
14:03:03 <ttx> that will be done after this meeting
14:03:07 <hberaud> o/
14:03:28 <ttx> #topic Assign next week tasks
14:04:03 <ttx> fungi: Notify the Infrastructure team to generate an artifact signing key (but not replace the current one yet), and begin the attestation process
14:04:08 <elodilles> as i see most if the team is away next week :-o
14:04:10 <ttx> should we consider yourself notified?
14:04:19 <fungi> yep
14:04:22 <fungi> i can take care of it
14:04:32 <ttx> yay, task done!
14:04:46 <ttx> All tasks assigned
14:04:49 <elodilles> :]
14:04:52 <ttx> Thanks elodilles !
14:05:04 <ttx> #topic Review countdown email
14:05:15 <ttx> #link https://etherpad.opendev.org/p/relmgmt-weekly-emails
14:05:27 <ttx> I actually had one question around the cycle highlights
14:05:41 <fungi> yeah, starting at line 45 in the draft
14:05:47 <ttx> fungi: should we direct drafters to yuo for advice, rather than kendall?
14:06:25 <fungi> updated
14:06:27 <ttx> ok, you can rephrase that sentence however you are comfortable
14:06:36 <ttx> wfm
14:06:48 <elodilles> about cycle highlight
14:07:00 <elodilles> i think there should be a patch somewhere...
14:07:03 <elodilles> let me find it
14:07:08 <hberaud> may we can put a reminder about the oslo ff next week in the upcoming deadlines?
14:07:38 <elodilles> hberaud: +1
14:07:42 <hberaud> that concern everyone
14:07:45 <ttx> Please add
14:08:13 <ttx> maybe on line 27
14:08:18 <elodilles> there it is: https://review.opendev.org/c/openstack/releases/+/906351
14:08:23 <elodilles> cycle highlight ^^^
14:08:57 <ttx> I put in my review already !
14:09:14 <elodilles> ttx: so it changes the deadline in the mail then
14:09:43 <ttx> OK, would be good to approve it then
14:09:49 <ttx> so that doc is up to date
14:10:03 <frickler> done
14:11:02 <ttx> OK adding oslo thing
14:11:24 <elodilles> thx o/
14:11:40 <elodilles> (i've updated the cycle highlight section of the mail)
14:11:40 <ttx> see line 28
14:12:10 <hberaud> wfm
14:12:22 <ttx> I'll propose an update for the template for that one
14:12:28 <ttx> since we did so many fixes
14:12:39 <hberaud> thanks
14:12:46 <frickler> https://review.opendev.org/c/openstack/releases/+/905154 seems also pretty urgent if nominations should start next week?
14:12:55 <frickler> should those also be mentioned in the mail?
14:13:20 <elodilles> ttx: thanks in advance o/
14:13:51 <ttx> frickler: I think it's a bit outside teh release team's thing
14:14:16 <ttx> We can't really supplant TC communications
14:14:34 <frickler> if it is outside of release team, why are those dates in the release schedule?
14:15:06 <ttx> I was not a fan, but we allow non-releasy mentions on the schedule
14:15:18 <ttx> like events and elections
14:15:43 <fungi> ideally the election officials or another tc representative/delegate will be sending a separate announcement about elections
14:15:56 <ttx> I like my release countdown emails very reproducible
14:16:08 <ttx> keeps teh amount of work doing them pretty low
14:16:16 <frickler> the mail mentions the PTG, so I think ppl could expect similarly important events like elections to be mentioned there, too
14:16:27 <frickler> just seeing this from a reader perspective
14:16:36 <ttx> the more we add custom reminder content, the more work it is
14:17:21 <ttx> I'm fine adding it (not in the template but in this particular email) if someone wants it
14:17:28 <ttx> It's already long though.
14:18:11 <fungi> would just tacking a line onto the "upcoming deadlines" section at the end be enough?
14:18:18 <elodilles> since we haven't been adding it i don't miss it either, tbh
14:18:25 <opendevreview> Merged openstack/releases master: Fix cycle highlight deadline  https://review.opendev.org/c/openstack/releases/+/906351
14:18:26 <ttx> yeah that would work
14:18:30 <elodilles> fungi: +1
14:18:58 <frickler> yeah, I was only thinking about a line there, sorry if I was implying something else
14:19:13 <fungi> seems a nice middle ground between taking responsibility for reminding folks and simply acknowledging stuff that's listed on the schedule
14:19:40 <ttx> works for me.. please add
14:21:04 <ttx> all good for me
14:21:30 <frickler> does it start at the beginning of the week or the end? I'm not sure
14:22:01 <ttx> frickler: a good example of why we are not the best at communicatnig that kind of info :)
14:22:02 <elodilles> LGTM
14:23:27 <fungi> frickler: https://review.opendev.org/905152 indicates nominations are expected to start 2024-02-14T23:45
14:23:36 <fungi> but keep in mind that change hasn't merged
14:23:44 <ttx> hmm, the dates are not even official...
14:24:04 <elodilles> let's just skip it for now :/
14:24:16 <ttx> i don;t think we should announce dates that the TC has not validated, yes
14:24:37 <elodilles> i mean, there should be and there will be a clear communication for the whole community, this is mostly for PTLs and release liaisons
14:24:39 <frickler> hmm, good point, bad also bad that this is only a week away
14:24:49 <fungi> there seems to be some unconfirmed concern raised in comments that it lands right on top of lunar new year
14:24:54 <ttx> yes we should tell th TC this is a bit late
14:25:05 <frickler> JayF: tonyb: ^^
14:25:11 <ttx> (or early)
14:25:47 <ttx> For now let's remove it. We can mention it next week (like when the nomination period closes)
14:25:49 <frickler> anyway, dropped the line from the mail again
14:25:58 <ttx> ok all set
14:26:01 <elodilles> thanks
14:26:07 <ttx> #topic Open Discussion
14:26:24 <ttx> anything anyone?
14:26:50 <elodilles> maybe we haven't officially say welcome to frickler :)
14:26:59 <frickler> \o/ hello
14:27:07 <elodilles> so welcome in the relmgt team o/
14:27:10 <ttx> No cake, no welcome !
14:27:14 <elodilles> :D
14:27:29 <frickler> I also proposed to be added as release liaison, if someone still hasn't seen that https://review.opendev.org/c/openstack/governance/+/907350
14:27:44 <ttx> frickler: thanks for officially joining the crazy team that tries to keep openstack released !
14:28:14 <elodilles> yepp, thanks, also for the work you already started o/
14:29:00 <ttx> Always good to have fresh eyes and people with different styles of itches to scratch
14:29:11 <elodilles> #info welcome frickler in the Release Management team \o/
14:29:27 <elodilles> so we have a highlight as well ^^^ :)
14:29:43 <ttx> OK, if nothing else, I'll close now...
14:29:51 <frickler> just a moment
14:29:57 * ttx holds
14:30:01 <frickler> some question about the open eol/eom patches
14:30:24 <frickler> most are waiting for known-slow to inactive PTLs
14:30:50 <frickler> we already overrode those for projects that are officially marked inactive
14:31:05 <elodilles> for inactive ones i usually add PTL-Approved manually with explanations. did i miss any such repo?
14:31:09 <frickler> but maybe we have some way to make better progress for the remainder, too
14:31:34 <elodilles> i usually ping them via IRC or worst case via mail
14:31:41 <fungi> in positive news, recent deletions have lowered the stable branch failures to around 6-8 notifications a day now (granted much of that may be due to an increased number of projects whose zuul configs are in an untestable error state now)
14:31:57 <elodilles> i did some pinging, but i'm a bit lagging behind this week
14:32:18 <frickler> yes, the number of zuul errors did increase instead of decreasing as I had hoped
14:32:21 <elodilles> fungi: yepp, i wanted to highlight that to you, too ;)
14:32:32 <elodilles> frickler: :-o
14:32:55 <elodilles> fungi: (i mean, about the less mail)
14:33:22 <fungi> no need to tell me, i notice it every day when i check my e-mail ;)
14:33:34 <elodilles> :)
14:33:38 <frickler> ok, so just keep pinging then, it is?
14:34:03 <fungi> the tc can rule that it's okay to go forward in the absence of a response
14:34:27 <elodilles> frickler: i don't really want force merge without PTL approval, but if we want that then we can set a deadline if you think
14:34:47 <fungi> chasing after absent project leaders is not a productive use of anyone's time
14:34:53 <frickler> I want to close these eol things out and then proceed to xena etc.
14:35:10 <elodilles> frickler: ++
14:35:50 <frickler> ok, so I'll check what's left when I'm back after next week and then take this up with the TC
14:36:04 <elodilles> frickler: ACK, thanks
14:36:14 <elodilles> and I'll do the pingings next week
14:36:38 <frickler> cool. that's all from me then, thx
14:36:58 <ttx> Alright! Last call...
14:37:01 <elodilles> thanks too o/
14:37:45 <ttx> #endmeeting