14:01:52 #startmeeting releaseteam 14:01:52 Meeting started Fri Jan 20 14:01:52 2023 UTC and is due to finish in 60 minutes. The chair is ttx. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:01:52 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:01:52 The meeting name has been set to 'releaseteam' 14:02:03 o/ 14:02:06 Looks like the lag is larger today 14:02:15 Alright, let's get going 14:02:39 Ping list: hberaud armstrong elodilles 14:02:45 ~o~ 14:02:55 #link https://etherpad.opendev.org/p/antelope-relmgt-tracking 14:03:08 o/ 14:03:12 down to line...252 14:03:22 #topic Review task completion 14:03:32 Generate a list of intermediary-released service deliverables that have not done a release in this cycle yet and propose release model change for them (ttx) 14:03:34 R-9. scary 14:03:53 I did find a bunch but most of them have already responded in previous years 14:04:09 vitrage however looked like a good candidate 14:04:15 Dmitriy Rabotyagov proposed openstack/releases master: Release OpenStack-Ansible Zed https://review.opendev.org/c/openstack/releases/+/871280 14:04:18 #link https://review.opendev.org/c/openstack/releases/+/870539 14:04:47 waiting for a second +2 14:05:02 PTL approved, so I guess we can proceed 14:05:09 Propose convenience releases for Xena to ease the transition of Xena to Extended Maintenance and avoid rush and broken releases when the transition deadline is coming (hberaud) 14:05:10 with the merge 14:05:30 Dmitriy Rabotyagov proposed openstack/releases master: Release OpenStack-Ansible Yoga https://review.opendev.org/c/openstack/releases/+/871281 14:06:06 https://review.opendev.org/q/topic:xena-stable 14:06:21 anything to add? 14:06:24 there have been many releases \o/ thanks hberaud for proposing these 14:06:29 Dmitriy Rabotyagov proposed openstack/releases master: Release OpenStack-Ansible Xena https://review.opendev.org/c/openstack/releases/+/871282 14:06:30 nope 14:06:48 and... I'll send the countdown email after this meeting 14:06:48 good to see that some projects are active on their stable branches 14:07:00 #topic Review countdown email 14:07:18 will it be the 'Between Milestone-2 and Milestone-3' one? 14:07:22 Need to copy it over, sorry 14:08:05 actually 14:08:14 I did cover those in separate emails 14:08:28 not sure it's worth sending one for this week 14:08:49 only vitrage got flagged and that was +1ed already 14:09:06 thoughts? 14:09:53 if those were all covered, then let's skip the mail 14:09:59 +1 14:10:26 ok 14:10:40 #topic Assign next week tasks 14:10:54 all set 14:10:58 i've already took all 14:11:00 taken 14:11:05 #topic Assign the next Chair 14:11:09 done too 14:11:11 that too o:) 14:11:20 #topic Discuss about zaqar's inclusion 14:11:39 (as I had to skip last meeting at the last minute, sorry for that) 14:12:53 gmann: FYI ^ 14:13:31 elodilles: np 14:13:58 who can summarize the issue? 14:14:36 well, i just read the new (?) info on the tracking page 14:14:45 zaqar is not in good fit and possible it could be a good candidate for inactive project 14:15:06 the last sentence is: "as zaqar team knows the issue and not sure when they will fix it. I think you can take decision on skipping its release and send on ML. After that if no release happening, gate is broken then TC can mark it as Inactive project." 14:15:18 the most i know is that zaqar's testing relies on mongodb, which is no longer open source and so has disappeared form the supported platforms for our upcoming release. the attempts to rsolve that have been ongoing since days after the zed release, and at present the project is still unable to merge any new changes, though they're working on dropping mongodb testing aiui 14:15:33 I'd rather not be the one deciding to not include it.. ideally that would be a TC decision 14:15:49 we are not empowered to make that type of decision 14:16:07 (dropping a deliverable from the next release) 14:16:17 on the other hand we are quite late 14:16:37 elodilles: +1 14:16:38 so a decision should be made very quickly i guess 14:17:12 it was brought to the tc's attention as a risk over winter holidays, but didn't get much traction at the time (mostly due to everyone being away or preoccupied, i think) 14:17:27 year-end holidays i mean 14:17:40 (northern-hemisphere winter) 14:18:34 it initially came to my attention when another project reported having to drop zaqar integration testing in order to be able to continue merging changes 14:19:19 fungi: was a patch proposed to mark it inactive? 14:19:28 MayIf not maybe we should push that 14:19:33 https://review.opendev.org/c/openstack/governance/+/870098 14:19:38 *If 14:19:56 16:36:29 for zaqar decision, I will propose 25 Jan which is next TC meeting to check and decide. 14:20:02 OK how about we track status there 14:20:03 i see this in tc meeting log ^^^ 14:20:13 and wait until next week 14:20:44 yes, let's track the status 14:21:17 OK anything else on that topic? 14:21:50 did PTLs respond to Bobcat Schedule? 14:22:07 limited response, some did +1 14:22:16 not ready to be approved yet 14:22:24 #topic Open discussion 14:22:25 ack, thanks 14:22:32 I guess we moved to open discussion :) 14:22:38 :] 14:22:43 sorry o:) 14:22:49 Fair warning that my February is pretty busy travel-wise 14:23:00 ack 14:23:05 I put me name to chair one of the only meetings I'll be attending 14:23:06 ack 14:23:56 anything else to discuss? 14:24:10 maybe worth to mention: 14:24:29 #link https://review.opendev.org/q/topic:inactive-release-test 14:24:38 so, 14:24:51 adjutant deliverables were released 14:25:02 and mistral gates are also fixed 14:25:25 so I think the mistral release patches can be merged, too 14:25:25 \o/ 14:25:35 i've updated them today 14:26:07 am i right that the new PTL is not added to governance repo? 14:26:12 (mistral) 14:26:54 just because in that case we won't get PTL-Approved triggered 14:26:54 ok... if nothing else we can close the meeting early 14:27:06 ah hm 14:27:15 https://opendev.org/openstack/governance/src/branch/master/reference/projects.yaml#L732 14:27:18 mistral is dpl 14:27:24 according to the current data anyway 14:27:34 we might want to add their release liaison for sure 14:27:46 they have two release liaisons listed 14:28:19 i can prepare the governance patch if that doesn't exist 14:28:45 mistral is still DPL for this cycle I can confirm 14:28:46 what needs patching in governance? 14:28:52 fungi: those are former liaisons and quite inactive :/ 14:28:56 oh 14:29:01 * they 14:29:50 avanzaghi: i'll prepare a patch to add you as release liaison if taht's OK 14:30:00 https://lists.openstack.org/pipermail/openstack-discuss/2022-December/031417.html 14:30:19 linked from comments in proposed governance change https://review.opendev.org/866562 14:30:43 and thanks for your efforts & fixing the gates :) 14:30:56 so yes, probably worth getting gmann to revisit since that comment was from 2022-12-07 14:31:53 avanzaghi: if you could review the mistral release patches that would be awesome: https://review.opendev.org/q/topic:inactive-release-test 14:32:25 right I'll look at it 14:32:42 and if everything is OK then I think we should release them. ttx hberaud : is that OK? 14:32:57 WFM 14:32:58 yes 14:33:01 \o/ 14:33:02 thanks 14:33:18 Alright, anything else to discuss? 14:33:53 nothing else from me for now 14:34:00 nope 14:34:11 ok then 14:34:14 #endmeeting