| *** ralonsoh_ is now known as ralonsoh | 06:55 | |
| ttx | frickler: if I remember correctly, there was a comment from fungi saying that it could merge earlier but then they would have to adjust the date on another patch. That's why I backpedaled | 07:01 |
|---|---|---|
| ttx | If that's not really an issue, I have no issue with it merging now | 07:02 |
| frickler | ttx: iiuc that would only come into effect in case the actual activation of the key would need to be delayed (https://review.opendev.org/c/openstack/project-config/+/927031), but that hopefully is unlikely. so I'm approving the release change now | 07:05 |
| opendevreview | Merged openstack/releases master: Publish the 2025.1/Epoxy key for future use https://review.opendev.org/c/openstack/releases/+/927030 | 07:19 |
| *** bauzas_ is now known as bauzas | 07:46 | |
| *** ralonsoh_ is now known as ralonsoh | 08:59 | |
| opendevreview | Merged openstack/releases master: Release blazar-dashboard RC1 for 2024.2 Dalmatian https://review.opendev.org/c/openstack/releases/+/928515 | 09:49 |
| opendevreview | Merged openstack/releases master: [OpenStack-Ansible] Add Dalmatian cycle highlights https://review.opendev.org/c/openstack/releases/+/928884 | 09:54 |
| opendevreview | Merged openstack/releases master: Release manila RC1 for 2024.2 Dalmatian https://review.opendev.org/c/openstack/releases/+/928536 | 11:02 |
| opendevreview | Merged openstack/releases master: Release tacker-horizon RC1 for 2024.2 Dalmatian https://review.opendev.org/c/openstack/releases/+/928561 | 11:02 |
| opendevreview | Merged openstack/releases master: Release neutron RC1 for 2024.2 Dalmatian https://review.opendev.org/c/openstack/releases/+/928550 | 11:08 |
| opendevreview | Merged openstack/releases master: Release adjutant RC1 for 2024.2 Dalmatian https://review.opendev.org/c/openstack/releases/+/928509 | 11:08 |
| opendevreview | Merged openstack/releases master: Release skyline-apiserver RC1 for 2024.2 Dalmatian https://review.opendev.org/c/openstack/releases/+/928557 | 11:08 |
| opendevreview | Merged openstack/releases master: Release blazar RC1 for 2024.2 Dalmatian https://review.opendev.org/c/openstack/releases/+/928517 | 11:08 |
| opendevreview | Merged openstack/releases master: Release blazar-nova RC1 for 2024.2 Dalmatian https://review.opendev.org/c/openstack/releases/+/928516 | 11:08 |
| opendevreview | Merged openstack/releases master: Release skyline-console RC1 for 2024.2 Dalmatian https://review.opendev.org/c/openstack/releases/+/928558 | 11:09 |
| fungi | ttx: frickler: yeah it's fine to merge the fingerprint/link documentation for the new key at any time. if the corresponding project-config change doesn't merge on the predicted date, we'll adjust the end/start dates for the keys on the releases site | 11:45 |
| opendevreview | Elod Illes proposed openstack/releases master: Release placement RC1 for 2024.2 Dalmatian https://review.opendev.org/c/openstack/releases/+/928556 | 12:07 |
| frickler | elodilles: fwiw I would vote to stop doing ptl-approved overrides for ptl's that are inactive, I would rather not release such projects. I was planning to discuss this in the meeting, but I see that you started to place those votes already. cf. also the discussion in this week's TC meeting | 12:13 |
| opendevreview | Elod Illes proposed openstack/releases master: Release designate RC1 for 2024.2 Dalmatian https://review.opendev.org/c/openstack/releases/+/928525 | 12:21 |
| opendevreview | Elod Illes proposed openstack/releases master: Release aodh RC1 for 2024.2 Dalmatian https://review.opendev.org/c/openstack/releases/+/928513 | 12:26 |
| elodilles | frickler: this is a bit tricky, as we say that deliverables, listed under deliverables/<series>, will be released | 12:28 |
| elodilles | but let's discuss this on the meeting :) | 12:29 |
| frickler | we also say that they will be supported for 18 months, yes, but if nobody is around to even approve releases, that's not going to happen either | 12:30 |
| opendevreview | Elod Illes proposed openstack/releases master: Release placement RC1 for 2024.2 Dalmatian https://review.opendev.org/c/openstack/releases/+/928556 | 12:33 |
| ttx | o/ | 13:00 |
| ttx | #startmeeting releaseteam | 13:00 |
| opendevmeet | Meeting started Fri Sep 13 13:00:38 2024 UTC and is due to finish in 60 minutes. The chair is ttx. Information about MeetBot at http://wiki.debian.org/MeetBot. | 13:00 |
| opendevmeet | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 13:00 |
| opendevmeet | The meeting name has been set to 'releaseteam' | 13:00 |
| elodilles | o/ | 13:00 |
| ttx | Ping list: release-team elod armstrong | 13:00 |
| ttx | Our agenda for today is at https://etherpad.opendev.org/p/dalmatian-relmgt-tracking -- down to line 390 or so | 13:01 |
| frickler | \o | 13:01 |
| ttx | #topic Review task completion | 13:01 |
| ttx | - Process any remaining library branching exception. (all) | 13:02 |
| ttx | #link https://review.opendev.org/q/topic:dalmatian-stable-branches+is:open | 13:02 |
| ttx | Looks like two leftovers | 13:02 |
| ttx | Should we bypass PTL-APPROVED and just merge those? i can do that | 13:03 |
| elodilles | yes, we did that for some of the brancing patches as well, so let's do that | 13:03 |
| frickler | as mentioned before the meeting, I'd prefer to stop doing that. but I also won't block you | 13:04 |
| ttx | frickler: at this point we should proceed as usual, but yes that would be a good discussion to have at PTG regarding future releases | 13:05 |
| frickler | see also the longish discussion at https://meetings.opendev.org/meetings/tc/2024/tc.2024-09-10-18.00.log.html#l-56 | 13:05 |
| elodilles | yeah that is two case actually: 1) inactive projects 2) release liaisons rely on 'if no response comes, we proceed with the release' && forgot about the release patches | 13:06 |
| ttx | I wrote down those two exceptions in the health dashboard | 13:06 |
| elodilles | ACK | 13:07 |
| ttx | #topic Assign R-2 week tasks | 13:07 |
| ttx | oops | 13:07 |
| ttx | #undo | 13:07 |
| opendevmeet | Removing item from minutes: #topic Assign R-2 week tasks | 13:07 |
| ttx | - On the Monday, generate release requests for all deliverables that have do not have a suitable candidate yet. (elod) | 13:07 |
| ttx | Branch devstack-plugin-* deliverables https://review.opendev.org/c/openstack/releases/+/928504 | 13:08 |
| elodilles | this is merged \o/ | 13:09 |
| ttx | cycle-with-intermediary deliverables https://review.opendev.org/c/openstack/releases/+/928505 | 13:09 |
| elodilles | released, too \o/ | 13:09 |
| ttx | cycle-with-rc that are not trailing deliverables and that have not done a RC1 yet https://review.opendev.org/q/topic:dalmatian-rc1-deadline | 13:09 |
| elodilles | more than half of them released ^^^ \o/ | 13:10 |
| elodilles | some -1 feedback from teams | 13:10 |
| elodilles | so we are waiting for updates there | 13:10 |
| ttx | For the remaining ones should we wait to release on Monday rather than Friday? | 13:10 |
| elodilles | i've also -1'd some repos that have broken gates :( | 13:10 |
| ttx | I can do the +2a on Monday | 13:10 |
| elodilles | ttx: i'm OK with that | 13:11 |
| elodilles | better on Monday than on Friday :) | 13:11 |
| frickler | at least zun seems to need to adapt to sqla 2.0, I can't see how that would happen short term | 13:11 |
| elodilles | :S | 13:11 |
| elodilles | (these are the repos with broken gates: https://review.opendev.org/q/topic:release-health-check-cwrc-dalmatian+is:open ) | 13:12 |
| ttx | ok I added a specific Monday task to remember it | 13:12 |
| elodilles | ++ | 13:12 |
| ttx | That leads us to: | 13:13 |
| ttx | #topic Assign R-2 week tasks | 13:13 |
| opendevreview | Merged openstack/releases master: [zun] Create 2024.2 branch for client and non-client libs https://review.opendev.org/c/openstack/releases/+/928421 | 13:17 |
| opendevreview | Merged openstack/releases master: [trove] Release version 8.6.0 for dalmatian and create 2024.2 branch https://review.opendev.org/c/openstack/releases/+/927937 | 13:17 |
| ttx | elodilles: I see storlets in your broken gate list but it does not seem to have resulted in a RC1 blocker | 13:19 |
| ttx | probably released as intermendiary, I guess | 13:19 |
| elodilles | hmm, let me check | 13:19 |
| ttx | Otherwise all tasks assigned | 13:19 |
| frickler | iirc tkajinam fixed it? | 13:19 |
| ttx | ah that's a possibility yes | 13:20 |
| frickler | hmm, no, still working on it https://review.opendev.org/c/openstack/storlets/+/929210 | 13:20 |
| elodilles | i don't see a release patch either :S | 13:20 |
| elodilles | i'll create an RC1 patch for that then | 13:21 |
| ttx | hmm, it's there already | 13:21 |
| frickler | this morning we saw it was broken by osc 7.1.0, cf. https://bugs.launchpad.net/python-openstackclient/+bug/2080600 | 13:21 |
| ttx | https://review.opendev.org/c/openstack/releases/+/928560 | 13:22 |
| ttx | storlets RC1 successful merge ^ | 13:22 |
| elodilles | ah, my bad, sry :S | 13:23 |
| frickler | might have been my bad, too, for not verifying gate status | 13:23 |
| elodilles | anyway, so that means we need an RC2 probably for storlets, right? | 13:23 |
| frickler | likely yes | 13:24 |
| frickler | and very likely also yet another OSC release | 13:24 |
| ttx | I itemized all the RC1 leftovers so that we can track them separately | 13:24 |
| elodilles | thanks ttx | 13:25 |
| ttx | should we add a task to track that storlets RC2 need? | 13:25 |
| elodilles | yes, that's a good idea | 13:25 |
| ttx | added | 13:25 |
| elodilles | thx | 13:25 |
| ttx | OK task allocation all set | 13:26 |
| ttx | #topic Review countdown email for week R-2 | 13:26 |
| ttx | #link https://etherpad.opendev.org/p/relmgmt-weekly-emails | 13:26 |
| elodilles | mail lgtm | 13:27 |
| ttx | OK, I will send it shortly after meeting | 13:27 |
| elodilles | (added some '2025.1' o:) | 13:27 |
| ttx | #topic Open Discussion | 13:28 |
| ttx | - How to deploy and test https://review.opendev.org/c/openstack/releases/+/929126 | 13:28 |
| ttx | So this is mostly untested, but looks safe on the surface | 13:28 |
| ttx | we could do a controlled merge and see | 13:29 |
| * frickler suggests to test in production | 13:29 | |
| ttx | Sounds like a great idea! | 13:29 |
| frickler | we should be able to rerun the failed swift announcement as a test case | 13:29 |
| elodilles | yes, merge 1 release patch and see what happens | 13:29 |
| ttx | how could we just rerun the announcement? | 13:30 |
| ttx | I'm fine with merging it on Monday and then approving one of the RC1 patches to see | 13:30 |
| elodilles | sounds OK to me, too | 13:30 |
| frickler | ah, I was wrong, this was the last job in the buildset, not the first one https://zuul.opendev.org/t/openstack/buildset/61debe91b25941f0be00f4239fa66d10 | 13:31 |
| frickler | then test with a new release it is | 13:31 |
| elodilles | +1 | 13:31 |
| frickler | do we ignore the missing release announcement or do you think it should be sent manually? | 13:32 |
| ttx | I have to check if the RC1 release announcement would actually trigger enough of the new code | 13:32 |
| ttx | I'd be fine with sending it manually | 13:32 |
| elodilles | does release-test trigger a release announcement? | 13:32 |
| elodilles | if yes, then we can try with that as well | 13:33 |
| frickler | at least it shouldn't hurt to run one release-test release first, ack | 13:33 |
| frickler | sorry gotta step away for a bit, will check back later | 13:35 |
| ttx | Hmm, I can;t find any run of announce-release for release-test, it might have an exception | 13:37 |
| elodilles | yepp, release-test also triggers a release announcement: https://lists.openstack.org/archives/list/release-announce@lists.openstack.org/message/QFJSRWUX5URHOKLS3SYR7YTIB7LWO4C6/ | 13:37 |
| ttx | ok so, on Monday, I'll merge my change, approve a release-test, tghen try on a real one | 13:38 |
| elodilles | but it definitely has a different format :S | 13:38 |
| ttx | elodilles: could you file a release-test release request so that I don;t self-approve? | 13:38 |
| elodilles | ttx: ACK, will do after the meeting | 13:38 |
| ttx | perfect, thanks. Will add a task for me to next week | 13:38 |
| elodilles | +1 | 13:40 |
| ttx | done | 13:40 |
| ttx | other topic: we don;t have the team registered for PTG yet | 13:40 |
| ttx | (see email to teh openstack-discuss list from this morning) | 13:41 |
| ttx | I think it's good practice for us to have one, can be the regular IRC meeting happening live | 13:41 |
| elodilles | +1 | 13:41 |
| ttx | If you agree I can register us | 13:41 |
| elodilles | please do | 13:41 |
| opendevreview | Yasufumi Ogawa proposed openstack/releases master: Release tacker RC1 for 2024.2 Dalmatian https://review.opendev.org/c/openstack/releases/+/928562 | 13:42 |
| ttx | ok | 13:42 |
| ttx | anything else? | 13:42 |
| elodilles | nothing from me | 13:42 |
| elodilles | and frickler had to step away :) | 13:43 |
| ttx | alright, let's close then | 13:43 |
| ttx | #endmeeting | 13:43 |
| opendevmeet | Meeting ended Fri Sep 13 13:43:09 2024 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 13:43 |
| opendevmeet | Minutes: https://meetings.opendev.org/meetings/releaseteam/2024/releaseteam.2024-09-13-13.00.html | 13:43 |
| opendevmeet | Minutes (text): https://meetings.opendev.org/meetings/releaseteam/2024/releaseteam.2024-09-13-13.00.txt | 13:43 |
| opendevmeet | Log: https://meetings.opendev.org/meetings/releaseteam/2024/releaseteam.2024-09-13-13.00.log.html | 13:43 |
| ttx | thanks everyone | 13:43 |
| elodilles | thanks ttx o/ | 13:43 |
| opendevreview | Elod Illes proposed openstack/releases master: Releasing release-test https://review.opendev.org/c/openstack/releases/+/929284 | 13:49 |
| elodilles | ttx: ^^^ | 13:49 |
| frickler | sorry for the interruption. last thing I wanted to note that I'll be out most of next week and not 100% sure yet when I'll return, so added a note for the week after that, too. will update once I'm actually back | 13:53 |
| tkajinam | elodilles frickler ttx, I fixed the issue we had before rc1 release and successfully created rc1, but osc 7.1 was released then and is not blocking CI in master/2024.2 . | 14:12 |
| tkajinam | s/not/now/ | 14:12 |
| elodilles | tkajinam: ACK, thanks for the heads up | 14:15 |
| tkajinam | I can fix it in storlets side but that's just a workaround and we eventually should fix the regression in osc | 14:16 |
| opendevreview | Jon Bernard proposed openstack/releases master: Add 2024.2 (Dalmatian) cycle highlights for cinder https://review.opendev.org/c/openstack/releases/+/929154 | 15:05 |
| opendevreview | Merged openstack/releases master: Release placement RC1 for 2024.2 Dalmatian https://review.opendev.org/c/openstack/releases/+/928556 | 15:05 |
| opendevreview | Jon Bernard proposed openstack/releases master: Add 2024.2 (Dalmatian) cycle highlights for cinder https://review.opendev.org/c/openstack/releases/+/929154 | 15:08 |
| *** bauzas_ is now known as bauzas | 16:44 | |
| *** bauzas_ is now known as bauzas | 19:44 | |
| opendevreview | Brian Rosmaita proposed openstack/releases master: Release cinder RC1 for 2024.2 Dalmatian https://review.opendev.org/c/openstack/releases/+/928519 | 21:27 |
| *** bauzas_ is now known as bauzas | 23:27 | |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!