| opendevreview | Merged openstack/releases master: Mention list of inactive projects in process doc https://review.opendev.org/c/openstack/releases/+/940974 | 11:51 |
|---|---|---|
| elodilles | reminder: weekly meeting starts in 30 mins | 13:30 |
| *** tkajinam is now known as Guest9129 | 13:39 | |
| elodilles | #startmeeting releaseteam | 14:00 |
| opendevmeet | Meeting started Fri Feb 14 14:00:32 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 armstrong | 14:00 |
| elodilles | #link https://etherpad.opendev.org/p/epoxy-relmgt-tracking | 14:00 |
| frickler | \o | 14:00 |
| ttx | o/ | 14:00 |
| elodilles | hello everyone o/ | 14:01 |
| kacperrh[m] | o/ | 14:01 |
| elodilles | (almost started the meeting on wrong channel :S | 14:01 |
| elodilles | ) | 14:01 |
| elodilles | we are at R-7 week, line 262 on the above linked tracking page | 14:01 |
| elodilles | let's start! | 14:02 |
| elodilles | #topic Review task completion | 14:02 |
| elodilles | 1st task was: | 14:02 |
| elodilles | Notify the Infrastructure team to generate an artifact signing key | 14:02 |
| elodilles | this happened already during last week's meeting | 14:02 |
| elodilles | fungi was pinged :) | 14:03 |
| fungi | yep | 14:03 |
| elodilles | 2nd task: | 14:03 |
| elodilles | Check with the Technical Committee to make sure Python runtimes have been determined for the next development cycle (elod) | 14:03 |
| fungi | i proded them last week and gouthamr got it underway | 14:03 |
| fungi | looks like it'll probably merge soon | 14:04 |
| elodilles | thanks, wanted to say that it happened without asking them as TC was proactive :) | 14:04 |
| elodilles | runtimes patch: https://review.opendev.org/c/openstack/governance/+/941141 | 14:04 |
| elodilles | yepp, hopefully this merges soon ^^^ | 14:04 |
| fungi | it was a takeaway from last week's release team meeting | 14:04 |
| elodilles | it looks good to me at least | 14:04 |
| elodilles | fungi: +1 | 14:04 |
| elodilles | and i've created the necessary patch for the zuul job templates | 14:05 |
| elodilles | zuul job templates patches: https://review.opendev.org/q/topic:2025.2 | 14:05 |
| fungi | thanks! | 14:05 |
| elodilles | i would appreciate reviews on these ^^^ | 14:05 |
| elodilles | np | 14:05 |
| elodilles | we need the 1st patch to land before we start branching stable/2025.1 | 14:06 |
| elodilles | some teams might want to start branching next week, though teams usually don't rush forward :X | 14:06 |
| elodilles | and that's all about the tasks | 14:07 |
| elodilles | any question or comment? | 14:07 |
| elodilles | looks not | 14:08 |
| elodilles | #topic Assign R-6 week tasks | 14:08 |
| elodilles | actually, all taken, if you look at the tracking page | 14:08 |
| elodilles | thanks ttx for chairing next week's meeting | 14:09 |
| elodilles | (i added my name to the library releases generating task, but if anyone wants to hijack it, then feel free to do that :)) | 14:09 |
| elodilles | #topic Review weekly countdown email | 14:10 |
| elodilles | #link https://etherpad.opendev.org/p/relmgmt-weekly-emails | 14:10 |
| elodilles | please review ^^^ | 14:10 |
| ttx | LGTM | 14:11 |
| frickler | +1 | 14:13 |
| elodilles | thanks! i'll send it some time after the meeting | 14:13 |
| elodilles | #topic Open Discussion | 14:14 |
| elodilles | any topic to raise here? | 14:14 |
| ttx | Nothing from me, calm week | 14:14 |
| elodilles | indeed | 14:15 |
| frickler | I created the wallaby eol patch matching content from victoria | 14:15 |
| fungi | i brought up in the tc meeting the desire to move emerging/inactive status into projects.yaml | 14:15 |
| elodilles | frickler: +1, will review that | 14:15 |
| frickler | not sure yet whether we'll also need to give it a full 4 weeks | 14:15 |
| fungi | there seemed to be consensus on the suggested improvement, but as it's not urgent it may be a few months before someone gets to it | 14:16 |
| frickler | elodilles: related, how are things progressing for the remaining victoria issues? | 14:16 |
| frickler | fungi: yeah, maybe some fresh TC member shows up after the election and picks this up ;) | 14:16 |
| elodilles | frickler: from my side, there is no need for the full 4 weeks, though for other unmaintainers maybe need some time (note that i think wallaby, xena, yoga, zed, 2023.1 could be proposed at the same time) | 14:17 |
| frickler | elodilles: well gmann said that they preferred to go step by step. I can also propose the next changes right away | 14:17 |
| elodilles | fungi: thanks for bringing the topic there, not urgent, indeed, we have ~half a year i guess :) | 14:18 |
| frickler | or maybe on monday rather | 14:18 |
| elodilles | frickler: didn't get there this week, but maybe after the meeting i'll fix some unmaintained gates | 14:18 |
| fungi | i got the impression the step-by-step preference was for actual eol finalization, not the proposing of eol | 14:18 |
| elodilles | frickler: ah, ACK, i see | 14:19 |
| elodilles | yeah, i feel the same as fungi says | 14:19 |
| fungi | so they could be proposed at the same time in separate changes, but plan to act on them with some delay between each | 14:19 |
| frickler | oh, maybe I misread that? so then I'll look into proposing those. or maybe cardoe wants to check whether following my notes would work | 14:19 |
| elodilles | fungi: +2 | 14:19 |
| fungi | or they could be proposed at different times, whatever's easier | 14:19 |
| frickler | #link https://etherpad.opendev.org/p/eol-unmaintained-branches | 14:20 |
| elodilles | but don't wait for 4 weeks after each patch, that would make the process quite long :S | 14:20 |
| frickler | that's where I track the changes and how I generated them | 14:20 |
| fungi | also remember that if/when 2023.1 goes eol, so too does 2023.2 (not-slurp) | 14:21 |
| elodilles | thanks frickler for creating that pad +1 | 14:21 |
| frickler | fungi: well 2023.2 goes eol 4 weeks after 2025.1 is released anyway | 14:21 |
| elodilles | fungi: well, 2023.2 might go EOL earlier than 2023.1 | 14:22 |
| elodilles | as far as I understood | 14:22 |
| elodilles | as frickler says | 14:22 |
| fungi | ah, yep | 14:22 |
| fungi | just can't go eol any later than 2023.1 does | 14:22 |
| frickler | we may also eol 2023.1 repos at the same time, though, if no opt-in happens | 14:23 |
| elodilles | yep. according to the unmaintained resolutions | 14:23 |
| elodilles | though, note that when a project's 2023.1 branch goes to EOL, then all its former branches (zed, yoga, etc) need to go to EOL | 14:24 |
| elodilles | if not EOL already | 14:24 |
| fungi | yes, so if someone wants to be caretaker for those older unmaintained branches they have to at least find a volunteer for any newer than that | 14:25 |
| elodilles | +1 | 14:25 |
| elodilles | thanks frickler for bringing this up. as i said, i'm planning to review the wallaby-eol patch | 14:26 |
| elodilles | anything else to discuss? | 14:26 |
| elodilles | based on the silence i think we reached the end of the meeting :) | 14:29 |
| elodilles | thanks for participating o/ | 14:29 |
| elodilles | #endmeeting | 14:29 |
| opendevmeet | Meeting ended Fri Feb 14 14:29:37 2025 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 14:29 |
| opendevmeet | Minutes: https://meetings.opendev.org/meetings/releaseteam/2025/releaseteam.2025-02-14-14.00.html | 14:29 |
| opendevmeet | Minutes (text): https://meetings.opendev.org/meetings/releaseteam/2025/releaseteam.2025-02-14-14.00.txt | 14:29 |
| opendevmeet | Log: https://meetings.opendev.org/meetings/releaseteam/2025/releaseteam.2025-02-14-14.00.log.html | 14:29 |
| opendevreview | Sahid Orentino Ferdjaoui proposed openstack/releases master: os-ken: release version 3.0.0 https://review.opendev.org/c/openstack/releases/+/941356 | 15:55 |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!