16:00:05 #startmeeting releaseteam 16:00:06 Meeting started Thu Oct 10 16:00:05 2019 UTC and is due to finish in 60 minutes. The chair is smcginnis. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:00:07 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 16:00:08 Ping ttx dhellmann diablo_rojo hberaud evrardjp armstrong tonyb 16:00:09 The meeting name has been set to 'releaseteam' 16:00:16 o/ 16:00:17 #link https://etherpad.openstack.org/p/train-relmgt-tracking Agenda 16:00:19 o/ 16:00:30 o/ 16:00:31 We're way, way down around line 588 16:00:33 o/ 16:01:12 This is probably it, so I'll get going. 16:01:15 last meeting before the release! 16:01:19 #topic Review last RCs and intermediary releases before pre-release freeze 16:01:23 The end is near! 16:01:25 close to the station 16:01:37 don;t forget your luggage 16:01:41 * fungi can hear the whistles 16:01:49 https://media1.tenor.com/images/ccd17b9c51655f059745ea8ab0b205eb/tenor.gif?itemid=6164113 16:01:54 The train whistels? 16:02:16 #link https://tiny.cc/ReleaseInbox 16:02:26 I think we're looking pretty good. 16:02:35 Hopefully proposing those RC2 patches helped. 16:02:45 I think it did 16:02:49 Waiting on some patches to land for Glance and the sahara-plugin ones. 16:02:57 I documented it as a R-1 step 16:03:06 Oh good. 16:03:19 I think with us proposing the other releases, some teams are starting to just rely on that. 16:03:27 So probably makes sense that we follow that through. 16:03:44 i can see where they may find it a convenience 16:04:12 so which one will be abandoned due to lack of PTL+1? 16:04:18 I've only had one person be a little annoyed at us for proposing patches for them, the rest of the feedback I've received has been very positive. 16:04:21 trove? 16:04:24 Yep 16:04:29 That's not too surprising. 16:04:43 Some good bug fixes in there, but nothing that can't wait until a stable release. 16:04:51 right.\ 16:04:57 given lxkong just sent e-mail to the ml saying trove is now officially down to one core reviewer 16:05:10 Oh, missed that. Yikes. 16:05:24 yeah, he removed all reviewers besides himself from the core team in gerrit 16:05:29 How much do you want to wait for glance & sahara-plugin? 16:05:47 I know the glance one is on the way. 16:06:03 NB: I won;t be around tomorrow, took the day off 16:06:04 And the sahara-plugin team is actively working on some patches, so I think we can give them some time. 16:06:30 I can watch for these later today, and if necessary I can wait until tomorrow morning. 16:07:21 and generate the patch tomorrow after sending the countdown email declaring the freeze? 16:07:30 works for me 16:07:46 Yeah, I'll generate the final patch as soon as the last one lands. 16:07:58 We ended up needing to do a couple updates last cycle. Hopefully we can avoid that this time. 16:08:00 (the countdown email says " we are in pre-release freeze" so it's good to send after the last RC merged 16:09:07 Good point. 16:09:40 The other ones out there are cycle-trailing or not release dependent patches. 16:09:56 Not sure what's up with the two puppet-cloudkitty releases. 16:10:42 So I'll watch those and push through anything once the teams are ready. 16:10:45 #topic R-0 email content final review 16:10:58 #link https://etherpad.openstack.org/p/relmgmt-weekly-emails 16:12:17 If you modify it let me know 16:12:28 so that I can update the process update patch 16:12:40 (or better , update the process update patch yourself) 16:12:43 I think the only thing I might modify is adding the link to the actual final patch. 16:13:04 yeah, on that topic... do we want a single patch? 16:13:16 IIRC it triggered some issue with long processing times 16:13:33 which is why i kept it a bit fuzzy 16:13:57 Hmm, I *think* the final release patches have been OK, but it might be safer to break that out into multiple patches. 16:14:30 If anything, so we can limit needing to get +1s from PTLs if we need to actually do critical releases and update before the end. 16:14:30 yeah, we did hit timeouts on them previously, but i think that was at rc1 due to branch creation? 16:14:43 Yeah, that sounds about right. 16:14:49 I think the tag creation is fairly quick. 16:15:21 hmm ok 16:15:43 worth looking back at the stein release day channel log i guess 16:15:48 I'll try to break that out into a few separate patches to play it safe. 16:15:52 Doesn't hurt. 16:15:57 so yeah, just update https://review.opendev.org/#/c/687840/ if you change teh wording 16:16:05 Sounds good. 16:16:13 #link Review next week tasks 16:16:31 I think it's pretty clear 16:16:39 PR is scheduled for 9am CT 16:16:46 Timing-wise - do we need to coordinate with anyone at the foundation ttx? 16:17:17 So approve early Wednesday morning for me if we want a couple hours before that 9am target. 16:17:22 Hmm, let me doublecheck 16:17:36 ttx: Do you want to take that task to make sure it's done in time? Otherwise I can make sure I'm awake early. 16:18:21 checking 16:18:21 Id offer to help, but it would be like.. 4AM or something for me. 16:18:33 I can totally start things earlier 16:18:34 Hah, yep 16:18:47 if you have your +2 in there I can do it 16:18:56 i'll try to be awake earlier than usual on wednesday 16:18:56 ttx: If you get it started, I can try to get online and help monitor things early. 16:19:07 fungi: Aren't you always awake? 16:19:09 confirmed PR going out at 9am 16:19:14 k 16:19:17 CT 16:19:24 smcginnis: i enter a low-power standby mode while recharging 16:19:30 ;) 16:19:36 so yes I'll do the W+a 16:19:40 W+1 16:20:01 OK, next is checking missing-releases. 16:20:06 I'll do it 16:20:12 i thought W+a was a new chmod mask 16:20:22 I guess I can take that. 16:20:34 Oh, nope, ttx has it. Perfect. :) 16:20:52 I can update the series status to mark as released. 16:21:03 Let me do some timezone math 16:21:10 And the default series. 16:21:15 9am CT is 14utc 16:21:23 Correct. 16:21:30 I'll approve the first patch 2 hours before, 12utc 16:21:43 Switches at the beginning of Nov. 16:21:53 then run missing-releases once that is completed 16:21:53 that's 8am where i am, so totally doable for me to be around 16:22:10 smcginnis: we'll wait for you to approve the rest 16:22:14 Could even do it a little earlier than 12utc if it looks like things are ready. Just to give a little extra time. 16:22:25 if you could join around 13utc that would be perfect 16:22:54 Should be good, that's about my normal time but I'll set an alarm to be safe. 16:23:22 ok all set 16:23:27 Back to other tasks, I'll plan on sending the release announcement. 16:23:43 And the openstack-discuss one. 16:24:10 And ttx has the final task of updating the process. 16:24:24 hopefully a noop 16:24:37 ++ 16:24:51 #topic Team photo 16:25:10 Super important topic ;) 16:25:15 Final thing - I've signed us up for a team photo at the PTG on Thursday morning at 9:30. 16:25:22 Anyone see any issues with that time slot? 16:25:31 Other than that some of the team won't be there at all. :/ 16:25:55 Tony let me know he will be in Shanghai, so looking forward to that. 16:26:04 Yay! 16:26:12 That's good news 16:26:27 Hopefully no more visa mishaps like in Denver. 16:26:38 * ttx looks up brand-new http://ptg.openstack.org/ptg.html 16:26:59 yes that should work for me 16:27:24 #topic Open discussion 16:27:25 Should also work for me 16:27:37 That's all for the meeting agenda. Anything else? 16:27:38 i'm still waiting to find out whether i have a visa, but hope to be there 16:27:56 Hoping it works out. 16:28:36 OK, I guess that's it then. Thanks everyone. 16:28:49 thanks smcginnis! 16:28:55 thanks smcginnis ! 16:29:00 Thanks smcginnis! 16:29:07 Happy late Rc processing tomorrow 16:29:40 #endmeeting