16:03:41 <tiffanie> #startmeeting openstack_ansible_meeting
16:03:42 <openstack> Meeting started Tue Oct  8 16:03:41 2019 UTC and is due to finish in 60 minutes.  The chair is tiffanie. Information about MeetBot at http://wiki.debian.org/MeetBot.
16:03:43 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
16:03:46 <openstack> The meeting name has been set to 'openstack_ansible_meeting'
16:03:55 <noonedeadpunk> o/
16:04:01 <tiffanie> #topic office hours
16:05:27 <jrosser> o/
16:05:46 <noonedeadpunk> so, we're kinda late regarding milestone as it's already branching time
16:06:13 <jrosser> yes, only today are we really able to merge anything again
16:06:14 <noonedeadpunk> And we kinda might start using parts of ussuri as project might eventually go on
16:07:11 <noonedeadpunk> Yep, and it's really great that gates are unlocked:)
16:07:26 <guilhermesp> o/
16:07:35 <cjloader> o/
16:08:11 <noonedeadpunk> but we kinda need to place hold patch for milestone to propose for milestone into releases repo
16:08:29 <noonedeadpunk> cjloader: how's your ironic stuff is doing?
16:08:59 <cjloader> having some issues with deploying it
16:09:19 <cjloader> so i'm playing around with it still
16:09:38 <cjloader> should have good idea by end of week
16:09:51 <noonedeadpunk> ok, I see.
16:10:14 <noonedeadpunk> so folks, can you check freeze patch for the milestone? https://review.opendev.org/#/c/681002/
16:11:32 <noonedeadpunk> cjloader: so if you need some help you can reach us:)
16:11:46 <cjloader> but not on the ironic side, mostly galera issues
16:12:16 <cjloader> ok will do
16:12:29 <jrosser> noonedeadpunk: can you quickly explain the steps we have to do for a release, i'm not partiularly familiar with the process
16:12:41 <jamesdenton> o/
16:15:15 <noonedeadpunk> So yes. so yes.. first of all, we needed to merge milestone like several weeks ago (but we didn't due to instanly locked gates). After milestone is placed, we do branching.
16:15:48 <noonedeadpunk> To do both we need to freeze our roles, create a patch to releases repo with freeze sha, and then unfreeze roles
16:16:03 <noonedeadpunk> The same process is with pranching.
16:16:19 <noonedeadpunk> Also evrardjp kindly described steps to be done here https://review.opendev.org/#/c/686583/
16:17:30 <noonedeadpunk> As I'm not rly good in explaining :(
16:18:23 <evrardjp> sorry I am in another meeting.
16:18:38 <evrardjp> but yeah that's the gist
16:24:20 <jrosser> so when we branch, so we need to backport everything that has merged since the freeze to the new train branches?
16:24:57 <noonedeadpunk> Basically yes.
16:25:13 <noonedeadpunk> But the train branch freeze is expected to be https://review.opendev.org/#/c/686573/
16:26:59 <jrosser> wow thats very broken
16:27:11 <noonedeadpunk> yep:(
16:27:52 <noonedeadpunk> But I guess that it should include recently merged role patches
16:28:04 <noonedeadpunk> which it currently doesn't
16:28:38 <jrosser> it just feels like in 12/24hours we will have a much more coherent set of SHA given what has merged today
16:28:48 <jrosser> so long as we don't break everything again :)
16:29:28 <jrosser> i'm nervous of the patches which introduce more widespread tempest tests
16:29:37 <jrosser> that could wedge up everything
16:30:02 <noonedeadpunk> I guess I've missed them
16:36:36 <cjloader> unless my ironic stuff merges
16:36:40 <cjloader> =)
17:05:14 <tiffanie> #endmeeting