16:00:08 #startmeeting releaseteam 16:00:09 Meeting started Thu Sep 17 16:00:08 2020 UTC and is due to finish in 60 minutes. The chair is smcginnis. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:00:10 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 16:00:12 The meeting name has been set to 'releaseteam' 16:00:14 Ping list: ttx armstrong 16:00:22 #link https://etherpad.opendev.org/p/victoria-relmgt-tracking Agenda 16:00:34 it's that time again 16:00:59 o/ 16:01:05 o/ 16:01:31 Great, good turn out. 16:01:39 #topic Review tasks completion 16:01:55 Process any remaining client library freeze exception - I believe we got the last client lib through yesterday. 16:02:03 * smcginnis checks dashboard one more time... 16:02:24 Nice, it hasn't been down to that few patches in awhile. 16:02:34 Freeze all cycle-based library releases except for release-critical bugs. 16:02:47 We've had one requirements freeze exception that I've seen. 16:02:58 Otherwise, I think it's been mostly quiet on that front. 16:03:16 So just a reminder to make sure we get the ack from requirements before releasing anything new. 16:03:23 did the pypi problem tank any release builds? 16:03:35 Happily no. 16:03:39 just making sure i didn't miss anything which needed to get rerun 16:03:40 o/ 16:03:56 It happened at a quiet time, and the one or two outstanding we waited on. 16:04:03 oh good 16:04:06 So the window worked out well as far as releases go. 16:04:30 Not so much for the teams trying to get last minute things in, but awesome work that it finally got figured out. 16:04:53 Propose stable/$series branch creation for all client and non-client libraries that had not requested it at freeze time. 16:05:05 armstrong, ttx: I think I saw this earlier? 16:05:22 Ah, yep 16:05:24 #link https://review.opendev.org/752447 16:05:38 yes, worked like a charm 16:05:42 I thought there would be more. That's great. 16:05:58 List cycle-with-intermediary deliverables that have not been released in the last 2 months. 16:06:03 diablo_rojo: I think you sent out something? 16:06:18 smcginnis, yep the cwi deliverables that hadn't released in two months 16:06:47 (I also helped armstrong understand the script and what it was doing) 16:06:57 Excellent 16:07:08 There were like a half a dozen that hadn't released. 16:07:16 Havent run it again since Monday though. 16:07:21 So it may have improved. 16:07:31 Probably the same. I don't think I've seen anything come through. 16:07:41 Yeah I don't recall seeing anything either. 16:08:22 Looks like a few of those were things like requirements and tempest things, so really not too back. 16:08:33 The others are not too surprising. 16:09:29 Yeah there wasn't anything particularly concerning that I saw. 16:09:33 where is the list? 16:09:39 OK, bumped on the ML. 16:09:51 that same etherpad as last week too 16:09:51 ttx: Should see a recent one from me now. 16:09:58 But also the ML thread 16:10:20 heat-agents, karbor(-dashboard), swift (normally does late to get all changes in), and vitrage(-dahsboard). 16:10:42 ok 16:10:51 Last task is the countdown. 16:11:04 I should remember to send that out tomorrow. :) 16:11:14 #topic Possible victoria red flags 16:11:21 #link https://review.opendev.org/#/c/747419/ 16:11:46 yeah just wanted to flag that one 16:12:15 No updates for a few days now. I will comment on there. 16:12:28 the earliest we fix this the better 16:12:59 ttx: Anything more on that? I haven't been tracking it. 16:13:26 not really... just that it needs to be on our collective radar 16:13:31 +1 16:13:52 #topic Review countdown content 16:13:56 #link https://etherpad.opendev.org/p/relmgmt-weekly-emails 16:14:51 lgtm 16:15:13 I just made another pass through it and checked out for me too. 16:15:28 #topic Assign R-3 tasks 16:15:37 Process any remaining library branching exception. 16:15:51 That's for all of us. Keep in mind requirements freeze and make sure we follow process. 16:16:02 On the Monday, generate release requests for all deliverables that have do not have a suitable candidate yet. 16:16:16 Anyone want to try the new script I proposed for doing this? 16:16:44 Or I can take it. 16:17:11 OK, then just Send countdown email. 16:17:15 I can take that too. 16:17:15 smcginnis I am available to help 16:17:15 I can do it 16:17:27 The release proposals? 16:17:31 yeah 16:17:37 Cool, thanks. 16:17:40 I can team up with armstrong again 16:17:44 Would be good to get feedback on the tool. 16:17:46 That would be great. 16:17:52 great! ttx 16:17:58 Thanks! 16:18:03 same deal as today on Monday? 16:18:09 yes 16:18:13 noted 16:18:24 Perfect. 16:18:34 #topic Wallaby PTL 16:18:44 Monday same time? 16:19:01 For various reasons, I am not sure I can continue as release PTL for Wallaby. 16:19:33 Would be a good opportunity to someone else to step up. You would have the support of the rest of us to get going. 16:19:44 So no decisions need to be made on the spot here, 16:19:56 but wanted to raise this so others can start thinking about it. 16:20:08 Election time is coming up soon, so you have a little time to think about it. 16:20:26 And feel free to ask either me and/or ttx any questions about it. 16:20:53 hberaud is not here, pinging him in case he would be interested 16:21:11 obviously we'd still be around for questions and help 16:21:11 As everyone has seen, we have things pretty much automated and documented now, so there's at least not too much to have to know through tribal knowledge at this point. 16:21:29 Definitely. 16:21:37 Yay for the process doc! 16:21:47 #topic Open floor 16:23:26 Nothing more from me today. If no one else, we can wrap up. 16:23:49 Can we document an onboarding training for the release team? For example, the training that dhellmann gave some time ago 16:24:32 I think we added a link to that recording somewhere. 16:24:38 armstrong, I want to say that it is somewhere? 16:24:43 yeah, good reminder... ptl nominations open on tuesday just before utc midnight and last for a full week 16:25:04 also the tc has approved a "distributed leadership" alternative to the traditional ptl model, which you could consider 16:25:24 fungi: Good reminder. 16:25:36 diablo_rojo: can you locate it? 16:25:46 Not sure how that would work with this team, but we could certainly distribute responsibilities. 16:25:48 though i do wonder what the "release liaison" for the release team would do, as it's a required position ;) 16:26:02 We should add the training video to https://releases.openstack.org/reference/reviewer_guide.html 16:26:15 fungi: Haha, that's what I was thinking. :) 16:26:21 #link https://governance.openstack.org/tc/resolutions/20200803-distributed-project-leadership.html 16:26:29 (for reference) 16:26:36 Thanks 16:26:55 armstrong, I will take look later today and see if I can find things. 16:27:17 diablo_rojo: If you track that down, that would be great if you could propose adding a link to the release docs. 16:27:28 diablo_rojo: ok sounds good, thanks 16:27:47 smcginnis, will do one or the other depending on what I find :) 16:27:54 ++ 16:28:13 OK, I think we can close things up now. Thanks everyone! 16:28:28 #endmeeting