14:00:09 #startmeeting releaseteam 14:00:09 Meeting started Fri Jul 16 14:00:09 2021 UTC and is due to finish in 60 minutes. The chair is hberaud. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:00:09 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:00:09 The meeting name has been set to 'releaseteam' 14:00:16 Ping list: elod armstrong 14:00:25 We're way down on line 206 now 14:00:28 o/ 14:00:35 #link https://etherpad.opendev.org/p/xena-relmgt-tracking 14:00:40 Will just wait a couple minutes for folks. 14:01:05 added a couple of topics 14:01:14 ack 14:01:18 o/ 14:03:29 Ok let's go! 14:03:31 #topic Review task completion 14:03:36 Milestone-2 => https://review.opendev.org/q/topic:%2522xena--milestone-2%2522+status:open 14:03:48 Merged openstack/releases master: Create queens-eol tag for manila-ui project https://review.opendev.org/c/openstack/releases/+/800963 14:03:51 A couple of patch just need a final +2 14:04:10 Deadline is today so feel free to approve them 14:04:27 We just have 3 exceptions 14:04:36 I'm on it 14:05:04 Where people asked to wait for patches 14:05:09 ttx: thanks 14:05:40 all pretty straightforward 14:06:03 Excellent 14:06:10 The next topic is "Ask Cinder team if we should include rbd-iscsi-client for Xena release." 14:06:35 So, they replied "it's on an independent release model, we have a CI issue to work out, but we intend to release sometime during xena" 14:06:42 So, no rush for this one 14:07:48 Concerning the barbican-ui topic, the team replied the same that during Wallaby. They have a patch that's been languishing that has all the basic functionality for barbican-ui. They would rather not abandon it, given that it is in their roadmap downstream, just kind of low priority right now. 14:08:03 So, I would suggest to give them on more chance 14:08:25 oh, it's independent? 14:08:34 Apparently yes 14:08:37 then I agree we need no decision 14:09:00 hmm 14:09:23 it would be independent if it existed 14:09:50 We only need to finalize xena content, so as long as it's not xena material we are good 14:09:51 And the last one was the monasca part, I proposed a patch to retire the project, and the team agreed with that https://review.opendev.org/c/openstack/releases/+/800628 So I think that we can +2 this one 14:10:26 +2 14:10:27 ttx: I think that they plan to host this project under the independent umbrella 14:10:46 but it doesn't yet exist on our side, right? 14:10:50 ok then we are good, they can release when they want 14:11:42 ok 14:12:08 And that's all for the discussion part 14:12:45 The last topic was to catch the ACL issues and apparently no issues have been detected, thanks ttx 14:12:55 yep, empty output means no issues 14:13:08 Excellent, no news, good news 14:13:30 Then we go to task assignment 14:13:39 #topic Assign R-11 tasks 14:13:42 So 14:14:11 We only have to handle the remaining exceptions for Milestone-2 14:14:37 As you know I'll be mostly offline during the 2 next weeks 14:15:01 So, ttx, elodilles, I'll let you handle the 3 remaining patches 14:15:05 So it's just about keeping an eye on those for new submissions? 14:15:10 there are the 3 exception you linked earlier, am I right? 14:15:14 hberaud: ack 14:15:15 yes 14:15:52 ok we can keep the watch. Did you give an extra deadline? 14:16:39 Merged openstack/releases master: Xena-2 Release for openstacksdk https://review.opendev.org/c/openstack/releases/+/800237 14:16:44 Merged openstack/releases master: Xena-2 Release for metalsmith https://review.opendev.org/c/openstack/releases/+/800234 14:17:21 For now, I didn't gave extra deadline, I'll leave a comment to notify our extra deadline and my PTO to PTL 14:17:28 PTLs 14:19:33 Usually Done 14:19:41 s/Usually// 14:20:01 And that's all for next weeks assignments 14:20:19 Merged openstack/releases master: Xena-2 Release for python-ironic-inspector-client https://review.opendev.org/c/openstack/releases/+/800251 14:21:04 I already proposed the Yoga schedule but we will discuss about this later during the meeting 14:21:21 #topic Review countdown email contents 14:21:27 https://etherpad.opendev.org/p/relmgmt-weekly-emails 14:23:50 I US-ified the dates 14:23:58 All good otherwuse 14:24:00 +i 14:24:01 Ok 14:24:24 Merged openstack/releases master: fix placeholder https://review.opendev.org/c/openstack/releases/+/801041 14:24:40 LGTM! 14:24:57 Merged openstack/releases master: Propose to retire monasca-analytics from deliverables https://review.opendev.org/c/openstack/releases/+/800628 14:25:12 Sent! 14:25:29 #topic SBOMs for OpenStack? 14:25:34 yeah so 14:25:38 ttx: the floor is yours 14:25:56 There is this thing the Biden administration has been pushing 14:26:06 called software bill of materials 14:26:18 in an effort to better track supply chain issues 14:26:19 https://en.wikipedia.org/wiki/Software_bill_of_materials 14:26:37 I noticed that Kubernetes started to work on publishing a formal SBOM doc with each release 14:26:52 We might want to follow suit, before someone else asks 14:27:10 At this stage the idea would be to do our homework and learn about it 14:27:21 and of te various tools being created to help handle them 14:27:26 I think the Linux foundation is also doing similar 14:27:38 I really love the idea 14:27:48 LF maintains SPDX which is a standard format 14:28:00 We have pretty good dependency tracking in openstack already 14:28:10 but that may just be one piece of the puzzle 14:28:23 Maybe we could inspire from the LF 14:28:24 It might not be a Xena thing, but definitely a hot topic for the yeti PTG 14:28:32 Yes 14:28:47 yeti? isn't yoga? 14:28:49 So this was more of a flag I wanted to raise so that we all learn more about those 14:28:54 Arh Yoga 14:28:57 Yggdrasil 14:29:00 lol 14:29:01 Toda whatever 14:29:14 Good suggestion 14:29:25 It will always be yeti in my mind 14:29:47 Boys don't cry 14:30:12 http://scd.rfi.fr/sites/filesrfi/imagecache/rfi_16x9_1024_578/sites/images.rfi.fr/files/aef_image/yeti-tintin_0.jpg 14:30:22 ttx are you too attached to yeti :) 14:30:23 :) 14:31:36 alright that is all I had on this topic 14:31:42 oh, maybe a link 14:31:46 Ok I added SBOM to our "things to change" 14:31:52 https://github.com/kubernetes/release/blob/master/docs/bom/create-a-bill-of-materials.md 14:32:08 That's the K8s proposed process around SBOM, pretty new 14:32:18 and very go-centric 14:32:24 ok 14:32:28 but still interesting to see as a data point 14:32:31 I'll have a deeper look 14:32:37 Sure 14:32:39 +1 14:33:11 So, next topic 14:33:19 #topic Yoga proposed schedule 14:33:26 your email worked for me btw 14:33:34 I think you had a stale PGP sig block 14:33:39 #link https://review.opendev.org/c/openstack/releases/+/800663 14:33:44 ttx: yes 14:34:30 Do we want to propose more alternative schedules? 14:34:52 I prefer to start with this one and spend time on alternative if really needed 14:34:54 At first glance i was thinking... this is short, like it does not account for lost time around new year 14:35:17 But event-wise that may lead to better alignment, so I think we can work with it 14:35:52 like if we do 25w every time we'll skew 14:35:56 I fear that we miss the ubuntu train if we propose longer schedule 14:36:02 but for now skew is probably a good diea 14:36:24 yeah I know they will appreciate the timing here 14:36:39 so +1 for me, after careful consideration 14:36:47 But I don;t want to influence the feedback 14:37:20 No problem, we have the time to leave the time to think more about this 14:37:54 Anything else about this topic? 14:38:39 no 14:38:42 Ok move on 14:38:44 #topic Open Floor 14:38:56 Anything else to discuss today? 14:39:14 one thing from me 14:39:24 elodilles: the floor is yours 14:39:37 I know that the timing is not the best (vacations), but I'm planning to generate release patches for Ussuri to prepare for the EM transition in November 14:39:48 EOM 14:40:03 I mean that's it :X 14:40:19 Can't we wait at least the end of R-11? 14:40:39 of course we can :) 14:41:04 Ok, so LGTM 14:41:07 though i don't know how fast the teams will react 14:41:45 You'll start by releasing the latest deltas? 14:41:46 (usually a ~half or so of the patches are abandoned due to missing approval from teams) 14:41:57 hberaud: yes 14:42:14 Ok that will limit the back and forth 14:43:31 At first glance November seems a bit far from us but as you said people take time to react, so... why not 14:43:57 hberaud: this is not the final release :) 14:44:13 more like a final-but-one :) 14:44:22 ok 14:44:24 :) 14:44:32 this process was done by smcginnis some time ago, 14:44:37 Ok 14:44:47 to avoid breakages with the final releases 14:44:59 I see 14:45:14 Sold 14:45:18 (teams in hurry, releases after deadline, things break, etc) 14:45:49 Ok no problem you convinced me :) 14:46:04 ok, thanks :) then I'll generate the patches then around next Friday, is that OK? 14:46:14 That make sense 14:46:21 Ok for me 14:46:37 ack 14:47:23 Anything else that you want to discuss today? 14:47:59 nothing else from me :X 14:48:54 nope nothing 14:50:00 OK, thanks everyone. Let's wrap up. 14:50:02 #endmeeting