16:01:50 <smcginnis> #startmeeting releaseteam
16:01:51 <openstack> Meeting started Thu Jan  3 16:01:50 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:52 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
16:01:54 <openstack> The meeting name has been set to 'releaseteam'
16:02:02 <smcginnis> #link https://etherpad.openstack.org/p/stein-relmgt-tracking Agenda
16:02:15 <smcginnis> #topic Roll call
16:02:32 <ttx> Hi!
16:02:42 <armstrong> O/
16:04:18 <smcginnis> Not much of an agenda in the etherpad. Please add any topics you want to discuss.
16:04:27 <smcginnis> But this is probably going to be a quick meeting.
16:04:45 <ttx> yes...
16:04:51 <armstrong> Ok
16:05:08 <ttx> challenge is getting people to wake up for stein-2
16:05:45 <ttx> where we should start making decisions for added deliverables
16:05:46 <smcginnis> I need to send the countdown email today. That will be my focus.
16:06:00 <smcginnis> #topic New deliverables
16:06:16 <smcginnis> ttx: Are there specific ones you are referring to?
16:06:29 * ttx looks
16:07:24 <ttx> We had a bunch in the gap analysis
16:07:36 <ttx> and it would be good to have those released at least once before stein-2
16:07:47 <ttx> if only to smooth out any release wrinkle
16:08:21 <smcginnis> Oh, repos that have been out there some time but never had an official release done?
16:08:41 <ttx> yes, those marked "New repository in Stein" in https://etherpad.openstack.org/p/UChiqxElUV
16:09:07 <tosky> do "new repositories from sahara plugins that we are trying to get out before M2" count as new deliverables, or is it about something else?
16:09:10 <ttx> I'll have to refresh that analysis, but I suspect most of them are still missing a deliverable file in openstack/releases
16:10:09 <smcginnis> tosky: I think this was something else, but those would be great too.
16:10:21 <smcginnis> tosky: Do you have some that will be ready soon?
16:10:56 <ttx> Basically there are a bunch of repos declared in governance that are not visible to release team because they don't have a deliverable file yet -- membership freeze means a devcision has to be made on those... and the new release process means we should either have them on -rc or have an internmediary release done already
16:11:15 <tosky> smcginnis: I sent the joints reviews (project-config and governance) few minutes ago, waiting for the results and the ack from the PTL, and we really want to have this done before M2, it has been in preparation for 2 cycles
16:11:57 <smcginnis> OK, great. Thanks tosky.
16:12:52 <smcginnis> ttx: Seems to be quite a few of those marked "new respository in Stein".
16:12:56 <ttx> maybe add a reminder to the membership freeze in the weekly reminder?
16:13:08 <smcginnis> I will add a note.
16:13:43 <ttx> not sure how we want to enforce that
16:14:00 <ttx> do we want to ask then to add an empty deliverable file if they plan to release in stein?
16:14:23 <smcginnis> That would at least help with tracking things.
16:14:29 <ttx> that would allow us to track it and avoid late surprises
16:14:50 <ttx> that's basically what membership freeze is... a deadline to declare stuff you'll want in the cycle
16:15:06 <ttx> and deliverable files are a way to "declare" that
16:15:09 <smcginnis> There's enough of them that it's hard to make a blanket decision if they are cycle-with-intermediary things or -rc.
16:15:14 <ttx> even if you don't have a release yet
16:15:23 <smcginnis> Works for me.
16:15:52 <ttx> I think that covers the "urgent" department
16:16:00 <smcginnis> Thanks.
16:16:05 <ttx> I'll take teh action of refreshing the list for our own tracking
16:16:31 <smcginnis> Thanks for doing that.
16:16:41 <smcginnis> #topic Resuming releases
16:16:57 <smcginnis> We held off on processing release requests over the holiday break.
16:17:11 <smcginnis> I think most of us are back now. We can probably get going on those things again.
16:17:26 <smcginnis> Anyone aware of any reason to hold off on doing any releases right now?
16:17:29 <ttx> yes, at least today to clear the backlog
16:17:41 <ttx> I'll be in tomorrow to help fixing stuff if anything breaks
16:17:49 <armstrong> @ttx: what happens if the put an empty file and keep it like that, will it be release emptied?
16:17:56 <smcginnis> Are you around fungi?
16:18:18 <fungi> yep!
16:18:19 <ttx> empty deliverable file? It will show up as missing in all release reports
16:18:27 <fungi> just following along with the meeting
16:19:05 <smcginnis> fungi: Are there any infra things going on that we should be aware of to hold off on processing releases?
16:20:25 <fungi> nope, there was a zuul restart last night americas time, and we've got one odd case with a stuck tripleo change in the gate which may or may not be related. other than that nothing out of the ordinary
16:20:38 <smcginnis> OK, thanks.
16:20:49 <fungi> also ovh-bhs1 is reporting a much lower quota than we expect
16:20:50 <smcginnis> So after the meeting I will start doing some reviews.
16:21:54 <smcginnis> #topic Open discussion
16:21:59 <smcginnis> Anything else for today?
16:22:03 <ttx> nothing
16:23:09 <smcginnis> OK, we can wrap it up then.
16:23:12 <smcginnis> Thanks everyone.
16:23:20 <smcginnis> #endmeeting