14:00:35 <elodilles> #startmeeting releaseteam
14:00:35 <opendevmeet> Meeting started Fri Aug 15 14:00:35 2025 UTC and is due to finish in 60 minutes.  The chair is elodilles. Information about MeetBot at http://wiki.debian.org/MeetBot.
14:00:35 <opendevmeet> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
14:00:35 <opendevmeet> The meeting name has been set to 'releaseteam'
14:01:01 <elodilles> Ping list: release-team elod
14:01:09 <elodilles> #link https://etherpad.opendev.org/p/flamingo-relmgt-tracking
14:01:32 <elodilles> we are at line 276
14:01:37 <elodilles> o/
14:02:32 <frickler> \o
14:02:49 <elodilles> hi frickler o/
14:02:53 <elodilles> i see that ttx is on holiday
14:03:00 <elodilles> so let's start quickly
14:03:13 <elodilles> #topic Review task completion
14:03:24 <elodilles> '    Notify the Infrastructure team to generate an artifact signing key (but not replace the current one yet), and begin the attestation process (ttx)'
14:03:31 <elodilles> fungi notified in meeting
14:03:41 <elodilles> so this is done ^^^ :)
14:03:46 <elodilles> next one:
14:03:53 <elodilles> '    Check with the Technical Committee (frickler)'
14:03:58 <fungi> #link https://review.opendev.org/957466 Publish the 2026.1/Gazpacho key for future use
14:04:03 <fungi> already up for review even
14:04:23 <elodilles> oh, nice, this is the artifact signing key
14:04:32 <elodilles> though it's still WIP
14:04:46 <fungi> yeah, just to keep it from merging so soon
14:05:05 <fungi> but it's ready to go when the time comes now
14:05:18 <elodilles> thanks fungi o/
14:06:03 <elodilles> added myself as reviewer, but feel free to ping me if i forget about it o:)
14:06:43 <frickler> it also doesn't hurt to publish it now already, or does it?
14:07:32 <frickler> for the python reqs there is https://review.opendev.org/c/openstack/governance/+/957199
14:08:22 <elodilles> frickler: i guess not, but we are not in a hurry with the signing key as we still have ~1.5 months till the new cycle to start
14:08:50 <elodilles> frickler: nice, so there's the runtime patch \o/
14:09:54 <elodilles> it usually takes some rounds of discussions until the supported runtimes are agreed on, but it's good that it's started already
14:10:01 <fungi> frickler: yeah the releases change with the key info can merge sooner, it's only the project-config change where timing is sensitive in order to avoid needing to revise the use date listed there
14:10:15 <fungi> but i would wait until closer to the release at least
14:10:26 <elodilles> fungi: +1
14:11:50 <elodilles> frickler: anything else for the runtimes / zuul job templates task?
14:13:50 <frickler> I don't think so, changing the templates only makes sense when the runtimes are agreed upon
14:14:10 <elodilles> ACK
14:14:26 <elodilles> yepp, this probably will take some time as i said
14:14:46 <elodilles> we might need to revisit this task at a later point
14:15:29 <elodilles> to assure we have all the supported runtimes and zuul job templates defined
14:16:07 <elodilles> i'll add a task for this to some later week's task list as a reminder
14:16:43 <elodilles> anyway, let's move on
14:16:51 <elodilles> next task was:
14:17:01 <elodilles> '    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?) Task is lacking documentation in PROCESS doc'
14:17:24 <elodilles> i've generated the DNM patches:
14:17:33 <elodilles> #link https://review.opendev.org/q/topic:release-health-check-flamingo
14:17:36 <elodilles> or more like:
14:17:41 <elodilles> #link https://review.opendev.org/q/topic:release-health-check-flamingo+is:open
14:17:59 <elodilles> these are the repos with failing gates ^^^
14:18:35 <elodilles> i'll send a reminder mail with [teams] in subject to ML about their unhealthy gate
14:19:23 <elodilles> (vitrage, venus, ironic, heat, cinder, magnum, tacker)
14:20:01 <elodilles> oh, and the process documenting patch: https://review.opendev.org/c/openstack/releases/+/855663
14:20:35 <elodilles> actually it misses one point as i don't have a nice solution to that yet:
14:21:03 <elodilles> how to get the last merged change's merging time
14:21:48 <elodilles> gerrit api only gives back the commit's timestamp, that can result to false dates :/
14:22:07 <elodilles> i mean, there's no 'merged_at' or similar timestamp
14:22:15 <elodilles> at least i'm not aware of that
14:22:51 <elodilles> otherwise, that process is something like that that is documented now in my patch
14:23:30 <fungi> elodilles: i do some gymnastics in opendev/engagement and openstack/election scripts for that
14:23:42 <elodilles> oh :-o
14:23:52 <elodilles> then i'll take a look there!
14:23:55 <fungi> but in short, it's check for change updates in a given time window, then iterate through and check their submit times
14:24:06 <fungi> requires post-processing
14:24:32 <fungi> not a singular query sadly
14:25:00 <elodilles> yeah, i hoped to some easy querying of a timestamp in a json, but feared that some more complex workaround is needed o:)
14:25:21 <elodilles> but thanks for the tip, i'll search for that :)
14:25:32 <fungi> you can fetch all the data in one query, but you need to look through the returned json
14:25:43 <elodilles> +1
14:25:55 <fungi> well, potentially one query if you're not expecting more results than fit in one "page"
14:26:09 <fungi> (the gerrit rest api does pagination)
14:26:38 <elodilles> it's strange that it cannot be queried easily as gerrit has the info on it's UI
14:26:45 <fungi> dealing with mult-page responses gets tricky too if you're trying to avoid gaps, but probably not something you need for this
14:27:23 <fungi> i think the problem is that there's no query filter for submit date, just modified date. but maybe the query language has added that feature more recently than the last time i checked
14:27:27 <elodilles> yeah, no need for sharp accuracy, just something better then random dates o:)
14:27:37 <elodilles> s/then/than/
14:28:10 <fungi> the election tooling returns the most recent merged change in a repository for a specific user, same code could be adapted easily i expect
14:28:39 <fungi> (or maybe it's the oldest in the requested date range, i forget. one of those)
14:28:46 <elodilles> thanks! noted!
14:30:29 <elodilles> if nothing else about projects with failing gates, then let's move on
14:31:48 <elodilles> #topic Assign R-6 week tasks
14:31:49 <fungi> elodilles: oh, https://review.opendev.org/Documentation/user-search.html has a mergedbefore and mergedafter filter now
14:31:56 <fungi> if that helps
14:32:28 <elodilles> fungi: sounds awesome! i'll experiment with the api then! thanks!
14:32:43 <fungi> yw
14:33:19 <elodilles> tasks are assigned, so we can proceed to the next topic
14:33:34 <elodilles> #topic Review weekly countdown email
14:33:40 <elodilles> #link https://etherpad.opendev.org/p/relmgmt-weekly-emails
14:33:44 <elodilles> please review ^^^
14:38:41 <frickler> lgtm
14:39:24 <elodilles> thanks, will send it some time after the meeting today
14:39:40 <elodilles> #topic Open Discussion
14:39:48 <elodilles> anything to discuss?
14:45:53 <elodilles> silence. OK, then let's end the meeting o:)
14:46:04 <elodilles> thanks for participating o/
14:46:13 <elodilles> #endmeeting