Thursday, 2020-11-26

*** freerunner has quit IRC00:55
*** freerunner has joined #openstack-release00:55
*** freerunner has quit IRC01:16
*** freerunner has joined #openstack-release01:16
*** sboyron has quit IRC01:17
*** lifeless has quit IRC03:41
*** lifeless has joined #openstack-release03:42
*** vishalmanchanda has joined #openstack-release04:22
*** ykarel|away has joined #openstack-release05:15
*** ykarel|away is now known as ykarel05:16
*** evrardjp has quit IRC05:33
*** evrardjp has joined #openstack-release05:33
*** ykarel has quit IRC06:54
*** e0ne has joined #openstack-release06:58
*** e0ne has quit IRC07:09
*** slaweq has joined #openstack-release07:11
*** ykarel has joined #openstack-release07:24
*** rpittau|afk is now known as rpittau07:26
*** e0ne has joined #openstack-release07:34
*** dtantsur|afk is now known as dtantsur07:37
*** sboyron has joined #openstack-release07:57
*** e0ne has quit IRC08:05
*** e0ne has joined #openstack-release08:10
openstackgerritSlawek Kaplonski proposed openstack/releases master: New neutron release for Stein  https://review.opendev.org/c/openstack/releases/+/76428908:17
slaweqhberaud: hi, ^^ that should be our last Stein release and we can go to EM08:18
slaweqit has this revert which we discussed few days ago08:18
*** jbadiapa has joined #openstack-release08:27
hberaudslaweq: awesome thanks08:32
hberaudslaweq: you don't want to put some specific release note to inform your users?08:36
slaweqhberaud: do You mean to put release not in neutron repo or in the releases somehow?08:37
hberaudslaweq: it could help you to highlight these significant changes08:37
*** tosky has joined #openstack-release08:37
hberaudslaweq: here => https://opendev.org/openstack/neutron/src/branch/stable/stein/releasenotes/notes08:37
slaweqhberaud: sure, I will do it right now08:38
hberaudslaweq: by using something like: reno new <release-note-title>08:38
slaweqhberaud: yes, I know how to use reno08:38
hberaudack np08:38
slaweqthx a lot08:38
hberaudmy pleasure, you're welcome08:39
hberaudthe reno isn't something mandatory but since you said this was a vicious bug I think it might be worth to talking about08:42
hberaudslaweq: FYI I'm waiting for this one before validating your release patch, also don't forget to update your SHA on your release patches.08:53
slaweqhberaud: sure08:54
openstackgerritMerged openstack/releases master: Release Bifrost 9.0.1 for Victoria  https://review.opendev.org/c/openstack/releases/+/76393609:05
*** ykarel has quit IRC09:12
openstackgerritMerged openstack/releases master: Release Ironic 16.0.2 for Victoria  https://review.opendev.org/c/openstack/releases/+/76394809:12
openstackgerritMerged openstack/releases master: Release Ironic Inspector 10.4.1 for Victoria  https://review.opendev.org/c/openstack/releases/+/76394909:12
*** ykarel has joined #openstack-release09:13
openstackgerritMerged openstack/releases master: Release IPA 6.4.2 for Victoria  https://review.opendev.org/c/openstack/releases/+/76397909:15
openstackgerritMerged openstack/releases master: Fix pygments_style  https://review.opendev.org/c/openstack/releases/+/76351509:15
*** e0ne has quit IRC09:15
openstackgerritMerged openstack/releases master: Release collect-logs role 1.2.0  https://review.opendev.org/c/openstack/releases/+/76399009:15
*** e0ne has joined #openstack-release09:41
*** slaweq has quit IRC09:45
*** slaweq has joined #openstack-release09:46
*** armstrong has joined #openstack-release10:48
*** ricolin has quit IRC11:34
*** e0ne has quit IRC12:08
*** e0ne has joined #openstack-release12:23
*** ianychoi_ has joined #openstack-release12:35
*** ianychoi has quit IRC12:36
*** armstrong has quit IRC12:57
*** slaweq has quit IRC13:17
*** slaweq has joined #openstack-release13:20
*** ykarel_ has joined #openstack-release13:23
*** ykarel has quit IRC13:25
*** mgoddard has joined #openstack-release13:44
*** ykarel_ is now known as ykarel13:44
*** sboyron has quit IRC13:48
*** e0ne has quit IRC13:52
*** sboyron has joined #openstack-release13:58
*** ykarel is now known as ykarel|away14:31
*** ykarel|away has quit IRC14:36
*** e0ne has joined #openstack-release14:52
*** frickler is now known as frickler_pto15:02
*** iurygregory has quit IRC15:02
*** armstrong has joined #openstack-release15:46
armstrongHello, I missed the meeting hour16:05
*** slaweq has quit IRC16:10
*** slaweq has joined #openstack-release16:13
*** e0ne has quit IRC16:29
elodarmstrong: it will be in half an hour, 17:00 UTC ( http://lists.openstack.org/pipermail/openstack-discuss/2020-November/018910.html )16:34
openstackgerritSlawek Kaplonski proposed openstack/releases master: New neutron release for Stein  https://review.opendev.org/c/openstack/releases/+/76428916:41
*** jbadiapa has quit IRC16:56
*** mgoddard has quit IRC16:57
*** dtantsur is now known as dtantsur|afk16:59
hberaud#startmeeting releaseteam17:00
openstackMeeting 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
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.17:00
ttxo/17:00
hberaudPing list: ttx armstrong elod17:00
*** openstack changes topic to " (Meeting topic: releaseteam)"17:00
openstackThe meeting name has been set to 'releaseteam'17:00
hberaud#link https://etherpad.opendev.org/p/wallaby-relmgt-tracking Agenda17:00
hberaudWe're way down on line 8117:00
armstrongo/17:00
elodo/17:01
*** mgoddard has joined #openstack-release17:02
hberaudWill just wait a couple minutes for folks.17:02
*** ricolin has joined #openstack-release17:02
hberaudLet's go!17:03
hberaud#topic Review task completion17:03
*** openstack changes topic to "Review task completion (Meeting topic: releaseteam)"17:03
hberaudReview cycle-trailing projects to check which haven’t released yet. Done17:03
hberaudhttp://lists.openstack.org/pipermail/openstack-discuss/2020-November/019042.html17:03
hberaudA couple of trailing project aren't yet released17:03
hberaudThat's all for this week17:04
hberaud#topic Assign R-19 tasks17:04
*** openstack changes topic to "Assign R-19 tasks (Meeting topic: releaseteam)"17:04
hberaudPropose autoreleases for cycle-with-intermediary libraries which did not release since the previous release.17:04
hberaudTakers?17:04
ttxI have limited availability on that week, would prefer not to drive any task17:05
hberaudSure np, I put myself17:06
ttxhappy to help review stuff17:06
armstrongI am available for any task17:06
hberaudTo catch if there are acl issues in newly created repositories, any volunteer?17:06
ttxI can do that17:07
hberaudarmstrong: maybe you want to manage this one ^17:07
hberaudttx: as you want17:07
armstrongnp, but guided if necessary17:07
hberaudarmstrong: maybe can be done by collaboration with ttx17:07
ttxhmm, if we can do that early in the week yes17:08
armstrongok works for me17:08
ttxarmstrong: maybe you try early next week and let me know if you have questions?17:08
hberaudok I let you manage your time together17:08
armstrongLike Monday?17:08
ttxsure17:08
armstrongok works17:09
hberaudawesome17:09
hberaudthanks to you!17:09
hberaud#topic Review countdown email contents17:09
*** openstack changes topic to "Review countdown email contents (Meeting topic: releaseteam)"17:09
hberaudhttps://etherpad.opendev.org/p/relmgmt-weekly-emails17:09
hberaud#link https://etherpad.opendev.org/p/relmgmt-weekly-emails17:09
hberaudLooks like I got all the dates updated.17:10
ttxLGTM17:10
hberaud+117:10
armstrong+117:10
hberaudawesome, thanks17:10
hberaud#topic stein-em status17:10
*** openstack changes topic to "stein-em status (Meeting topic: releaseteam)"17:10
hberaudSo we are near from the end17:11
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 release17:11
elod\o/17:11
elodthanks for the reviews17:12
hberaudI'm waiting for the CI, and if everything is OK I'll fast approve them17:12
ttxI did approve the neutron release17:12
ttxit passed ci ok17:12
hberaudawesome17:12
eloddo I need to update the neutron stein-em patch?17:12
hberaudah... they didn't updated the SHA => https://review.opendev.org/c/openstack/releases/+/76240417:12
ttxslaweq should be able to lift the -1 on https://review.opendev.org/c/openstack/releases/+/762404 very soon17:12
hberaudelod: yes17:12
elodwell, I'll update17:12
ttx++17:13
elodgood-good, np17:13
hberaudelod: thanks and we'll approve17:13
ttxand then we should be able to close by merging https://review.opendev.org/c/openstack/releases/+/76247517:13
hberaudYES \o/ :D17:13
elod:]17:13
hberaudThen I think we can move on17:14
ttxI just front-loaded my +2 so you can +a17:14
hberaud#topic Redflag IRC notifications17:14
*** openstack changes topic to "Redflag IRC notifications (Meeting topic: releaseteam)"17:14
ttxI'm off tomorrow17:14
hberaudttx: ack, thanks17:14
hberaudah oups soory I missed a topic17:14
hberaud#topic Status of our previous issue17:15
*** openstack changes topic to "Status of our previous issue (Meeting topic: releaseteam)"17:15
hberaudSo everything seems under controle for now17:15
hberaudI didn't noticed new issues17:15
ttxnope all good17:15
hberaudSo as you already know we already restarted approving patches since Wednesday17:15
hberaudbut I just wanted to be clear17:16
hberaudSo this is lead us to...17:16
hberaud#topic Redflag IRC notifications17:16
*** openstack changes topic to "Redflag IRC notifications (Meeting topic: releaseteam)"17:16
hberaudHow we should handle these kind of failure and how to manage to stop/start to approve patches17:17
hberaudttx: suggested some redflags17:17
hberaudsorry, reword: ttx suggested some redflags17:17
*** tosky has quit IRC17:17
ttxtwo remarks re: proposed plan17:17
hberaudTo allow us  to know when it's safe to approve releases or not17:18
ttxI would not reuse '#topic' since that won't work as expected17:18
hberaudyes17:18
openstackgerritMerged openstack/releases master: New neutron release for Stein  https://review.opendev.org/c/openstack/releases/+/76428917:18
ttxAnd 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 next17:18
hberaudthis is why I submitted an email with "redflag" in the subject17:18
hberaudI agree17:19
hberaudmake sense17:19
ttxWe'd always go from RED to GREEN through ORANGE17:19
hberaudYes make sense17:19
ttxI think a highlight is a good idea, the trick is that it does not persist17:20
hberaudAlso for those who use weechat we can use the "highlight_regex" config as noticed line 102 https://etherpad.opendev.org/p/wallaby-relmgt-tracking17:20
ttxso maybe we should just /topic Releasing status: GREEN17:20
ttxand catch that17:20
hberaudHmmm, I'm using it in my config and it work everytime17:20
hberaudit can be persistant17:21
hberaudyou can put it in your config file17:21
ttxno, I mean17:21
ttxIf you are not in the channel and you just join, no way to know17:22
hberaudAh yes17:22
hberaudgot it17:22
ttxIf we use /topic it will persist in the topic17:22
hberaudindeed17:22
ttxand you can still have a highlight on it, I think17:22
ttxAlso avoids reusing a command that is reserved to meetbot17:22
hberaudwe can use another word.. like redflag17:22
hberaudor something like that17:22
hberaud#redflag17:23
ttxThe only drawback is that in infra alert cases the topic is rewritten17:23
ttxbut I guess that's just another case of RED17:23
ttxsince when that happens we probably don;t want to release17:23
hberaudyes17:23
ttxSo one issue is that during meetings we overwrite the topic17:24
hberaudelse... another simple approach is to ping all core member directly about this17:24
ttxanother issue is that you need chanop to update topic17:24
hberaudand also send a redflag email17:24
hberaudI see17:24
ttxhmm... yeah that might work better17:25
hberaudok let's start with that17:25
ttxso... pinglist + email for persistence17:25
hberaudexact!17:25
ttxok let's start this way17:25
hberaudemail: Red, Orange, Green17:26
hberaudBy modifying the subject17:26
ttx[release] Status: RED - Bla bla17:26
hberaudsold!17:26
ttxthen we can reply and edit subject to go back to ORANGE and GREEN17:26
hberaudexact17:27
ttxto avoid creating 3 threads17:27
hberaudexact17:27
ttxsold17:27
hberaudawesome :)17:27
hberaudthen I think we can move on open discussion17:27
hberaud#topic Open Discussion17:27
*** openstack changes topic to "Open Discussion (Meeting topic: releaseteam)"17:27
hberaudAnything else?17:27
elodnothing from me this time17:28
armstrongttx what time will best for you on Monday? I want to set my calendar :)17:29
hberaudA last thing from my side, I'll try to formalize the previous topic (redflag) in our doc to keep a track17:30
ttxarmstrong: 13utc or 15utc17:30
hberaudmaybe in the reviewer guide17:30
ttx++17:30
armstrong15 UTC17:30
ttxor some other doc page17:30
ttxarmstrong: ok I'll be around, just ping me if you need me17:31
armstrongttx ok17:31
hberaudok let's discuss about it directly on the future patch17:31
hberaudOK, thanks everyone. Almost there!17:31
hberaud#endmeeting17:31
*** openstack changes topic to "OpenStack Release Managers office - Come here to discuss how to release OpenStack components - Logged at http://eavesdrop.openstack.org/irclogs/%23openstack-release/"17:31
openstackMeeting ended Thu Nov 26 17:31:59 2020 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:32
openstackMinutes:        http://eavesdrop.openstack.org/meetings/releaseteam/2020/releaseteam.2020-11-26-17.00.html17:32
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/releaseteam/2020/releaseteam.2020-11-26-17.00.txt17:32
openstackLog:            http://eavesdrop.openstack.org/meetings/releaseteam/2020/releaseteam.2020-11-26-17.00.log.html17:32
ttxThanks hberaud !17:32
openstackgerritElod Illes proposed openstack/releases master: [neutron] Transition Stein to EM  https://review.opendev.org/c/openstack/releases/+/76240417:34
*** armax has quit IRC17:59
*** armax has joined #openstack-release18:02
*** mgoddard has quit IRC18:08
*** armax has quit IRC18:11
openstackgerritMerged openstack/releases master: [neutron] Transition Stein to EM  https://review.opendev.org/c/openstack/releases/+/76240418:42
hberaudOk last sprint https://review.opendev.org/c/openstack/releases/+/76247518:48
openstackgerritMerged openstack/releases master: Set Stein status to Extended Maintenance  https://review.opendev.org/c/openstack/releases/+/76247518:57
hberaud\o/ stein is now officially18:59
hberaud#success Stein's transition to extended maintenance completed19:00
openstackstatushberaud: Added success to Success page (https://wiki.openstack.org/wiki/Successes)19:00
elod\o/19:07
elodthx hberaud :]19:07
*** e0ne has joined #openstack-release19:32
*** e0ne has quit IRC19:32
*** e0ne has joined #openstack-release19:48
*** e0ne has quit IRC19:52
*** e0ne has joined #openstack-release20:02
*** e0ne has quit IRC20:03
*** e0ne has joined #openstack-release20:03
hberaudttx: http://lists.openstack.org/pipermail/release-job-failures/2020-November/001494.html and http://lists.openstack.org/pipermail/release-job-failures/2020-November/001495.html are reno config.py error too (like the previous one on paunch), nothing mean, I don't think we need to publicly warn about this20:24
hberaudsmcginnis: ^20:24
hberaudand they are related to stein-em with neutron-*20:25
hberaudwhich is now EM, so I don't expect to see this job runned once again with stein and neutron-*20:26
hberaudcan be informally discussed directly with the team20:27
hberaudI'll ping them tomorrow to prevent similar things to happen with more recent series20:28
hberaudWell, See you tomorrow20:28
*** rpittau is now known as rpittau|afk20:45
*** e0ne has quit IRC21:04
*** tosky has joined #openstack-release21:09
*** slaweq has quit IRC21:45
*** slaweq has joined #openstack-release21:47
*** vishalmanchanda has quit IRC22:21
*** e0ne has joined #openstack-release22:26
*** slaweq has quit IRC22:26
*** e0ne has quit IRC22:42
*** sboyron has quit IRC22:53
*** e0ne has joined #openstack-release22:56
*** e0ne has quit IRC22:59

Generated by irclog2html.py 2.17.2 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!