19:00:12 <tonyb> #startmeeting releaseteam
19:00:13 <openstack> Meeting started Thu Jun 20 19:00:12 2019 UTC and is due to finish in 60 minutes.  The chair is tonyb. Information about MeetBot at http://wiki.debian.org/MeetBot.
19:00:14 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
19:00:16 <openstack> The meeting name has been set to 'releaseteam'
19:01:26 <tonyb> diablo_rojo, armstrong, evrardjp, ttx, smcginnis dhellmann, fungi: Gentle reminder about the release team meeting
19:01:28 <ttx> o/
19:01:40 * fungi was already reminded, but thanks!
19:01:41 <tonyb> .... So I was 17secs late :(
19:01:51 <tonyb> better than last week though :/
19:02:03 <armstrong> I/
19:02:32 <armstrong> o/
19:02:54 <armstrong> Hi @tonyb
19:02:57 <tonyb> fungi: I figured your higlight would happen
19:03:01 <tonyb> hey armstrong
19:03:27 <fungi> i get highlights just from you thinking about my existence, tonyb
19:04:26 <tonyb> fungi: oooooh is that how it works ?
19:04:32 <smcginnis> o/
19:04:51 <tonyb> smcginnis: I wasn't sure if you were going to be here .... starting a new job an all
19:05:01 <diablo_rojo> o/
19:05:26 <smcginnis> In another meeting, but trying to pay attention. ;)
19:05:39 <tonyb> I think we have everyone ... dhellmann is traveling and evrardjp enjoys his evenings
19:05:43 <tonyb> smcginnis: okay cool
19:06:43 <tonyb> So we only have one agenda item
19:06:48 <tonyb> #topic Status of the weekly release email (last sent on R-26)
19:07:16 <tonyb> and I'm not really sure what to say about this ...
19:07:39 <ttx> I added it to discuss what is the desired state
19:08:05 <ttx> Do we want to do weekly updates ? If yes, how can we help in producing them ?
19:08:27 <tonyb> ttx: the tldr is Tony values it, and intended to do it but it never quite happens
19:09:08 <ttx> I feel like we did a bit too many of those in the past, but there are key ones that still need to happen
19:09:51 <tonyb> ttx: I don't have an opinion on the too many aspect but I agree we're definately missing them ATM
19:09:54 <ttx> I was wondering if we should not have a template that would automate 99% of it
19:10:07 <fungi> also they're mostly canned, right? could be delegated or even rotated?
19:10:14 <ttx> Taking last cycles as a base
19:10:15 <diablo_rojo> I don't think they really need to be weekly until like.. somewhere between m2 and m3
19:10:25 <fungi> oh, and here i just assumed they were already templated ;)
19:10:44 <ttx> fungi: They are not fully canned -- I resisted that a bit in the past (people tend to ignore canned stuff)
19:11:01 <tonyb> I guess they are kinda templateable
19:11:17 <ttx> But then canning does not prevent last minute customization if you want to apply your spice to it
19:11:31 <ttx> and it would help in quickly sending it if no time
19:11:32 <diablo_rojo> indeed it does not
19:11:40 <tonyb> there will always be stuff that needs to be added kinda ad-hoc'ish but I guess we could get most of it ...
19:12:29 <ttx> tonyb: My suggestion would be to dump all the ones from the previous cycle  in some etherpad, where we can continuously improve them
19:12:38 <fungi> right, presumably anything derived from the schedule could be added in an automated fashion and then you just work around that for the odd bits
19:12:48 <ttx> then when the week comes, you can just pick the current state and hit send
19:13:02 <ttx> Then we can discuss which ones should be skipped
19:13:24 <ttx> And we can help in updating the message
19:13:50 <ttx> We definitely need to have a tactic to apply before R-13
19:13:57 <fungi> i suppose it could be a standing weekly meeting item to go over what would be sent and work out if it's needed that week
19:14:03 <tonyb> Well we *kinda* have that already in that last cycle smcginnis but all the emails into etherpad(s) and I've pulling the ones for the matching weeks as a base
19:14:50 <ttx> I would place them all in the SAME etherpad, so that we can more easily tell which ones are superfluous and decide to skip them
19:15:03 <fungi> that smcginnis guy has so many great ideas
19:15:11 <ttx> If only he was around
19:15:45 <ttx> tonyb: if the content is mostlt team-drafted in advance, do you think you can post it regularly ?
19:15:57 <tonyb> okay, I'll do that (pull everything into on etherpad today)
19:16:02 <ttx> or is the blocker elsewhere?
19:16:08 <tonyb> ttx: Yes I can do that
19:16:31 <ttx> I can do a pass at looking up the content for the coming weeks once it's all in one etherpad
19:16:33 <tonyb> ttx: nope the blocker is partially creative and partially time
19:16:45 <tonyb> both of which would be solved by the current suggestion
19:16:49 <ttx> I'm pretty sure we can skip a lot between t1 and t2
19:16:50 <diablo_rojo> If there are weeks you are out/can't send the emails, I suppose I could.
19:16:54 <diablo_rojo> tonyb, ^
19:17:25 <tonyb> like the week I am AFK in July :)
19:17:36 <diablo_rojo> Heh yeah sure :)
19:18:08 <fungi> if the important bits are derived from the schedule and/or some scripted queries, and there's a couple minutes in the meeting to go over that and add/remove anything that's come up, seems like it should be pretty easy for just about anybody to send it out
19:18:51 <tonyb> fungi: Yup I agree
19:19:05 <ttx> yes, we can do a last-minute revoew of the content
19:19:24 <fungi> even on weeks when the ptl isn't otherwise indisposed
19:19:26 <ttx> The real difference is that there is a base content available for quick send if all else fails
19:19:47 <ttx> and I think that will help
19:20:17 <tonyb> Okay I;ll do this and drop a link here when it's done
19:20:38 <tonyb> I'll start today and try to have it done by Monday
19:20:46 <ttx> ++
19:21:42 <tonyb> ttx: Thanks for brining it up
19:21:55 <ttx> I was wondering if I missed the memo :)
19:22:45 <tonyb> ttx: Nope I'm just flailing a little
19:22:50 <diablo_rojo> ttx secretly loves email
19:23:51 <tonyb> I think we're done with that topic? (thanks again)
19:24:00 <ttx> yes, and I had nothing else :)
19:24:53 <tonyb> #topic open discussion
19:25:27 <tonyb> Anyone have anything?
19:26:00 <fungi> heads up, on monday we're removing some old v2 backward compatibility shims from non-legacy jobs
19:26:52 <fungi> it might be wise to keep an eye out for immediate breakage monday into tuesday at least, and maybe suspend release approvals if there seems to be an increased risk of some projects being affected
19:27:06 <fungi> though i suspect the impact to release jobs should be minimal or nonexistent
19:27:14 <tonyb> okay cool
19:27:39 <fungi> #link http://lists.openstack.org/pipermail/openstack-discuss/2019-June/006888.html Long overdue cleanups of Zuulv2 compatibility base configs
19:28:44 <tonyb> So should we offically try to clear the (release) queue today and just leave it until Wednesday UTC?
19:28:54 <tonyb> or would that be over reacting?
19:29:04 <tonyb> don't wnat to make life harder for y'all
19:30:23 <ttx> I don;t think we need to do anything special -- just be careful on Monday/Tuesday
19:30:36 <ttx> (i.e. approve one by one and keep an eye on them)
19:30:54 * diablo_rojo makes note
19:31:55 <tonyb> okay
19:32:20 <fungi> yeah, be vigilant and give me or anyone else involved a heads up if you see something you think could be related to that
19:32:40 <fungi> so we can help fix or rerun stuff quickly
19:33:19 <tonyb> okay
19:33:27 <fungi> this was stuff that should have been removed well over a year ago, but because we didn't get around to it we don't know what new jobs may have quietly grown dependent on those migration conveniences
19:34:10 <tonyb> fungi: Yeah it's good for it to go
19:34:39 <fungi> non-legacy jobs will save a fair amount of unnecessary overhead
19:36:15 <tonyb> So I'll probably skip +Wing anything on my Monday as I live in the future and don't want to pester ianw
19:37:23 <tonyb> anything else?
19:37:58 <ttx> nope
19:38:44 <tonyb> #endmeeting