13:00:38 <ttx> #startmeeting releaseteam
13:00:38 <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:38 <opendevmeet> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
13:00:38 <opendevmeet> The meeting name has been set to 'releaseteam'
13:00:55 <elodilles> o/
13:00:57 <ttx> Ping list: release-team elod armstrong
13:01:32 <ttx> Our agenda for today is at https://etherpad.opendev.org/p/dalmatian-relmgt-tracking -- down to line 390 or so
13:01:45 <frickler> \o
13:01:53 <ttx> #topic Review task completion
13:02:11 <ttx> - Process any remaining library branching exception. (all)
13:02:26 <ttx> #link https://review.opendev.org/q/topic:dalmatian-stable-branches+is:open
13:02:57 <ttx> Looks like two leftovers
13:03:29 <ttx> Should we bypass PTL-APPROVED and just merge those? i can do that
13:03:59 <elodilles> yes, we did that for some of the brancing patches as well, so let's do that
13:04:02 <frickler> as mentioned before the meeting, I'd prefer to stop doing that. but I also won't block you
13:05:01 <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:39 <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:06:26 <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:38 <ttx> I wrote down those two exceptions in the health dashboard
13:07:04 <elodilles> ACK
13:07:25 <ttx> #topic Assign R-2 week tasks
13:07:29 <ttx> oops
13:07:33 <ttx> #undo
13:07:33 <opendevmeet> Removing item from minutes: #topic Assign R-2 week tasks
13:07:52 <ttx> - On the Monday, generate release requests for all deliverables that have do not have a suitable candidate yet. (elod)
13:08:56 <ttx> Branch devstack-plugin-* deliverables https://review.opendev.org/c/openstack/releases/+/928504
13:09:10 <elodilles> this is merged \o/
13:09:17 <ttx> cycle-with-intermediary deliverables https://review.opendev.org/c/openstack/releases/+/928505
13:09:29 <elodilles> released, too \o/
13:09:35 <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:10:04 <elodilles> more than half of them released ^^^ \o/
13:10:16 <elodilles> some -1 feedback from teams
13:10:28 <elodilles> so we are waiting for updates there
13:10:38 <ttx> For the remaining ones should we wait to release on Monday rather than Friday?
13:10:43 <elodilles> i've also -1'd some repos that have broken gates :(
13:10:52 <ttx> I can do the +2a on Monday
13:11:03 <elodilles> ttx: i'm OK with that
13:11:17 <elodilles> better on Monday than on Friday :)
13:11:29 <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:57 <elodilles> :S
13:12:15 <elodilles> (these are the repos with broken gates: https://review.opendev.org/q/topic:release-health-check-cwrc-dalmatian+is:open )
13:12:46 <ttx> ok I added a specific Monday task to remember it
13:12:56 <elodilles> ++
13:13:02 <ttx> That leads us to:
13:13:06 <ttx> #topic Assign R-2 week tasks
13:17:16 <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:18 <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:19:15 <ttx> elodilles: I see storlets in your broken gate list but it does not seem to have resulted in a RC1 blocker
13:19:24 <ttx> probably released as intermendiary, I guess
13:19:32 <elodilles> hmm, let me check
13:19:41 <ttx> Otherwise all tasks assigned
13:19:47 <frickler> iirc tkajinam fixed it?
13:20:32 <ttx> ah that's a possibility yes
13:20:43 <frickler> hmm, no, still working on it https://review.opendev.org/c/openstack/storlets/+/929210
13:20:54 <elodilles> i don't see a release patch either :S
13:21:31 <elodilles> i'll create an RC1 patch for that then
13:21:44 <ttx> hmm, it's there already
13:21:58 <frickler> this morning we saw it was broken by osc 7.1.0, cf. https://bugs.launchpad.net/python-openstackclient/+bug/2080600
13:22:26 <ttx> https://review.opendev.org/c/openstack/releases/+/928560
13:22:35 <ttx> storlets RC1 successful merge ^
13:23:40 <elodilles> ah, my bad, sry :S
13:23:56 <frickler> might have been my bad, too, for not verifying gate status
13:23:56 <elodilles> anyway, so that means we need an RC2 probably for storlets, right?
13:24:02 <frickler> likely yes
13:24:17 <frickler> and very likely also yet another OSC release
13:24:38 <ttx> I itemized all the RC1 leftovers so that we can track them separately
13:25:06 <elodilles> thanks ttx
13:25:15 <ttx> should we add a task to track that storlets RC2 need?
13:25:50 <elodilles> yes, that's a good idea
13:25:53 <ttx> added
13:25:57 <elodilles> thx
13:26:36 <ttx> OK task allocation all set
13:26:51 <ttx> #topic Review countdown email for week R-2
13:26:57 <ttx> #link https://etherpad.opendev.org/p/relmgmt-weekly-emails
13:27:36 <elodilles> mail lgtm
13:27:50 <ttx> OK, I will send it shortly after meeting
13:27:51 <elodilles> (added some '2025.1' o:)
13:28:03 <ttx> #topic Open Discussion
13:28:21 <ttx> - How to deploy and test https://review.opendev.org/c/openstack/releases/+/929126
13:28:44 <ttx> So this is mostly untested, but looks safe on the surface
13:29:10 <ttx> we could do a controlled merge and see
13:29:13 * frickler suggests to test in production
13:29:31 <ttx> Sounds like a great idea!
13:29:36 <frickler> we should be able to rerun the failed swift announcement as a test case
13:29:47 <elodilles> yes, merge 1 release patch and see what happens
13:30:03 <ttx> how could we just rerun the announcement?
13:30:18 <ttx> I'm fine with merging it on Monday and then approving one of the RC1 patches to see
13:30:43 <elodilles> sounds OK to me, too
13:31: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:43 <frickler> then test with a new release it is
13:31:53 <elodilles> +1
13:32:07 <frickler> do we ignore the missing release announcement or do you think it should be sent manually?
13:32:10 <ttx> I have to check if the RC1 release announcement would actually trigger enough of the new code
13:32:51 <ttx> I'd be fine with sending it manually
13:32:52 <elodilles> does release-test trigger a release announcement?
13:33:03 <elodilles> if yes, then we can try with that as well
13:33:41 <frickler> at least it shouldn't hurt to run one release-test release first, ack
13:35:39 <frickler> sorry gotta step away for a bit, will check back later
13:37:01 <ttx> Hmm, I can;t find any run of announce-release for release-test, it might have an exception
13:37:07 <elodilles> yepp, release-test also triggers a release announcement: https://lists.openstack.org/archives/list/release-announce@lists.openstack.org/message/QFJSRWUX5URHOKLS3SYR7YTIB7LWO4C6/
13:38:02 <ttx> ok so, on Monday, I'll merge my change, approve a release-test, tghen try on a real one
13:38:03 <elodilles> but it definitely has a different format :S
13:38:19 <ttx> elodilles: could you file a release-test release request so that I don;t self-approve?
13:38:37 <elodilles> ttx: ACK, will do after the meeting
13:38:56 <ttx> perfect, thanks. Will add a task for me to next week
13:40:08 <elodilles> +1
13:40:18 <ttx> done
13:40:56 <ttx> other topic: we don;t have the team registered for PTG  yet
13:41:24 <ttx> (see email to teh openstack-discuss list from this morning)
13:41:41 <ttx> I think it's good practice for us to have one, can be the regular IRC meeting happening live
13:41:52 <elodilles> +1
13:41:53 <ttx> If you agree I can register us
13:41:59 <elodilles> please do
13:42:25 <opendevreview> Yasufumi Ogawa proposed openstack/releases master: Release tacker RC1 for 2024.2 Dalmatian  https://review.opendev.org/c/openstack/releases/+/928562
13:42:40 <ttx> ok
13:42:43 <ttx> anything else?
13:42:54 <elodilles> nothing from me
13:43:06 <elodilles> and frickler had to step away :)
13:43:06 <ttx> alright, let's close then
13:43:09 <ttx> #endmeeting