elodilles | reminder: weekly meeting will start in a bit more than 30 minutes | 13:27 |
---|---|---|
elodilles | #startmeeting releaseteam | 14:00 |
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 |
opendevmeet | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 14:00 |
opendevmeet | The meeting name has been set to 'releaseteam' | 14:00 |
elodilles | Ping list: release-team elod | 14:01 |
elodilles | #link https://etherpad.opendev.org/p/flamingo-relmgt-tracking | 14:01 |
elodilles | we are at line 276 | 14:01 |
elodilles | o/ | 14:01 |
frickler | \o | 14:02 |
elodilles | hi frickler o/ | 14:02 |
elodilles | i see that ttx is on holiday | 14:02 |
elodilles | so let's start quickly | 14:03 |
elodilles | #topic Review task completion | 14:03 |
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 |
elodilles | fungi notified in meeting | 14:03 |
elodilles | so this is done ^^^ :) | 14:03 |
elodilles | next one: | 14:03 |
elodilles | ' Check with the Technical Committee (frickler)' | 14:03 |
fungi | #link https://review.opendev.org/957466 Publish the 2026.1/Gazpacho key for future use | 14:03 |
fungi | already up for review even | 14:04 |
elodilles | oh, nice, this is the artifact signing key | 14:04 |
elodilles | though it's still WIP | 14:04 |
fungi | yeah, just to keep it from merging so soon | 14:04 |
fungi | but it's ready to go when the time comes now | 14:05 |
elodilles | thanks fungi o/ | 14:05 |
elodilles | added myself as reviewer, but feel free to ping me if i forget about it o:) | 14:06 |
frickler | it also doesn't hurt to publish it now already, or does it? | 14:06 |
frickler | for the python reqs there is https://review.opendev.org/c/openstack/governance/+/957199 | 14:07 |
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 |
elodilles | frickler: nice, so there's the runtime patch \o/ | 14:08 |
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:09 |
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 |
fungi | but i would wait until closer to the release at least | 14:10 |
elodilles | fungi: +1 | 14:10 |
elodilles | frickler: anything else for the runtimes / zuul job templates task? | 14:11 |
frickler | I don't think so, changing the templates only makes sense when the runtimes are agreed upon | 14:13 |
elodilles | ACK | 14:14 |
elodilles | yepp, this probably will take some time as i said | 14:14 |
elodilles | we might need to revisit this task at a later point | 14:14 |
elodilles | to assure we have all the supported runtimes and zuul job templates defined | 14:15 |
elodilles | i'll add a task for this to some later week's task list as a reminder | 14:16 |
elodilles | anyway, let's move on | 14:16 |
elodilles | next task was: | 14:16 |
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 |
elodilles | i've generated the DNM patches: | 14:17 |
elodilles | #link https://review.opendev.org/q/topic:release-health-check-flamingo | 14:17 |
elodilles | or more like: | 14:17 |
elodilles | #link https://review.opendev.org/q/topic:release-health-check-flamingo+is:open | 14:17 |
elodilles | these are the repos with failing gates ^^^ | 14:17 |
elodilles | i'll send a reminder mail with [teams] in subject to ML about their unhealthy gate | 14:18 |
elodilles | (vitrage, venus, ironic, heat, cinder, magnum, tacker) | 14:19 |
elodilles | oh, and the process documenting patch: https://review.opendev.org/c/openstack/releases/+/855663 | 14:20 |
elodilles | actually it misses one point as i don't have a nice solution to that yet: | 14:20 |
elodilles | how to get the last merged change's merging time | 14:21 |
elodilles | gerrit api only gives back the commit's timestamp, that can result to false dates :/ | 14:21 |
elodilles | i mean, there's no 'merged_at' or similar timestamp | 14:22 |
elodilles | at least i'm not aware of that | 14:22 |
elodilles | otherwise, that process is something like that that is documented now in my patch | 14:22 |
fungi | elodilles: i do some gymnastics in opendev/engagement and openstack/election scripts for that | 14:23 |
elodilles | oh :-o | 14:23 |
elodilles | then i'll take a look there! | 14:23 |
fungi | but in short, it's check for change updates in a given time window, then iterate through and check their submit times | 14:23 |
fungi | requires post-processing | 14:24 |
fungi | not a singular query sadly | 14:24 |
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 |
elodilles | but thanks for the tip, i'll search for that :) | 14:25 |
fungi | you can fetch all the data in one query, but you need to look through the returned json | 14:25 |
elodilles | +1 | 14:25 |
fungi | well, potentially one query if you're not expecting more results than fit in one "page" | 14:25 |
fungi | (the gerrit rest api does pagination) | 14:26 |
elodilles | it's strange that it cannot be queried easily as gerrit has the info on it's UI | 14:26 |
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:26 |
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 |
elodilles | yeah, no need for sharp accuracy, just something better then random dates o:) | 14:27 |
elodilles | s/then/than/ | 14:27 |
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 |
fungi | (or maybe it's the oldest in the requested date range, i forget. one of those) | 14:28 |
elodilles | thanks! noted! | 14:28 |
elodilles | if nothing else about projects with failing gates, then let's move on | 14:30 |
elodilles | #topic Assign R-6 week tasks | 14:31 |
fungi | elodilles: oh, https://review.opendev.org/Documentation/user-search.html has a mergedbefore and mergedafter filter now | 14:31 |
fungi | if that helps | 14:31 |
elodilles | fungi: sounds awesome! i'll experiment with the api then! thanks! | 14:32 |
fungi | yw | 14:32 |
elodilles | tasks are assigned, so we can proceed to the next topic | 14:33 |
elodilles | #topic Review weekly countdown email | 14:33 |
elodilles | #link https://etherpad.opendev.org/p/relmgmt-weekly-emails | 14:33 |
elodilles | please review ^^^ | 14:33 |
frickler | lgtm | 14:38 |
elodilles | thanks, will send it some time after the meeting today | 14:39 |
elodilles | #topic Open Discussion | 14:39 |
elodilles | anything to discuss? | 14:39 |
elodilles | silence. OK, then let's end the meeting o:) | 14:45 |
elodilles | thanks for participating o/ | 14:46 |
elodilles | #endmeeting | 14:46 |
opendevmeet | Meeting ended Fri Aug 15 14:46:13 2025 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 14:46 |
opendevmeet | Minutes: https://meetings.opendev.org/meetings/releaseteam/2025/releaseteam.2025-08-15-14.00.html | 14:46 |
opendevmeet | Minutes (text): https://meetings.opendev.org/meetings/releaseteam/2025/releaseteam.2025-08-15-14.00.txt | 14:46 |
opendevmeet | Log: https://meetings.opendev.org/meetings/releaseteam/2025/releaseteam.2025-08-15-14.00.log.html | 14:46 |
fungi | elodilles: in https://review.opendev.org/c/openstack/election/+/957549 i'm testing possible efficiency gains by switching from after/before to mergedafter/mergedbefore | 14:47 |
elodilles | fungi: yepp, the query works fine with 'mergedafter' so it should be easy to prepare a simple command for it \o/ | 16:15 |
Generated by irclog2html.py 4.0.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!