16:00:06 <smcginnis> #startmeeting releaseteam
16:00:07 <openstack> Meeting started Thu Sep 10 16:00:06 2020 UTC and is due to finish in 60 minutes.  The chair is smcginnis. Information about MeetBot at http://wiki.debian.org/MeetBot.
16:00:08 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
16:00:10 <openstack> The meeting name has been set to 'releaseteam'
16:00:14 <smcginnis> Ping list: ttx armstrong
16:00:18 <armstrong_> o/
16:00:20 <smcginnis> #link https://etherpad.opendev.org/p/victoria-relmgt-tracking Agenda
16:02:58 <smcginnis> Just waiting for ttx. He has a talk in ~40 minutes, so hopefully we can move through the agenda quickly.
16:03:22 <ttx> o/
16:03:24 <smcginnis> #topic Review task completion
16:03:32 <ttx> sorry damn overlapping meetings
16:03:40 <smcginnis> Process remaining lib freeze exceptions - think we're good there.
16:03:45 <smcginnis> ttx: no worries. I know how that goes.
16:04:06 <smcginnis> We've had one ffe. Otherwise, there are just a few stable branch patches out there for libs that did not include that.
16:04:18 <smcginnis> What do folks think - should we process those now?
16:04:25 <smcginnis> Most got responses, but a few without.
16:04:27 <diablo_rojo> o/
16:04:47 <smcginnis> The only one in question is oslo related to the focal testing upgrades. I have a message out to bnemec on that one.
16:05:09 <smcginnis> But at least the other ones I think can be processed.
16:05:24 <diablo_rojo> Yeah I say go for it.
16:05:56 <smcginnis> OK, we can get those out after the meeting then.
16:06:12 <smcginnis> Next weekly task, cycle highlights reminder.
16:06:22 <smcginnis> diablo_rojo: I think I saw you sent an email on that, right?
16:06:41 <diablo_rojo> I did yeah
16:06:48 <diablo_rojo> and a reminder yesterday
16:06:57 <smcginnis> Not a lot coming in so far, but at least a few have come in since then.
16:07:06 <smcginnis> Next, autoreleases for client libraries.
16:07:09 <diablo_rojo> Yeah I saw Nova and Cyborg so far.
16:07:18 <smcginnis> #link https://review.opendev.org/#/q/status:open+project:openstack/releases+branch:master+topic:victoria-client-lib
16:07:20 <diablo_rojo> There might be some others since I last looked
16:07:30 <smcginnis> diablo_rojo: I think that was it.
16:07:48 <diablo_rojo> Ah well... I guess we will see what happens
16:08:03 <smcginnis> Got a few client patches with -1, mostly waiting for some final updates to land.
16:08:19 <smcginnis> Then a bunch that will likely be no responses that we can process on Monday.
16:08:28 <diablo_rojo> Souns good.
16:08:39 <ttx> +1
16:08:44 <smcginnis> Evaluate any libraries that did not have any change merged
16:08:50 <smcginnis> diablo_rojo: You had an etherpad for that, right?
16:10:00 <diablo_rojo> I did
16:10:16 <smcginnis> #link https://etherpad.opendev.org/p/v-unreleased-deliverables
16:10:21 <smcginnis> Found it from yesterday.
16:10:23 <diablo_rojo> Thats the one :)
16:10:27 <diablo_rojo> I was just about to link it lol
16:10:31 <diablo_rojo> beat me to it
16:10:45 <diablo_rojo> So no regular libraries, just client ones.
16:11:18 * hberaud sorry I've a school meeting to address now
16:11:28 <smcginnis> hberaud: ack
16:12:10 <smcginnis> diablo_rojo: Did you check these to see if they have had changes merged?
16:12:44 <smcginnis> https://releases.openstack.org/reference/process.html#r-5-week-milestone-3 Bullet 4 is the full task details.
16:13:37 <smcginnis> Actually, I think the only libraries are the client ones, and those are Horizon plugins.
16:14:19 <smcginnis> ttx: I'm brain dead. Have we typically done horizon plugin releases as part of the client lib releases? I'd have to look because I can't remember right now.
16:14:31 <ttx> no
16:14:34 <smcginnis> I *think* those have usually waited.
16:14:58 <ttx> Usually they lag behind services since they are supposed to expose new features there
16:15:03 <diablo_rojo> So then only need to look at the non dashboard ones in the client-library list?
16:15:05 <e0ne> smcginnis: IMO, it's better to release plugins after horizon, but most of plugins have other release cycle model
16:15:06 <smcginnis> That makes sense.
16:15:22 <smcginnis> e0ne: Yeah, that's reasonable.
16:15:24 <ttx> so library -> services -> dashboard
16:15:37 <smcginnis> I wonder if we should be more explicit about that.
16:15:47 <diablo_rojo> That makes sense.
16:15:54 <ttx> One might argue that client libs also should lag behind services, but we usually need them for other servcies, so it's a trade-off
16:16:28 <ttx> dashboards on the other end can easily lag behind.
16:16:46 <smcginnis> So is horizon deadline the RC1 deadline? Or any time before official release? Or should they really be cycle-trailing?
16:17:48 <ttx> RC1
16:17:56 <ttx> I mean, like the services
16:18:29 <ttx> We only enforce libs
16:18:50 <ttx> so.. libraries -> client-libs -> everything else
16:19:03 <ttx> "everything else" deadline is RC1 really
16:19:15 <smcginnis> So for this specific task, I think we just need to care about the c-w-i deliverables that have not had any commits.
16:19:16 <ttx> even if we encourage feature freeze now
16:19:36 <smcginnis> Since those may not be "cycle-based" anymore if they did not require any changes this cycle.
16:19:56 <ttx> oh.
16:20:03 <ttx> So "refreshed" in that sentence means released.
16:20:28 <ttx> The trick here is to say: if you don;t release something soon, we'll pick a very old release
16:20:52 <ttx> and cut stable/victoria from it
16:21:03 <ttx> it's just a fair warning
16:21:21 <smcginnis> So the email should cover it. They've been warned.
16:21:50 <smcginnis> Which is the next task bullet in the list.
16:22:05 <ttx> let me clarify since I was not looking at the right line
16:22:39 <ttx> The goal of the warning on line 362 is to ask for an intermediary release ASAP as we don;t have anythign to fall back to
16:23:01 <ttx> The goal of the warning on line 380 is to recommend an intermediary release ASAP as we don;t have anything recent to fall back to
16:23:30 <ttx> So the one on line 362 is a bit more pressing
16:23:38 <smcginnis> But line 359 is just to prepare for 362?
16:23:40 <ttx> But I think we said we would just force releases if stuck
16:24:17 <ttx> No.. line 359 is like... this library is not moving anymore, should we just make it independent and not artrificially refresh it
16:24:40 <smcginnis> We've retagged the last release from the previous cycle before, just to have something, but it raises the question as to whether those deliverables are still cycle based or independent. Or just dead.
16:24:42 <openstackgerrit> Ivan Kolodyazhny proposed openstack/releases master: WIP. Release horizon 18.5.0 and tempest-horizon 1.1.0  https://review.opendev.org/751041
16:24:59 <ttx> or stable
16:25:40 <ttx> but yeah, let's just rerelease them if needed
16:25:52 <ttx> surprised there are so many
16:26:07 <diablo_rojo> So was there anything else we needed to do with the client-libraries that havent released yet?
16:26:16 <ttx> hmm wait
16:26:27 <ttx> I bet most of those had changes merged
16:26:51 <ttx> The check is to detect things that are not moving... but the command only places you halfway there, by listing things that have not been released
16:27:22 <diablo_rojo> Ohhhh okay so I also need to go through open reviews and double check those client libraries arent there
16:27:30 <ttx> yeah, not very fun
16:27:35 <diablo_rojo> I didn't do that part. I guess I misunderstood.
16:27:37 <diablo_rojo> Can do that today.
16:27:48 <ttx> the instructions are a bit unclear
16:27:56 <smcginnis> osc-placement is the only concerning one there I think. The rest are horizon plugins.
16:28:02 <ttx> and frankly it's a lot of work for little gain
16:28:10 <smcginnis> We should clarify the task. Any probably script it.
16:28:15 <diablo_rojo> It makes more sense to generate the list and then go through open reviews to pair it down more.
16:28:38 <smcginnis> Not necessarily open reviews though. It's whether anything has actually merged or not.
16:28:48 <ttx> smcginnis: are we looking at the same thing? I'm looking at https://etherpad.opendev.org/p/v-unreleased-deliverables
16:29:04 <smcginnis> Yep
16:29:36 <ttx> there is more than just osc-placement and horizon plugins in there :)
16:29:47 <smcginnis> But the task says
16:29:50 <smcginnis> "Evaluate any libraries"
16:30:02 <smcginnis> So the output includes a lot of stuff that does not apply.
16:30:08 <ttx> ah
16:30:18 <ttx> This is definitely not scripted enough
16:30:25 <smcginnis> Definitely
16:30:40 <ttx> We could just drop that one
16:30:47 <ttx> I'll add a note to discuss that, next time
16:30:58 <smcginnis> Should be able to get the list of deliverables we care about, then pull changes since last release of CYCLE-1.
16:31:01 <smcginnis> Good call.
16:31:03 <sboyron> what is already scripted ?
16:31:22 <smcginnis> sboyron: We have a script that gets the list of deliverables not released this cycle.
16:31:45 <smcginnis> But that's only part of the task, and the list of deliverables returned is more than what we are concerned with at this point.
16:31:49 <sboyron> smcginnis: ack
16:31:50 <ttx> need to jump off in 9 min
16:31:58 <smcginnis> Yeah, let's get going.
16:32:13 <smcginnis> Short story, but job failure was nothing to be worried about.
16:32:21 <smcginnis> #topic Review countdown email content
16:32:30 <smcginnis> #link https://etherpad.opendev.org/p/relmgmt-weekly-emails
16:33:42 <smcginnis> Looks fine to me. I just removed some of the Upcoming Deadlines that will now be past.
16:33:56 <diablo_rojo> Still reading but so far so good
16:34:16 <smcginnis> Will send tomorrow.
16:34:19 <smcginnis> #topic Assign R-4 tasks
16:34:19 <diablo_rojo> Looks good to me
16:34:24 <smcginnis> Process any remaining client library freeze exception.
16:34:28 <smcginnis> That's for all of us.
16:34:34 <diablo_rojo> Reviews!
16:34:39 <smcginnis> Freeze all cycle-based library releases except for release-critical bugs
16:34:54 <smcginnis> That's also for all of us. Don't approve any new releases unless there has been an approved FFE for it.
16:34:59 <diablo_rojo> Don't review!
16:35:05 <smcginnis> :)
16:35:14 <smcginnis> Propose stable/$series branch creation for all client and non-client libraries that had not requested it at freeze time.
16:35:23 <smcginnis> Scripty thing, so easy. Any takers?
16:35:38 <ttx> I can do it if nobody wants it
16:35:48 <smcginnis> Sold!
16:35:54 <smcginnis> List cycle-with-intermediary deliverables that have not been released in the last 2 months.
16:36:06 <smcginnis> Another script thing, but also need to send an email with results.
16:36:08 <smcginnis> Takers?
16:36:12 <diablo_rojo> Sure.
16:36:35 <smcginnis> Excellent. And I've got the countdown email.
16:36:42 <smcginnis> #topic Open floor
16:36:45 <smcginnis> Anything else?
16:37:14 <armstrong> Willing to do something ...
16:37:36 <diablo_rojo> I can give up my todo ;)
16:37:40 <ttx> armstrong: I can give you my task if you want :)
16:37:43 <smcginnis> armstrong: Maybe you can work with ttx on the branch creation script.
16:37:44 <diablo_rojo> LOL
16:37:48 <ttx> no! mine!
16:37:51 <smcginnis> :)
16:37:54 <ttx> yessss
16:37:54 <armstrong> ok sounds good
16:38:14 <smcginnis> ttx: Good luck with your talk. Looking forward to it.
16:38:31 <ttx> We can do that next Thursday my-afternoon/your-morning
16:38:35 <smcginnis> sboyron: If you were interested, take a look at bullet item 4 here - https://releases.openstack.org/reference/process.html#r-5-week-milestone-3
16:38:35 <ttx> armstrong: ^
16:38:48 <smcginnis> The list-deliverables script is in the openstack/releases repo.
16:38:50 * ttx jumps off
16:38:54 <smcginnis> ttx: o/
16:38:54 <sboyron> smcginnis ack
16:39:13 <smcginnis> sboyron: Some useful things under the tools/ directory too.
16:39:46 <smcginnis> Feel free to ask questions here if you are looking at anything and have any questions on anything.
16:39:54 <smcginnis> https://releases.openstack.org/reference/process.html is generally useful to look through too.
16:40:01 <smcginnis> OK, anything else today?
16:40:34 <sboyron> smcginnis will do
16:40:42 <diablo_rojo> Good luck ttx!
16:40:56 <smcginnis> OK, thanks everyone. Let's wrap up.
16:41:00 <smcginnis> #endmeeting