14:00:01 #startmeeting releaseteam 14:00:01 Meeting started Fri May 28 14:00:01 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:02 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:00:04 The meeting name has been set to 'releaseteam' 14:00:05 Ping list: elod armstrong 14:00:11 o/ 14:00:13 #link https://etherpad.opendev.org/p/xena-relmgt-tracking 14:00:18 We're way down on line 128 now. 14:00:29 Will just wait a couple minutes for folks. 14:00:59 o/ 14:02:16 o/ 14:03:00 Let's go! 14:03:05 #topic Review task completion 14:03:12 Ensure that all trailing projects have been branched for the previous series. => Done 14:03:22 https://review.opendev.org/q/topic:%22xena-milestone-1%22+(status:open%20OR%20status:merged) 14:03:36 We are near from the end of this topic 14:04:11 Cinder asked to get more time to check patches 14:04:19 Monasca need to fix some gates 14:04:55 I just updated os-ken and osc-placement 14:05:06 I think that we can approve those without response, I don't expect response from team 14:05:18 osc-placement needs double check by RH nova folks 14:05:27 Any opinion concerning those without response? 14:05:32 I mean that's what gibi asked 14:05:38 Yes 14:05:58 osc-placement and os-ken are not part of those without response 14:06:08 ack 14:06:14 they need PTL/liaison approval as usual 14:07:20 I'll ping the PTLs of those without response once again we can proceed them on Monday 14:07:57 Next task 14:08:03 Propose autoreleases for cycle-with-intermediary libraries which did not release since the previous release. => Done 14:08:33 Deadline for trailing project is at R-14 so we will double check this point later 14:09:05 "To catch if there are acl issues in newly created repositories", ttx, armstrong any updates? 14:09:38 We found noissue 14:09:50 *no issue 14:09:52 Excellent, thank you 14:10:03 So next topic 14:10:04 confirmed 14:10:16 #topic Assign R-18 tasks 14:10:19 Merged openstack/releases master: [Telemetry] Transition Train to EM https://review.opendev.org/c/openstack/releases/+/790776 14:10:49 Nothing much for R-18, we only need to double check the milestone-1 remaining patches 14:11:07 #topic Assign R-15 tasks 14:11:17 I guess that could be 'all' :) 14:11:31 yes 14:12:43 Concerning R-17 and R-16 we don't have lot of tasks to manage, so I proposed to manage the emails sending, and to assign R-15 now to allow us to skip meetings during these weeks 14:13:03 As long as we don't have last minutes emergencies 14:13:34 I take the task 14:13:44 (at R-15) 14:14:08 So next meeting will be R-14, that work for you? 14:14:23 works for me 14:14:32 armstrong: thanks I'll ping you 14:14:40 ok 14:14:58 ttx: ^ 14:15:06 ( ~ one month without a meeting :-o ) 14:16:28 yes please 14:16:36 #topic Review countdown email contents 14:16:48 https://etherpad.opendev.org/p/relmgmt-weekly-emails 14:18:14 So concerning this email I've a question concerning the goals 14:18:31 IIRC xena is without goal from a TC point of view 14:18:58 hmm ok 14:19:03 so I think that a part of the first sentence need to be removed 14:19:21 https://governance.openstack.org/tc/goals/selected/xena/index.html => 404 14:19:31 done 14:19:39 ++ 14:19:47 the rest seems ok to me 14:19:58 i think they said "no goals in Xena" 14:19:59 LGTM! 14:20:05 yeah 14:20:11 ok thanks 14:20:17 maybe 14:20:25 we can add OFTC there? 14:20:37 in the email? 14:20:40 in the mail 14:20:49 just a thought 14:20:52 Yeah I was thinking about that 14:21:11 Can't hurt, that could be another reminder 14:21:22 something like that 14:21:29 feel free to edit 14:21:37 or remove :) 14:21:38 yes excellent, short at efficient 14:21:46 s/at/and/ 14:22:06 Anything else concerning the email? 14:22:22 nope 14:23:02 #topic Train-em status 14:23:20 So just a quick status about train-em 14:23:22 https://review.opendev.org/q/topic:%22train-em%22+(status:open%20OR%20status:merged) 14:23:37 or just the open ones: https://review.opendev.org/q/topic:train-em+is:open 14:23:47 thanks 14:23:56 indeed 14:24:15 we got some responses, so the list is shrinking 14:24:32 I think that we can continue with keystone, solum, senlin, murano 14:24:35 but still there are some -1 and some without response 14:24:52 I need to recheck the state of oslo 14:25:02 I'll try further pinging on IRC and/or mail 14:25:05 and if the patches have been merged 14:25:57 I propose to wait until next friday and then maybe cut there. @eldo: what do you think about that? 14:26:10 sounds OK to me 14:26:21 cool 14:27:32 so next topic 14:27:40 #topic Open Floor 14:27:58 Anything else that you want to discuss today? 14:28:11 maybe two small things to mention 14:28:23 1. the easy one: https://review.opendev.org/c/openstack/releases/+/791702 14:28:33 i think we can proceed with this one ^^^ 14:28:51 looking 14:29:07 done 14:29:23 yeah that one does not appear on my dashboard so i missed it 14:29:40 thx :) after all the jobs have finished i'll run the branch deletion script 14:30:09 thank you elod 14:30:24 the 2nd thing is openstack/os-cloud-config related, 14:30:35 as it doesn't have an ocata-eol tag, 14:30:56 however it has an entry in the repository 14:31:24 I forgot to mention this during the week 14:31:37 so my question is what can we do about it 14:33:31 https://opendev.org/openstack/releases/src/branch/master/deliverables/ocata/os-cloud-config.yaml#L36-39 14:33:34 vs 14:33:35 I'm not sure to understand, you mean that the ocata-eol entry exist here in openstack/release (https://opendev.org/openstack/releases/src/branch/master/deliverables/ocata/os-cloud-config.yaml#L39) but the tag doesn't exist https://opendev.org/openstack/os-cloud-config# ? I'm right? 14:33:40 https://opendev.org/openstack/os-cloud-config/src/tag/ocata-eol 14:33:54 Ok 14:33:59 hberaud: yes 14:34:07 good question... 14:34:12 this project seems abandonned 14:34:15 so... 14:34:32 I'm not it's worth to force something here 14:35:10 maybe we could simply remove the exist entry and simply retry to recreate it 14:35:17 yes, I just wanted to delete the branch, and thought maybe the tag can be added manually, or something, just to reflect the required state 14:36:01 Maybe we could start with the deletion/addition and see what will happen 14:36:24 otherwise some patches will be lost. (i know that it's an abandoned branch, but...) 14:36:25 and then if that doesn't work escalate it to the infra team 14:36:38 i'm sure the deletion will work :) 14:36:47 lol me too 14:36:51 yeah it probably does not matter that much 14:37:06 the question is whether we want to have a tag just for the sake of completeness :) 14:37:31 if this is possible then I prefer this scenario 14:37:44 explicit is better than implicit 14:38:33 ok, maybe fungi knows how to apply manually the tag. I'll try to ping him :) 14:39:07 and that's it from me 14:40:53 Hervé Beraud proposed openstack/releases master: delete the missing ocata-eol tag https://review.opendev.org/c/openstack/releases/+/793610 14:40:53 Hervé Beraud proposed openstack/releases master: reapply the missing ocata-eol tag https://review.opendev.org/c/openstack/releases/+/793611 14:40:56 elod: ^ 14:41:21 hberaud: that looks also good to me, thanks :D 14:41:41 Merged openstack/releases master: Create ocata-eol tag for horizon project https://review.opendev.org/c/openstack/releases/+/791702 14:43:14 ttx, elod, armstrong FYI => http://lists.openstack.org/pipermail/openstack-discuss/2021-May/022737.html Just to ensure that everybody have seen it 14:43:19 Anything else? 14:43:41 nothing from me 14:44:16 ok thanks for sharing will register soon 14:44:24 thanks 14:44:51 please, this is the feedback link on etherpad for my research https://etherpad.opendev.org/p/armstrong 14:45:08 Thank you armstrong 14:45:10 I will appreciate your criticisms 14:45:25 I'll have a look 14:45:32 thanks hberaud 14:46:09 OK, thanks everyone. Let's wrap up. 14:46:13 #endmeeting