17:00:09 <hberaud> #startmeeting releaseteam
17:00:10 <openstack> Meeting started Thu Nov 26 17:00:09 2020 UTC and is due to finish in 60 minutes.  The chair is hberaud. Information about MeetBot at http://wiki.debian.org/MeetBot.
17:00:11 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
17:00:12 <ttx> o/
17:00:12 <hberaud> Ping list: ttx armstrong elod
17:00:14 <openstack> The meeting name has been set to 'releaseteam'
17:00:15 <hberaud> #link https://etherpad.opendev.org/p/wallaby-relmgt-tracking Agenda
17:00:37 <hberaud> We're way down on line 81
17:00:52 <armstrong> o/
17:01:01 <elod> o/
17:02:10 <hberaud> Will just wait a couple minutes for folks.
17:03:01 <hberaud> Let's go!
17:03:04 <hberaud> #topic Review task completion
17:03:11 <hberaud> Review cycle-trailing projects to check which haven’t released yet. Done
17:03:15 <hberaud> http://lists.openstack.org/pipermail/openstack-discuss/2020-November/019042.html
17:03:58 <hberaud> A couple of trailing project aren't yet released
17:04:14 <hberaud> That's all for this week
17:04:27 <hberaud> #topic Assign R-19 tasks
17:04:45 <hberaud> Propose autoreleases for cycle-with-intermediary libraries which did not release since the previous release.
17:04:54 <hberaud> Takers?
17:05:56 <ttx> I have limited availability on that week, would prefer not to drive any task
17:06:06 <hberaud> Sure np, I put myself
17:06:20 <ttx> happy to help review stuff
17:06:29 <armstrong> I am available for any task
17:06:33 <hberaud> To catch if there are acl issues in newly created repositories, any volunteer?
17:07:03 <ttx> I can do that
17:07:05 <hberaud> armstrong: maybe you want to manage this one ^
17:07:17 <hberaud> ttx: as you want
17:07:26 <armstrong> np, but guided if necessary
17:07:54 <hberaud> armstrong: maybe can be done by collaboration with ttx
17:08:08 <ttx> hmm, if we can do that early in the week yes
17:08:22 <armstrong> ok works for me
17:08:26 <ttx> armstrong: maybe you try early next week and let me know if you have questions?
17:08:29 <hberaud> ok I let you manage your time together
17:08:53 <armstrong> Like Monday?
17:08:58 <ttx> sure
17:09:03 <armstrong> ok works
17:09:08 <hberaud> awesome
17:09:22 <hberaud> thanks to you!
17:09:31 <hberaud> #topic Review countdown email contents
17:09:38 <hberaud> https://etherpad.opendev.org/p/relmgmt-weekly-emails
17:09:43 <hberaud> #link https://etherpad.opendev.org/p/relmgmt-weekly-emails
17:10:04 <hberaud> Looks like I got all the dates updated.
17:10:30 <ttx> LGTM
17:10:38 <hberaud> +1
17:10:42 <armstrong> +1
17:10:50 <hberaud> awesome, thanks
17:10:55 <hberaud> #topic stein-em status
17:11:13 <hberaud> So we are near from the end
17:11:37 <hberaud> Only neutron remains out of EM, they encountered a big bug in stein and train and they want to revert the changes who introduced this one and release a last stable stein version free from the bug. They just proposed a latest release
17:11:51 <elod> \o/
17:12:04 <elod> thanks for the reviews
17:12:04 <hberaud> I'm waiting for the CI, and if everything is OK I'll fast approve them
17:12:15 <ttx> I did approve the neutron release
17:12:19 <ttx> it passed ci ok
17:12:23 <hberaud> awesome
17:12:37 <elod> do I need to update the neutron stein-em patch?
17:12:52 <hberaud> ah... they didn't updated the SHA => https://review.opendev.org/c/openstack/releases/+/762404
17:12:53 <ttx> slaweq should be able to lift the -1 on https://review.opendev.org/c/openstack/releases/+/762404 very soon
17:12:56 <hberaud> elod: yes
17:12:58 <elod> well, I'll update
17:13:09 <ttx> ++
17:13:12 <elod> good-good, np
17:13:19 <hberaud> elod: thanks and we'll approve
17:13:27 <ttx> and then we should be able to close by merging https://review.opendev.org/c/openstack/releases/+/762475
17:13:41 <hberaud> YES \o/ :D
17:13:49 <elod> :]
17:14:09 <hberaud> Then I think we can move on
17:14:11 <ttx> I just front-loaded my +2 so you can +a
17:14:14 <hberaud> #topic Redflag IRC notifications
17:14:16 <ttx> I'm off tomorrow
17:14:29 <hberaud> ttx: ack, thanks
17:14:53 <hberaud> ah oups soory I missed a topic
17:15:00 <hberaud> #topic Status of our previous issue
17:15:17 <hberaud> So everything seems under controle for now
17:15:27 <hberaud> I didn't noticed new issues
17:15:33 <ttx> nope all good
17:15:54 <hberaud> So as you already know we already restarted approving patches since Wednesday
17:16:06 <hberaud> but I just wanted to be clear
17:16:21 <hberaud> So this is lead us to...
17:16:28 <hberaud> #topic Redflag IRC notifications
17:17:18 <hberaud> How we should handle these kind of failure and how to manage to stop/start to approve patches
17:17:28 <hberaud> ttx: suggested some redflags
17:17:46 <hberaud> sorry, reword: ttx suggested some redflags
17:17:52 <ttx> two remarks re: proposed plan
17:18:21 <hberaud> To allow us  to know when it's safe to approve releases or not
17:18:22 <ttx> I would not reuse '#topic' since that won't work as expected
17:18:30 <hberaud> yes
17:18:42 <openstackgerrit> Merged openstack/releases master: New neutron release for Stein  https://review.opendev.org/c/openstack/releases/+/764289
17:18:51 <ttx> And i would add a third status (ORANGE) when it's ok to approve one by one and watch for completion before we move to teh next
17:18:57 <hberaud> this is why I submitted an email with "redflag" in the subject
17:19:09 <hberaud> I agree
17:19:15 <hberaud> make sense
17:19:17 <ttx> We'd always go from RED to GREEN through ORANGE
17:19:34 <hberaud> Yes make sense
17:20:04 <ttx> I think a highlight is a good idea, the trick is that it does not persist
17:20:18 <hberaud> Also for those who use weechat we can use the "highlight_regex" config as noticed line 102 https://etherpad.opendev.org/p/wallaby-relmgt-tracking
17:20:34 <ttx> so maybe we should just /topic Releasing status: GREEN
17:20:45 <ttx> and catch that
17:20:58 <hberaud> Hmmm, I'm using it in my config and it work everytime
17:21:18 <hberaud> it can be persistant
17:21:40 <hberaud> you can put it in your config file
17:21:46 <ttx> no, I mean
17:22:02 <ttx> If you are not in the channel and you just join, no way to know
17:22:08 <hberaud> Ah yes
17:22:11 <hberaud> got it
17:22:15 <ttx> If we use /topic it will persist in the topic
17:22:17 <hberaud> indeed
17:22:24 <ttx> and you can still have a highlight on it, I think
17:22:32 <ttx> Also avoids reusing a command that is reserved to meetbot
17:22:48 <hberaud> we can use another word.. like redflag
17:22:58 <hberaud> or something like that
17:23:05 <hberaud> #redflag
17:23:11 <ttx> The only drawback is that in infra alert cases the topic is rewritten
17:23:25 <ttx> but I guess that's just another case of RED
17:23:39 <ttx> since when that happens we probably don;t want to release
17:23:46 <hberaud> yes
17:24:12 <ttx> So one issue is that during meetings we overwrite the topic
17:24:21 <hberaud> else... another simple approach is to ping all core member directly about this
17:24:43 <ttx> another issue is that you need chanop to update topic
17:24:43 <hberaud> and also send a redflag email
17:24:59 <hberaud> I see
17:25:03 <ttx> hmm... yeah that might work better
17:25:20 <hberaud> ok let's start with that
17:25:39 <ttx> so... pinglist + email for persistence
17:25:45 <hberaud> exact!
17:25:56 <ttx> ok let's start this way
17:26:04 <hberaud> email: Red, Orange, Green
17:26:18 <hberaud> By modifying the subject
17:26:27 <ttx> [release] Status: RED - Bla bla
17:26:36 <hberaud> sold!
17:26:53 <ttx> then we can reply and edit subject to go back to ORANGE and GREEN
17:27:03 <hberaud> exact
17:27:05 <ttx> to avoid creating 3 threads
17:27:10 <hberaud> exact
17:27:11 <ttx> sold
17:27:20 <hberaud> awesome :)
17:27:36 <hberaud> then I think we can move on open discussion
17:27:46 <hberaud> #topic Open Discussion
17:27:58 <hberaud> Anything else?
17:28:27 <elod> nothing from me this time
17:29:20 <armstrong> ttx what time will best for you on Monday? I want to set my calendar :)
17:30:14 <hberaud> A last thing from my side, I'll try to formalize the previous topic (redflag) in our doc to keep a track
17:30:20 <ttx> armstrong: 13utc or 15utc
17:30:24 <hberaud> maybe in the reviewer guide
17:30:38 <ttx> ++
17:30:45 <armstrong> 15 UTC
17:30:47 <ttx> or some other doc page
17:31:03 <ttx> armstrong: ok I'll be around, just ping me if you need me
17:31:16 <armstrong> ttx ok
17:31:21 <hberaud> ok let's discuss about it directly on the future patch
17:31:47 <hberaud> OK, thanks everyone. Almost there!
17:31:59 <hberaud> #endmeeting