14:00:00 #startmeeting releaseteam 14:00:00 Meeting started Fri Jul 7 14:00:00 2023 UTC and is due to finish in 60 minutes. The chair is hberaud. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:00:00 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:00:00 The meeting name has been set to 'releaseteam' 14:00:05 Ping list: elodilles armstrong 14:00:08 o/ 14:00:10 https://etherpad.opendev.org/p/bobcat-relmgt-tracking 14:00:14 We are now at line 230 14:00:27 sharp. at. 16:00:00. :] 14:00:37 lol 14:00:53 o/ 14:01:22 I wouldn't have made it if I had wanted to do it on purpose 14:01:29 :] 14:01:31 let's go 14:01:35 #topic Review task completion 14:01:49 Propose change to release-model: abandoned tripleo _independent deliverables 14:01:55 https://review.opendev.org/c/openstack/releases/+/887505 14:02:27 we just need answer from the team i guess 14:02:30 as far as I can see nobody yet replied 14:02:55 yes 14:03:01 the patch is on the rails 14:03:12 next, propose change to remove networking-old deliverable (ttx) 14:03:18 https://review.opendev.org/c/openstack/releases/+/887504 14:03:21 yep posted 14:03:41 this one can be merged i think ^^^ 14:03:46 yes 14:03:52 i mean, it neads a 2nd review o:) 14:04:00 done 14:04:13 \o/ 14:04:15 thanks 14:04:21 np 14:04:23 Get confirmation from neutron and horizon teams about ovn-bgp-agent and xstatic-angular-fileupload presence in Bobcat release (elod) 14:04:36 ovn-bgp-agent: https://review.opendev.org/c/openstack/releases/+/887385 14:04:48 this one is merged & done ^^^ 14:04:55 indeed 14:05:16 and the second one => xstatic-angular-fileupload: will be _independent deliverable, like the other xstatic* deliverables 14:05:25 that wfm 14:05:37 discussed on IRC: https://meetings.opendev.org/irclogs/%23openstack-horizon/%23openstack-horizon.2023-07-05.log.html#t2023-07-05T12:45:11 14:05:43 this solution seems the more appropriate 14:06:32 so this is not coupled to bobcat, right? 14:06:43 do they will propose the patch or do we have to propose it? 14:06:48 yes 14:06:55 i mean, we don't have to have a deliverables yaml until Bobcat-2 14:07:14 since it's in _independent 14:07:16 if this is an independent deliverable I guess that yes 14:07:31 I mean that doesn't shock me 14:08:08 may we can setup a deliverable patch file, to ensure to not forget it... 14:08:18 at least 14:08:32 hberaud: sounds good to me! 14:08:38 +1 14:08:58 i can propose one after the meeting 14:09:55 I added a task related to that for R-10 14:10:10 as the two next weeks we doesn't have meeting 14:10:15 ++ 14:10:37 well, next task 14:10:39 Generate a list of all cycle-with-intermediary libraries which did not release since the 2023-05-11 date of milestone-1 14:10:47 https://review.opendev.org/q/topic:bobcat-milestone-2 14:11:13 https://review.opendev.org/q/topic:bobcat-milestone-2+status:open 14:11:40 ( https://review.opendev.org/q/topic:bobcat-milestone-2+is:open+project:openstack/releases ) 14:11:47 Merged openstack/releases master: Remove networking-odl from Bobcat release https://review.opendev.org/c/openstack/releases/+/887504 14:12:03 ( as glance team hijacked our topic o:)) 14:12:11 :) 14:12:49 some needs a 2nd core review 14:13:14 yeah I just validated one 14:13:19 and metalsmith too 14:13:31 i'm not sure that ironic team saw my comment, but anyway, they have 2x +1 on metalsmith 14:13:55 yeah I think they missed your comment 14:14:10 i am hesitant with the version bump there 14:14:36 if you say that MINOR bump is enough then I'm OK with the patch 14:15:40 hmm I hesit too 14:15:53 maybe i can -1 to highlight my question and handle the patch next week 14:16:03 yeah good idea 14:16:22 I dropped my +2 14:16:43 ++ 14:16:44 thanks elodilles 14:17:26 and manila team -1'd the patch to signal we should wait a bit, 14:17:29 concerning keyston, I agree with you 14:17:38 and release at M2 can't hurt 14:18:15 hberaud: ACK, then let's release it 14:18:23 for manila we can wait early next week and close the patch if they don't come back to us 14:18:47 hberaud: yepp, let's wait with manila patch 14:19:00 and that's all for this topic 14:19:16 next topic 14:19:21 Catch if there are acl issues in newly created repositories (hberaud) 14:19:55 so as I said only ironic deliverables were present in the result of our tool 14:20:15 so I think this is related to the way they manage their lifecycle 14:20:17 yepp, ironic team is a bit special 14:20:36 as they have some special ACL to be able to handle bugfix branches 14:20:49 so, for this reason, I didn't proposed patches 14:20:52 so this is fine 14:20:56 yeah that was the same issue at the last check 14:21:05 yes 14:21:18 See R-21 comments 14:21:49 simply the list has grown 14:22:06 ack 14:22:07 where's the script that performs the acl check? 14:22:22 maybe it just needs to focus on perms for specific branches 14:22:35 https://opendev.org/openstack/releases/src/branch/master/tools/aclissues.py 14:22:49 thanks 14:23:33 okay, so it's doing line by line parsing of the acl, not reading it as an ini file 14:24:01 probably would need an overhaul if you wanted it to be smarter about checking things only in specific sections 14:24:14 probably 14:24:19 yeah it was pretty basic, based on every conf being standard 14:24:36 if we start making fancy exceptions it would have to be a lot smarter 14:24:53 Merged openstack/releases master: Bobcat-2 release for python-glanceclient https://review.opendev.org/c/openstack/releases/+/887496 14:24:54 Merged openstack/releases master: Bobcat-2 release for os-vif https://review.opendev.org/c/openstack/releases/+/887486 14:25:32 yeah, we have some logic in https://opendev.org/openstack/project-config/src/branch/master/tools/normalize_acl.py you might be able to reuse 14:26:21 I added a comment in the "thing to change" section, to keep on eye on that 14:26:48 ++ 14:27:12 #topic Assign R-12 and R-10 week tasks 14:27:14 i think we used a custom ini parser because gerrit acls can have duplicate sections, while configparser doesn't handle that 14:27:32 er, duplicate options i guess it was 14:28:15 hberaud: i can take the 'convenienve releases for Yoga' if you don't insist on that o:) 14:29:08 as you that, I don't mind doing it 14:29:10 beyond that the last free task is the next release cycle schedule 14:29:12 I prefer not to take anything as I won't be around much 14:29:29 I guess i could do that 14:29:46 if nobody else wants it 14:29:47 do we know the name of the next cycle yet? 14:30:01 We just got the list from the trademark lawyers 14:30:08 ttx: probably you know better the Foundation's timeplan o:) 14:30:10 we still need to run some vote on it 14:30:28 so we'll use a placeholder name for initial planning 14:30:33 ACK 14:30:53 I seen canteloupe somewhere 14:31:18 yes, but that was just used as a random name :) 14:31:21 i guess :) 14:31:27 yeah surely 14:31:32 we'll see though :) 14:31:33 alright, I took the task 14:31:41 rhymes with antelope 14:31:43 thanks ttx 14:31:47 yeah 14:31:51 fungi: :D 14:32:06 indeed 14:32:27 and everything seems now assigned 14:32:32 #topic Review countdown email 14:32:38 https://etherpad.opendev.org/p/relmgmt-weekly-emails 14:33:03 LGTM 14:33:10 °1 14:33:12 +1 14:33:13 Merged openstack/releases master: Bobcat-2 release for keystonemiddleware https://review.opendev.org/c/openstack/releases/+/887483 14:33:14 I fixed a few things... basically the milestones are called "Bobcat-2", "Bobcat-3", only the final release is called 2023.2 Bobcat 14:33:27 ack thanks 14:33:51 if only so that we don't get confusion at C-1 milestone (which wil be in 2023) being called 2024.1 14:34:09 :S 14:34:22 and you never know, we might delay release until 2024 14:34:32 :) 14:34:33 so Bobcat could end up being 2024.1 after all 14:34:53 (Bobcat is the name of the development cycle, 2023.2 is the name of the release) 14:35:19 subtle difference, but I like to be pedantic 14:35:32 otherwise lgtm 14:35:54 ++ 14:35:58 sent 14:36:20 #topic Open Discussion 14:36:26 anything else? 14:36:36 - 14:37:03 nothing from me 14:37:30 ok lets keep it short 14:37:35 thanks everyone 14:37:40 thanks o/ 14:37:42 #endmeeting