15:00:24 <smcginnis> #startmeeting releaseteam
15:00:25 <openstack> Meeting started Fri Sep 27 15:00:24 2019 UTC and is due to finish in 60 minutes.  The chair is smcginnis. Information about MeetBot at http://wiki.debian.org/MeetBot.
15:00:26 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
15:00:29 <openstack> The meeting name has been set to 'releaseteam'
15:00:33 <smcginnis> ping ttx dhellmann diablo_rojo hberaud evrardjp armstrong tonyb
15:00:36 <hberaud> o/
15:00:46 <smcginnis> Welcome to our special edition release team meeting.
15:00:59 <smcginnis> #link https://etherpad.openstack.org/p/train-relmgt-tracking Agenda
15:01:21 <smcginnis> Around line 564
15:01:26 <ttx> o/
15:01:31 <evrardjp> I am in a workshop, so I can't attend this meeting, sorry.
15:01:40 <smcginnis> Actually, line 515.
15:01:44 <smcginnis> I'm getting ahead of myself.
15:01:50 <smcginnis> evrardjp: ack, thanks.
15:02:16 <smcginnis> #topic autoreleases without any feedback
15:02:31 <smcginnis> I posted a reminder yesterday and then again today for these.
15:02:55 <ttx> So according to my newly-posted process we should approve those without feedback now
15:03:19 <ttx> I mean, not during meeting, but just after
15:03:28 <smcginnis> I agree, the ones without an explicit -1 should just go.
15:03:30 <smcginnis> We've tried.
15:03:44 * ttx checks recent updates
15:04:44 <smcginnis> I tried to get clarification, but I saw jokke mention glance would be "sometime early next week".
15:05:22 <ttx> yeah, so we should approve the ones were the PTL did not post anything, just after this meeting
15:05:26 <smcginnis> I would guess with the ones without any response, more than likely the tempest-plugin ones are good.
15:05:33 <ttx> FOr the ones with a standing -1. I propose we review them now
15:05:33 <smcginnis> dashboard probably too.
15:05:51 <smcginnis> +1
15:05:53 <smcginnis> #topic Discuss standing -1s on autoreleases
15:05:58 <smcginnis> Barbican
15:06:11 <smcginnis> #link https://review.opendev.org/#/c/684045/
15:06:27 <smcginnis> Says waiting for FFE, but I am not aware of one out there.
15:07:09 <ttx> Hmm yeah, let's ask for an update. and approve on Monday if there is none
15:07:27 <smcginnis> Just commented on that patch.
15:07:49 <smcginnis> Glance
15:07:51 <smcginnis> #link https://review.opendev.org/684060
15:08:06 <smcginnis> I believe that is held up by needing a FFE for glance_store.
15:08:20 <smcginnis> #link https://review.opendev.org/685050
15:08:41 <ttx> yeah, and a backport
15:08:59 <smcginnis> So that one is probably early next week based on needing to get the lib update out and then address whatever depends on that within glance itself.
15:09:12 <smcginnis> blazar-tempest-plugin
15:09:20 <smcginnis> #link https://review.opendev.org/684000
15:09:20 <ttx> yeah, maybe try to talk to erno/Abishek today about it
15:09:40 <smcginnis> I've pinged Erno but no response yet.
15:10:01 <ttx> Pierre is reactive, so I' inclined to trust him
15:10:02 <smcginnis> Blazar tempest plugin comment is that they are still merging some fixes.
15:10:11 <ttx> Surprised though
15:10:13 <smcginnis> OK, we can just wait on that one then.
15:10:15 <ttx> Maybe ask for an update
15:10:18 <smcginnis> Last update was on the 24th.
15:10:25 <smcginnis> I'll comment on there asking for the latest.
15:10:34 <ttx> might have slipped between the cracks
15:10:51 <smcginnis> Yeah, that's my hope.
15:10:52 <smcginnis> Heat
15:11:06 <smcginnis> #link https://review.opendev.org/684062
15:11:29 <smcginnis> ricolin commented it wasn't ready yet not long ago.
15:11:31 <ttx> woiuld be good to know what it is waiting on
15:11:38 <ttx> (in general)
15:11:51 <ttx> maybe ask for what it is waiting on
15:11:54 <smcginnis> There is also https://review.opendev.org/684008 waiting on ack for the tempest plugin.
15:11:56 <ttx> At this point we should know
15:12:00 <smcginnis> Agreed
15:12:26 <ttx> well that other one we'll approve now
15:12:33 <ttx> (post-meeting)
15:13:24 <smcginnis> monasca-api
15:13:26 <smcginnis> #link https://review.opendev.org/#/c/684031/
15:13:27 <ttx> witek is waiting for a substantial patch to merge.
15:13:42 <ttx> it's stuck in gate. Let's wait until Monday on this oen
15:14:01 <smcginnis> OK.
15:14:32 <smcginnis> #link https://review.opendev.org/#/c/684003/ congress-tempest-plugin
15:14:51 <smcginnis> That one Eric updated with a new hash but then left -1.
15:14:59 <smcginnis> I wonder if that was meant to be a +1.
15:15:17 <ttx> Maybe aslet me see the patch queue there
15:15:50 <ttx> yeah, it's emnpty
15:15:55 <ttx> so probably a misfire
15:16:07 <smcginnis> Only patches out there don't look like they are close to merging.
15:16:24 <smcginnis> Well, I guess we can wait a bit and see if we get a response.
15:16:28 <ttx> we should override the -1
15:16:39 <ttx> there is no patch up
15:17:15 <ttx> I +2, your call
15:17:22 <smcginnis> I commented on https://review.opendev.org/#/c/684003/2 if you want to approve.
15:17:26 <ttx> yes on it
15:17:31 <smcginnis> Oh, I see we both did.
15:17:46 <smcginnis> OK, mischief managed on that one I guess.
15:18:11 <smcginnis> #link https://review.opendev.org/#/c/684036/ monasca-persister
15:18:20 <ttx> On that one, knwoing what we are waiting on would be good
15:18:25 <smcginnis> I wonder if this is also held up by that large patch.
15:18:35 <ttx> could be. It's a pretty massive patch
15:18:51 <smcginnis> Wait a little longer for a response?
15:18:53 <openstackgerrit> Merged openstack/releases master: Auto release request for blazar  https://review.opendev.org/684047
15:18:57 <ttx> main reason why it does not make much sense to cut the stable branch before
15:19:07 <ttx> yes, but ask what is holding it up
15:19:27 <smcginnis> I had just commented their earlier, so we can wait for a response from witek.
15:19:39 <ttx> ok I'll ask
15:20:32 <witek> I think persister is ready, will update the hash
15:20:43 <ttx> hah, great! One down
15:21:24 <smcginnis> #link https://review.opendev.org/#/c/684072/ mistral
15:21:28 <smcginnis> Thank you witek
15:21:33 <ttx> On mistral, rakhmerov communicated this morning and we know what patches to track, so OK to wait a bit
15:22:01 <smcginnis> Looks like the two referenced are still in progress.
15:22:24 <ttx> yes
15:22:54 <smcginnis> #link https://review.opendev.org/#/c/685305/ Tricircle (take 2)
15:23:04 <smcginnis> We have the auto generated patch, and a new patch.
15:23:25 <ttx> the way I interpret that one is that it should wait until https://review.opendev.org/#/c/684159/ is approved
15:23:31 <ttx> but it's a bit unclear
15:23:48 <ttx> Let's regroup on Monday once China is awake
15:24:15 <smcginnis> No reviews for 3 days on the referenced change id.
15:24:25 <smcginnis> And it's a trivial patch that should not hold up anything.
15:24:32 <ttx> it is true
15:24:46 <smcginnis> Nothing else looks close to merging.
15:24:59 <ttx> Let me see if the autorelease still points to head
15:25:28 <ttx> yes it still does
15:25:31 <smcginnis> Yep
15:25:42 <smcginnis> I think there may just be some confusion there.
15:25:45 <ttx> Maybe comment on that other patch that we will approve https://review.opendev.org/#/c/684109 on Monday
15:26:02 <ttx> unless he comments there that we are waiting for another patch.
15:26:15 <smcginnis> Maybe we should just approve it today. Nothing inflight to wait for that I can see.
15:26:53 <ttx> I think he meant to include that constraint update patch
15:26:57 <smcginnis> Only think that looks sort of important is the py3 testing https://review.opendev.org/#/c/681481/
15:27:01 <ttx> which is generally a good thing to have
15:27:10 <smcginnis> That's nothing that should hold up a release.
15:27:16 <smcginnis> It's ultimately sort of a no-op.
15:27:22 <ttx> sure, but I think that is what he tried to express
15:27:34 <ttx> So I'm willing to give him until Monday to get that in
15:27:47 <smcginnis> OK, we can wait.
15:27:49 <ttx> But we need to leave a clearer / more actionable comment
15:27:58 <smcginnis> The lack of any core reviews on those concerns me though.
15:28:12 <smcginnis> And they are all easy enough to backport later if desired.
15:28:18 <ttx> the fact that he missed the autorelease concerns me
15:28:36 <smcginnis> Was he added as a reviewer?
15:28:39 <ttx> yes
15:28:47 <smcginnis> Hmm
15:28:56 <openstackgerrit> Merged openstack/releases master: Auto release request for congress-tempest-plugin  https://review.opendev.org/684003
15:28:59 <openstackgerrit> Pierre Riteau proposed openstack/releases master: Auto release request for blazar-tempest-plugin  https://review.opendev.org/684000
15:28:59 <smcginnis> So multiple causes for multiple concerns there.
15:29:03 <ttx> OK, let me leave a message on that one
15:29:07 <smcginnis> Thanks
15:29:13 <ttx> with clear action in case he does not react
15:30:16 <smcginnis> ++
15:30:29 <smcginnis> #topic Other train releases
15:30:40 <smcginnis> #link https://review.opendev.org/685050 glance_store
15:30:48 <smcginnis> FFE posted to the ML not long ago.
15:30:57 <smcginnis> I haven't checked if there was a response to that yet.
15:31:28 <smcginnis> I did ping prometheanfire to make sure he was aware of it though.
15:31:49 <smcginnis> My assumption is that is what is holding up the glance release.
15:31:58 <ttx> I did abandon the confused tricircle review so that we don;t have two
15:32:03 <smcginnis> #link https://review.opendev.org/#/c/682269/
15:32:05 <smcginnis> OK, good.
15:32:10 <openstackgerrit> Graham Hayes proposed openstack/releases master: Auto release request for designate-dashboard  https://review.opendev.org/684057
15:32:24 <smcginnis> Puppet OpenStack Train Milestone 3.
15:32:31 <fungi> #link http://lists.openstack.org/pipermail/openstack-discuss/2019-September/009752.html
15:32:33 <smcginnis> I was looking at that right before the meeting.
15:32:37 <smcginnis> I think that's OK to go.
15:32:46 <smcginnis> fungi: Thanks
15:32:53 <ttx> smcginnis: I already +2d so please go ahead
15:33:06 <smcginnis> Done
15:33:22 <smcginnis> I know we keep having these semver discussions with the packaging projects, but not sure what to do about it.
15:33:30 <ttx> mugsie just in time to avoid autorelease
15:33:38 <smcginnis> It's just going to keep coming up every time.
15:33:40 <fungi> and yeah, no replies to jokke's glance_store ffe request yet
15:33:45 <ttx> I don;t care that much, wahetever works for them
15:35:13 <smcginnis> I don't know where we can document "packaging projects are weird and don't bother them about not properly following semver" so new reviewers don't always flag it.
15:35:23 <smcginnis> But maybe now evrardjp will know at least. :)
15:35:39 <ttx> in the reviewers tips. And yes, he is well placed to document that
15:35:48 <ttx> coming from that weirdo crowd and all
15:35:56 <smcginnis> Haha
15:36:18 <smcginnis> OK, I think that's all for pending releases for now then.
15:36:22 <smcginnis> Monday will be busy.
15:36:22 <ttx> I'll +2 all the oens that we should autorelease now
15:36:27 <smcginnis> ++
15:36:30 <smcginnis> #topic R-2 email content final review
15:36:32 <ttx> Not that much
15:36:43 <smcginnis> #link https://etherpad.openstack.org/p/relmgmt-weekly-emails
15:36:52 <smcginnis> Line 499
15:37:43 <smcginnis> Not sure if we should be promoting holding off on stable branch creation like we have in that draft.
15:37:58 <smcginnis> But I suppose if it makes things easier for them.
15:38:22 <ttx> smcginnis: I guess we could check for new commits on those we are about to force. But that sounds like a lot of work
15:38:31 <smcginnis> Yeah
15:38:47 * fungi is curious what makes this meeting a special edition, but his flight is boarding so will find out later
15:39:23 <smcginnis> fungi: It's Friday and an hour early since I was traveling all week.
15:39:44 <smcginnis> And RC's are just so darn special.
15:40:08 <smcginnis> OK, the draft looks good to me. I can send that after the meeting.
15:40:43 <smcginnis> #topic Open discussion
15:40:45 <smcginnis> #link https://review.opendev.org/#/c/685327
15:40:56 <smcginnis> I like the clarity of that.
15:41:12 <smcginnis> Less room for errors in interpretation on when something should be done.
15:41:28 <smcginnis> ttx: Anything you wanted to comment on that?
15:41:43 <ttx> no, just that it is incremental work
15:41:49 <ttx> I'll clarify other weeks
15:41:55 <smcginnis> OK, thanks.
15:41:57 <ttx> Just a LOT of work to sync
15:42:02 <smcginnis> Yeah
15:42:13 <ttx> but it will avoid having to translate all the time
15:42:37 <ttx> Like I've done the work this time, would rather not leave it to interpretation for next time
15:42:37 <smcginnis> That will be important. We need things to be less work, even if we are doing more.
15:42:49 <ttx> I also included the temail template
15:42:53 <ttx> s
15:43:13 <ttx> that way it avoid duplicating info like "mention in the email"
15:43:52 <smcginnis> One other subject I wanted to bring up, at least to start thinking about.
15:44:03 <smcginnis> I'm going to email tonyb and see how things are going.
15:44:17 <smcginnis> I'm hoping he is just getting caught up on his day job and will be back.
15:44:44 <smcginnis> But either way, we may need to think about how we handle stable releases without really having regular "stable" people to review.
15:45:32 <smcginnis> Maybe mriedem can take over Tony's Monday stable review timeslot, but I think we actually just need to start treating them like normal releases that just require a little more scrutiny.
15:46:12 <smcginnis> So nothing we need to debate or decide here today, but I wanted to raise the topic for folks to start thinking about.
15:46:26 <openstackgerrit> Merged openstack/releases master: Puppet OpenStack Train Milestone 3  https://review.opendev.org/682269
15:46:42 <mriedem> feel free to ping me for stable release reviews
15:46:47 <smcginnis> Since at least for the last couple months, stable releases have kind of been up in the air with not having a clear process to follow.
15:47:01 <ttx> ++
15:47:26 <smcginnis> mriedem: Tony used to have a regular review task on Monday's so we could follow a process, but yeah, maybe we can just ping you for anything that we are not entirely sure on.
15:47:27 <ttx> smcginnis: you should be able to +2 all the ones with a +2.. except https://review.opendev.org/#/c/684031/ which should be considered a -1
15:47:32 <dulek> smcginnis: Hey, does it matter if kuryr-kubernetes has a release, but it's not having "rc1" suffix on its name?
15:47:54 <ttx> depends on its release model, let me check
15:48:07 <smcginnis> dulek: No, it's cycle-with-intermediary.
15:48:17 <smcginnis> Those do not do release candidates. So you should be all set.
15:48:21 <smcginnis> dulek: Thanks for checking!
15:48:31 <ttx> you just do releases, and teh latest is included in the global "openstack" release
15:48:56 <dulek> Okay, thanks!
15:49:20 <ttx> smcginnis: once all the silent are approved, we are not looking at too many exceptions
15:49:57 <ttx> The largest would be glance, which will block the post-RC1 process (since it's in the devstack default set I assume)
15:50:20 <smcginnis> Oh right.
15:50:29 <ttx> oh we should look at next week tasks
15:50:32 <smcginnis> Hopefully that doesn't take too long then.
15:50:36 <ttx> forgot to add that to agenda
15:50:45 <smcginnis> #topic Review next week's tasks
15:51:09 <ttx> so there is another round of autoreleases... to cut missing branches this time
15:51:11 <smcginnis> Proposing stable/train branches for deliverables that missed it.
15:51:32 <smcginnis> I can do that if no one else can, but would also be very happy to let someone else handle that.
15:51:38 <smcginnis> We have a nice script to do it at least.
15:51:49 <ttx> otherwise there is the whole post-RC1 process to coordinate with Ghanshyam
15:52:03 <ttx> once we have all the eggs in the basket
15:52:06 <smcginnis> Though last time I did them all in one patch and ended up with a job timeout, so maybe we should be more careful with how many we try to do at once.
15:52:21 <ttx> I probably won;t do much as I'm traveling and taking a day off on Londay too
15:52:24 <ttx> Monday
15:52:48 <smcginnis> Nordics should be fun.
15:52:51 <ttx> So I'' only take the email template
15:53:03 <smcginnis> Looks like it will be just me and evrardjp next week for the most part.
15:53:07 <ttx> yes
15:53:14 <smcginnis> OK, I will take care of the branching.
15:53:53 <smcginnis> The post-rc1 tasks for us are mainly reminding qa and requirements to do their things.
15:54:23 <smcginnis> I can also take the task to add release note links. That's another easy script.
15:54:51 <smcginnis> "Encourage liaisons" is just a countdown email reminder.
15:54:53 <ttx> Post-RC1 tasks you will need to coordinate with gmann
15:55:13 <ttx> ++ moves there
15:55:40 <smcginnis> OK, I think that's pretty much it.
15:56:09 <ttx> Added a "handle standing RC1 exceptions" task to the top
15:56:16 <ttx> ok
15:56:31 <ttx> I think we are good!
15:56:33 <smcginnis> OK, we can wrap it up then. Thanks!
15:56:40 <smcginnis> #endmeeting