16:00:08 <hberaud> #startmeeting releaseteam
16:00:08 <openstack> Meeting started Thu Oct 22 16:00:08 2020 UTC and is due to finish in 60 minutes.  The chair is hberaud. Information about MeetBot at http://wiki.debian.org/MeetBot.
16:00:09 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
16:00:11 <openstack> The meeting name has been set to 'releaseteam'
16:00:22 <damani> hi
16:00:24 <hberaud> #link https://etherpad.opendev.org/p/wallaby-relmgt-tracking Agenda
16:00:54 <fungi> ohai
16:00:56 <elod> o/
16:02:26 <hberaud> #topic Setup wallaby
16:02:49 <hberaud> before going any further we will start with setup our future meetings
16:03:54 <hberaud> If you want to be notified at the begining of each meeting then don't hesitate to put your name in the Ping List (line 13 of our etherpad ^^^^^ )
16:05:00 <hberaud> also if you plan to schedule some review days do not hesitate to put your name on our "Review days (lines 16-20)"
16:05:30 <hberaud> else as you surely already know Wallaby is now on the rails
16:06:16 <ttx> I'm in
16:06:20 <hberaud> and all the related tasks above (etherpad) have been processed
16:06:23 <damani> hberaud, yes sorry i will put my name for the notification
16:06:33 <hberaud> damani: np :)
16:06:46 <damani> i will put also my name for the code review
16:06:48 <damani> :)
16:06:55 <hberaud> nice
16:07:16 <hberaud> well next topic
16:07:19 <hberaud> #topic Gerrit-breach
16:07:42 <hberaud> so just few words about this, it seems that we are ok on our side
16:07:57 <damani> yes
16:08:05 <hberaud> AFAIK nobody complained about something
16:08:11 <openstackgerrit> Daniel Bengtsson proposed openstack/releases master: New bugfix release for oslo.messaging for ussuri.  https://review.opendev.org/759289
16:08:27 <armstrong> o/
16:08:45 <ttx> yep
16:08:59 <smcginnis> Yeah, I didn't see anything odd.
16:08:59 <hberaud> armstrong, smcginnis: FYI don't hesitate to put our name in our Ping list
16:09:22 <hberaud> well next topic
16:09:26 <hberaud> #topic Clarifying why heat's victoria release note list all versions
16:09:42 <smcginnis> That appears to be the open bug with reno.
16:09:50 <armstrong> smcginnis ok I will do that now, thanks
16:09:59 <hberaud> I missed that one
16:10:11 <hberaud> good to know
16:10:40 <hberaud> ricolin: FYI ^^^
16:10:53 <hberaud> ricolin: and https://storyboard.openstack.org/#!/story/2008139
16:11:14 <hberaud> next
16:11:19 <hberaud> #topic Clarifying how to manage Extended maintenance and EOL branches
16:11:51 <elod> first of all, I offer my help for any tasks regarding Extended Maintenance process :)
16:12:05 <hberaud> lol
16:12:43 <hberaud> I started to write a test https://review.opendev.org/#/c/758990/ to check delta between our status and existing branches on the projects sides
16:12:59 <smcginnis> elod: Thanks for getting that email sent out.
16:13:24 <hberaud> I'll add some process to our doc to clarify thing on our side
16:13:39 <elod> smcginnis: np
16:14:01 <hberaud> but I think the stable team should ensure that patches are -2 on eol branches as elod suggested
16:14:23 <elod> hberaud: yes, I can help with that :)
16:14:43 <smcginnis> fungi: Anything we can trigger after an -eol tag that would tell gerrit to block those right off the bat?
16:14:43 <elod> nevertheless, some automation would be good to not to miss any such case
16:15:13 <hberaud> Also I don't know if zuul could ignore these branches if they are eol, I don't think is it possible, isn't?
16:15:25 <smcginnis> I suppose if we make sure the branch is deleted in a timely manner after that tagging, then we don't have to worry about it.
16:15:40 <hberaud> +1
16:16:05 <hberaud> I think our process should say to notify ASAP the infra team
16:16:20 <hberaud> I don't think we need the right to drop the branches
16:16:41 <hberaud> this could be done by simply asking the infra, thoughts?
16:17:03 <hberaud> s/the/to/
16:17:21 <elod> actually Infra team said that they need to be sure that the EOLing is OK from release team perspective, If i understand correctly
16:17:31 <hberaud> yep
16:17:50 <hberaud> so if we ask them I think we could consider that this is ok for us
16:18:05 <elod> yes, that's ok
16:18:11 <hberaud> awesome
16:18:15 <smcginnis> I'd say our approval of the tagging request is the release team approval of it.
16:18:32 <hberaud> +1
16:18:39 <elod> that's also true :)
16:19:00 <hberaud> so either the infra schedule periodical checks on our side
16:19:08 <hberaud> or we noticed them
16:19:53 <hberaud> s/noticed/notify/
16:19:55 <hberaud> sorry
16:20:02 <hberaud> as you want
16:20:17 <elod> both sound ok to me,
16:20:25 <hberaud> fungi: any preferences?
16:20:43 <elod> of course if we can figure out any way we can do it more straightforward, then it would be even better
16:21:16 <fungi> we could update acls for projects to block proposed changes for those branch patterns, i think
16:21:35 <fungi> but might make more sense to just use that as an indication that the branch should be deleted at the earliest opportunity
16:21:43 <hberaud> it will be awesome
16:21:58 <smcginnis> ++
16:22:23 <hberaud> to avoid to spend time to track new patches and chase them for -2
16:22:29 <fungi> newer gerrit we're upgrading to will allow us to grant branch deletion via api as a specific permission, so we could do some automation there
16:22:52 <hberaud> awesome
16:23:11 <fungi> so in theory it could be automated from the releases repo at that point
16:23:12 <hberaud> maybe it could be triggered from our side
16:23:24 <fungi> yeah, similar to the automated branch creation
16:23:29 <hberaud> fair enough
16:23:33 <hberaud> thanks
16:23:45 <elod> thanks fungi !
16:23:52 <hberaud> #topic Next meetings/weeks
16:24:16 <ttx> Looks like it's a noop now
16:24:27 <hberaud> no meeting will happen during the next 3 weeks
16:24:32 <hberaud> yep
16:24:33 <smcginnis> fungi: Do we have a planned timeframe for that gerrit upgrade yet?
16:24:43 <ttx> there were a bunch of duplicated tasks in the etherpad I looked up this morning
16:24:44 <fungi> smcginnis: mid-november it's looking like
16:24:49 <smcginnis> Great!
16:24:58 <hberaud> ttx: I dropped them
16:25:00 <fungi> not sure if this weeks events will alter our timeline at all
16:25:05 <ttx> well, we'll have a PTG meeting next week, but otherwise yes
16:25:09 <smcginnis> I was wondering about that.
16:25:34 <ttx> It's the low tide season for release management, so enjoy it!
16:25:44 <hberaud> #topic Open Discussion
16:25:54 <ttx> also if we have development to do after PTG discussions, it's a great time to do it now
16:26:10 <hberaud> agreed
16:26:25 <hberaud> anything else?
16:26:37 <fungi> do development now after ptg discussions? i'm not quite sure how to parse that suggestion
16:26:56 * fungi goes looking for his time machine
16:26:59 <smcginnis> It's much more efficient to do the development before you discuss it. :D
16:27:42 <fungi> oh, i think i get it. saying the time immediately after the ptg will be great to get development done
16:27:52 <smcginnis> Yeah :)
16:27:56 <ttx> yes
16:27:57 <hberaud> About the PTL don't forget to put topics in our etherpad that you want to bring there => https://etherpad.opendev.org/p/relmgmt-wallaby-ptg
16:28:00 <clarkb> re the planned gerrit upgrade I had intended on announcing that as a friday- sunday outage in novemeber on tuesday. Tuesday ended up being occupied with other things. I'm not yet sure if we're going to stick with that schedule. But gauging reaction to that from this group is probably a good water temp test
16:28:35 <clarkb> we have to do the notedb conversion which takes about 8 hours, and tahts running from tip of stable branch with unreleased speedup fixes to the process
16:29:21 <fungi> yes, we'll need to expect a weekend-long outage for the upgrade, and also a variety of regressions in functionality/integrations immediately afterward
16:30:00 <fungi> apparently we can recover from a security breach in half the outage you need for an upgrade ;)
16:30:06 <hberaud> thanks for details
16:30:54 <smcginnis> We'll see if you can get quoted in The Register again. :)
16:31:12 <fungi> he's working on raising his celebrity profile
16:31:38 <hberaud> :)
16:32:15 <hberaud> anything else?
16:32:35 <smcginnis> Nope
16:32:36 <elod> i have one thing, if there's nothing else
16:33:04 <elod> about the time slot of the release meeting
16:33:32 <elod> i want to participate on the meeting, but it is at the same time as nova meeting
16:33:32 <smcginnis> We do seem to have skewed more to the east now.
16:33:56 <elod> and i have a nova stable core hat so i need to be there as well
16:34:16 <hberaud> I can propose a vote for few slots
16:34:30 <ttx> sure
16:34:34 <hberaud> more early on Thursday
16:34:48 <elod> hberaud: thanks \o/
16:35:16 <hberaud> I'll share a doodle or something like that via email on the ML
16:35:30 <hberaud> elod: you're welcome
16:35:39 <elod> hberaud: thx :)
16:36:00 <elod> I'll try to help with mostly stable related tasks if my time allows :)
16:36:44 <hberaud> awesome
16:36:47 <hberaud> then I think we are done, thanks everyone for joining us!
16:36:59 <elod> thanks o/
16:37:01 <hberaud> #endmeeting