16:01:09 #startmeeting releaseteam 16:01:11 Meeting started Thu Feb 21 16:01:09 2019 UTC and is due to finish in 60 minutes. The chair is smcginnis. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:01:12 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 16:01:14 The meeting name has been set to 'releaseteam' 16:01:16 Ping list: smcginnis ttx dhellmann diablo_rojo hberaud evrardjp fungi armstrong 16:01:20 o/ 16:01:23 #link https://etherpad.openstack.org/p/stein-relmgt-tracking Agenda 16:01:27 * dhellmann is on a call but will lurk 16:02:33 o/ 16:02:38 o/ 16:03:16 Alright, guess we can get going. 16:03:35 #topic Lib freeze and upcoming deadlines 16:03:46 We are already hitting non-client lib freeze. 16:03:58 It's been a longer cycle, but this always seems to come up quick. 16:04:20 Especially for the new folks, the following week is a lot of deadlines. 16:04:39 Stein-3 is also soft string freeze, feature freeze, client lib freeze, and probably some project specific deadlines too. 16:05:15 I should check with prometheanfire if we are still planning in requirements freeze too. 16:05:44 So next week might be a little more active with release activities. 16:06:01 And the stein-3 week probably more so. 16:06:13 Any questions on any of that? 16:06:40 yeah, we should try to make sure we get those lib releases out quickly to allow for testing 16:07:08 There does always seem to be a few surprise lib updates that break things in unexpected ways. 16:07:17 So please do pay attention to reviewing those. 16:07:31 The more time to recover from those situations, the better. 16:07:37 smcginnis: ya, freeze period is coming up 16:07:52 prometheanfire: Anything changing there, or same as we have done in the past? 16:08:07 same as the past 16:08:13 prometheanfire: Going to send out any new witty batman posts? :P 16:08:23 ahah 16:08:51 or A song of ice and fire/Game of throne memes 16:09:03 Ooh, that could be the new theme. 16:09:27 #topic Task follow up 16:09:42 #link https://etherpad.openstack.org/p/stein-email-r6 Countdown email draft 16:09:55 Pretty much all of the tasks for the week related to content for the countdown email 16:10:09 Please take a look there and feel free to make any suggestions for content changes. 16:10:30 Thanks evrardjp and diablo_rojo for getting the c-w-i project list and the good discussion on that yesterday. 16:10:52 smcginnis: I'll see if I can find a new theme 16:11:03 I think I would like to keep that list limited to the non-client things this week and point out the client ones next week. 16:11:04 Harry Potter? 16:11:06 prometheanfire: ;) 16:11:26 +1 to separating the lists to avoid overwhelming readers 16:11:37 I did mention in there that folks need to be aware of the client feeze, so nothing should be too surprising. 16:11:38 I didn't do anything -- just use the tooling. Great tooling, hard to have the whole overview of things in head though 16:11:39 GoT seems good, but I'll look into it 16:12:00 evrardjp: Figuring out what tooling is there and how to use it is a good thing to go through though. 16:12:07 mail looks good 16:12:31 The other task was one for fungi for the signing artifact. 16:12:39 Not sure if he's around right now though. 16:12:41 prometheanfire : the "freeze is coming" lines write themselves 16:12:45 o/ 16:12:52 Hey hberaud 16:13:37 #topic Upcoming tasks 16:13:40 #link https://releases.openstack.org/reference/process.html#final-library-release-week-before-milestone-3 16:13:58 dhellmann: Do you know if we are still doing bullet 4 there? ^ 16:14:07 looking 16:14:19 i have not yet gotten to the signing key generation yet, but it is near the top of my to do list 16:14:19 I seem to remember creating patches for that but them getting abandoned or something. 16:14:29 Or the qa team already having taken care of it. 16:14:30 as far as I know we do still need to do that 16:14:35 fungi: ack, thanks! 16:14:35 maybe that's what happened? 16:14:42 would be good to coordinate with them 16:14:51 Yeah, that might have been it. 16:15:31 Any volunteers to ping in -qa about that task and make sure they are aware of it and see if they need us to do anything or if they have it covered? 16:15:43 * smcginnis looks over in evrardjp and diablo_rojo's direction 16:15:55 * diablo_rojo reads bullet 4 16:16:27 Basically just need to make sure they are aware of the end of cycle activities coming up and are ready for it. 16:16:36 Oh sure 16:16:38 I can do that 16:16:44 Awesome, thanks diablo_rojo 16:17:17 diablo_rojo: I've put it down in the etherpad for next weeks tasks as a reminder. 16:17:56 #topic Open floor 16:18:04 smcginnis, got it! Thanks :) 16:18:09 I think overall we're in good shape. 16:18:17 Anything else anyone wants to talk about? 16:18:28 how do you qualify good/bad shape? 16:18:55 We haven't had to say "Oh crap, I forgot we were supposed to do that" yet. :) 16:19:10 *yet :-) 16:19:14 :D 16:19:16 ;) 16:19:19 Good documentation will help with that lol 16:19:29 So long as you actually read the docs 16:19:45 Yeah, as long as we are good about paying attention to process.rst, we should be fine. 16:19:53 Great documentation of everything that needs to be done there. 16:20:08 But if anyone comes across something that has been more tribal knowledge so far, please do add to that. 16:20:12 ++ 16:20:24 Ideally anyone could step in and just follow that guide to run a release. 16:20:47 smcginnis: I think diablo_rojo and I should do that with your help 16:21:03 That would be great! 16:21:18 OK, anything else for today? 16:21:18 you bring the beer, we bring the manpower 16:21:22 nothing 16:21:26 I got nothing 16:21:27 evrardjp: How was the Westvleten? 16:21:33 :D 16:21:39 :D 16:21:47 nothing here 16:21:47 we should close the meeting first 16:22:02 but it was amazing 16:22:08 evrardjp: You don't want that logged for all time in the meeting logs? :) 16:22:12 #endmeeting