Thursday, 2020-10-22

*** tinwood has quit IRC00:03
*** tinwood has joined #openstack-release00:04
*** brinzhang has quit IRC02:31
openstackgerritchenming proposed openstack/releases master: update url  https://review.opendev.org/75917503:08
*** evrardjp has quit IRC04:33
*** evrardjp has joined #openstack-release04:33
*** vishalmanchanda has joined #openstack-release05:39
*** jbadiapa has joined #openstack-release05:46
*** sboyron has joined #openstack-release06:06
*** jtomasek has joined #openstack-release06:20
*** slaweq has joined #openstack-release06:21
*** noonedeadpunk has quit IRC06:31
*** noonedeadpunk has joined #openstack-release06:32
*** noonedeadpunk has quit IRC06:34
*** noonedeadpunk has joined #openstack-release06:39
*** slaweq has quit IRC06:44
*** slaweq has joined #openstack-release06:46
*** rpittau|afk is now known as rpittau06:54
*** e0ne has joined #openstack-release07:12
*** tosky has joined #openstack-release07:44
*** dtantsur|afk is now known as dtantsur08:56
*** iurygregory has quit IRC08:57
*** iurygregory has joined #openstack-release09:28
damanihi10:05
hberauddamani: hello10:06
*** armstrong has joined #openstack-release12:34
hberaudsmcginnis: FYI I voluntarily removed you from the list of people to whom I sent the direct email, so don't be surprised if you don't receive this email, I don't want to spam you with something useless for you12:36
openstackgerritHervé Beraud proposed openstack/releases master: [WIP] Adding a tool to track project who need to drop eol branches  https://review.opendev.org/75899014:27
openstackgerritHervé Beraud proposed openstack/releases master: Managing the review inbox by series  https://review.opendev.org/75837814:37
openstackgerritHervé Beraud proposed openstack/releases master: Managing the review inbox by series  https://review.opendev.org/75837814:50
*** e0ne has quit IRC15:14
smcginnishberaud: Sure. Which emails?15:24
hberaudsmcginnis: this one => https://review.opendev.org/#/c/758991/15:25
smcginnishberaud: Ah. Well, I'm not a PTL anywhere anymore, so that's good. ;)15:26
hberaudsmcginnis: are you not the cinder's release liaison?15:27
smcginnisOh, right! I forgot about that.15:28
hberaudas this email is destined to PTLs + liaisons15:28
*** sboyron has quit IRC15:28
hberaudand I get your name in my extract :)15:28
openstackgerritHervé Beraud proposed openstack/releases master: Adding PTL Cycle Information  https://review.opendev.org/75899115:31
openstackgerritDaniel Bengtsson proposed openstack/releases master: New bugfix release for pbr.  https://review.opendev.org/75928615:54
openstackgerritHervé Beraud proposed openstack/releases master: Managing the review inbox by series  https://review.opendev.org/75837815:55
openstackgerritDaniel Bengtsson proposed openstack/releases master: New bugfix release for openstackdocsthemes.  https://review.opendev.org/75928615:55
openstackgerritHervé Beraud proposed openstack/releases master: Managing the review inbox by series  https://review.opendev.org/75837815:56
*** rpittau is now known as rpittau|afk15:57
ttxo/16:00
hberaud#startmeeting releaseteam16:00
openstackMeeting 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
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:00
*** openstack changes topic to " (Meeting topic: releaseteam)"16:00
openstackThe meeting name has been set to 'releaseteam'16:00
damanihi16:00
hberaud#link https://etherpad.opendev.org/p/wallaby-relmgt-tracking Agenda16:00
fungiohai16:00
elodo/16:00
hberaud#topic Setup wallaby16:02
*** openstack changes topic to "Setup wallaby (Meeting topic: releaseteam)"16:02
hberaudbefore going any further we will start with setup our future meetings16:02
hberaudIf 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:03
hberaudalso if you plan to schedule some review days do not hesitate to put your name on our "Review days (lines 16-20)"16:05
hberaudelse as you surely already know Wallaby is now on the rails16:05
ttxI'm in16:06
hberaudand all the related tasks above (etherpad) have been processed16:06
damanihberaud, yes sorry i will put my name for the notification16:06
hberauddamani: np :)16:06
damanii will put also my name for the code review16:06
damani:)16:06
hberaudnice16:06
hberaudwell next topic16:07
hberaud#topic Gerrit-breach16:07
*** openstack changes topic to "Gerrit-breach (Meeting topic: releaseteam)"16:07
hberaudso just few words about this, it seems that we are ok on our side16:07
damaniyes16:07
hberaudAFAIK nobody complained about something16:08
openstackgerritDaniel Bengtsson proposed openstack/releases master: New bugfix release for oslo.messaging for ussuri.  https://review.opendev.org/75928916:08
armstrongo/16:08
ttxyep16:08
smcginnisYeah, I didn't see anything odd.16:08
hberaudarmstrong, smcginnis: FYI don't hesitate to put our name in our Ping list16:08
hberaudwell next topic16:09
hberaud#topic Clarifying why heat's victoria release note list all versions16:09
*** openstack changes topic to "Clarifying why heat's victoria release note list all versions (Meeting topic: releaseteam)"16:09
smcginnisThat appears to be the open bug with reno.16:09
armstrongsmcginnis ok I will do that now, thanks16:09
hberaudI missed that one16:09
hberaudgood to know16:10
hberaudricolin: FYI ^^^16:10
hberaudricolin: and https://storyboard.openstack.org/#!/story/200813916:10
hberaudnext16:11
hberaud#topic Clarifying how to manage Extended maintenance and EOL branches16:11
*** openstack changes topic to "Clarifying how to manage Extended maintenance and EOL branches (Meeting topic: releaseteam)"16:11
elodfirst of all, I offer my help for any tasks regarding Extended Maintenance process :)16:11
hberaudlol16:12
hberaudI started to write a test https://review.opendev.org/#/c/758990/ to check delta between our status and existing branches on the projects sides16:12
smcginniselod: Thanks for getting that email sent out.16:12
hberaudI'll add some process to our doc to clarify thing on our side16:13
elodsmcginnis: np16:13
hberaudbut I think the stable team should ensure that patches are -2 on eol branches as elod suggested16:14
elodhberaud: yes, I can help with that :)16:14
smcginnisfungi: Anything we can trigger after an -eol tag that would tell gerrit to block those right off the bat?16:14
elodnevertheless, some automation would be good to not to miss any such case16:14
hberaudAlso 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
smcginnisI 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
hberaud+116:15
hberaudI think our process should say to notify ASAP the infra team16:16
hberaudI don't think we need the right to drop the branches16:16
hberaudthis could be done by simply asking the infra, thoughts?16:16
hberauds/the/to/16:17
elodactually Infra team said that they need to be sure that the EOLing is OK from release team perspective, If i understand correctly16:17
hberaudyep16:17
hberaudso if we ask them I think we could consider that this is ok for us16:17
elodyes, that's ok16:18
hberaudawesome16:18
smcginnisI'd say our approval of the tagging request is the release team approval of it.16:18
hberaud+116:18
elodthat's also true :)16:18
hberaudso either the infra schedule periodical checks on our side16:19
hberaudor we noticed them16:19
hberauds/noticed/notify/16:19
hberaudsorry16:19
hberaudas you want16:20
elodboth sound ok to me,16:20
hberaudfungi: any preferences?16:20
elodof course if we can figure out any way we can do it more straightforward, then it would be even better16:20
fungiwe could update acls for projects to block proposed changes for those branch patterns, i think16:21
fungibut might make more sense to just use that as an indication that the branch should be deleted at the earliest opportunity16:21
hberaudit will be awesome16:21
smcginnis++16:21
hberaudto avoid to spend time to track new patches and chase them for -216:22
funginewer gerrit we're upgrading to will allow us to grant branch deletion via api as a specific permission, so we could do some automation there16:22
hberaudawesome16:22
fungiso in theory it could be automated from the releases repo at that point16:23
hberaudmaybe it could be triggered from our side16:23
fungiyeah, similar to the automated branch creation16:23
hberaudfair enough16:23
hberaudthanks16:23
elodthanks fungi !16:23
hberaud#topic Next meetings/weeks16:23
*** openstack changes topic to "Next meetings/weeks (Meeting topic: releaseteam)"16:23
ttxLooks like it's a noop now16:24
hberaudno meeting will happen during the next 3 weeks16:24
hberaudyep16:24
smcginnisfungi: Do we have a planned timeframe for that gerrit upgrade yet?16:24
ttxthere were a bunch of duplicated tasks in the etherpad I looked up this morning16:24
fungismcginnis: mid-november it's looking like16:24
smcginnisGreat!16:24
hberaudttx: I dropped them16:24
funginot sure if this weeks events will alter our timeline at all16:25
ttxwell, we'll have a PTG meeting next week, but otherwise yes16:25
smcginnisI was wondering about that.16:25
ttxIt's the low tide season for release management, so enjoy it!16:25
hberaud#topic Open Discussion16:25
*** openstack changes topic to "Open Discussion (Meeting topic: releaseteam)"16:25
ttxalso if we have development to do after PTG discussions, it's a great time to do it now16:25
hberaudagreed16:26
hberaudanything else?16:26
fungido development now after ptg discussions? i'm not quite sure how to parse that suggestion16:26
* fungi goes looking for his time machine16:26
smcginnisIt's much more efficient to do the development before you discuss it. :D16:26
fungioh, i think i get it. saying the time immediately after the ptg will be great to get development done16:27
smcginnisYeah :)16:27
ttxyes16:27
hberaudAbout the PTL don't forget to put topics in our etherpad that you want to bring there => https://etherpad.opendev.org/p/relmgmt-wallaby-ptg16:27
clarkbre 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 test16:28
clarkbwe 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 process16:28
fungiyes, we'll need to expect a weekend-long outage for the upgrade, and also a variety of regressions in functionality/integrations immediately afterward16:29
fungiapparently we can recover from a security breach in half the outage you need for an upgrade ;)16:30
hberaudthanks for details16:30
smcginnisWe'll see if you can get quoted in The Register again. :)16:30
*** dtantsur is now known as dtantsur|afk16:31
fungihe's working on raising his celebrity profile16:31
hberaud:)16:31
hberaudanything else?16:32
smcginnisNope16:32
elodi have one thing, if there's nothing else16:32
elodabout the time slot of the release meeting16:33
elodi want to participate on the meeting, but it is at the same time as nova meeting16:33
smcginnisWe do seem to have skewed more to the east now.16:33
elodand i have a nova stable core hat so i need to be there as well16:33
hberaudI can propose a vote for few slots16:34
ttxsure16:34
hberaudmore early on Thursday16:34
elodhberaud: thanks \o/16:34
hberaudI'll share a doodle or something like that via email on the ML16:35
hberaudelod: you're welcome16:35
elodhberaud: thx :)16:35
elodI'll try to help with mostly stable related tasks if my time allows :)16:36
hberaudawesome16:36
hberaudthen I think we are done, thanks everyone for joining us!16:36
elodthanks o/16:36
hberaud#endmeeting16:37
*** 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/"16:37
openstackMeeting ended Thu Oct 22 16:37:01 2020 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:37
openstackMinutes:        http://eavesdrop.openstack.org/meetings/releaseteam/2020/releaseteam.2020-10-22-16.00.html16:37
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/releaseteam/2020/releaseteam.2020-10-22-16.00.txt16:37
openstackLog:            http://eavesdrop.openstack.org/meetings/releaseteam/2020/releaseteam.2020-10-22-16.00.log.html16:37
smcginnisThanks hberaud!16:38
ttxthanks hberaud !16:40
*** valleedelisle has joined #openstack-release16:40
openstackgerritDaniel Bengtsson proposed openstack/releases master: New feature release for oslo.messaging on wallaby.  https://review.opendev.org/75929716:43
*** jtomasek has quit IRC17:07
*** valleedelisle has quit IRC17:13
*** valleedelisle has joined #openstack-release17:24
*** vishalmanchanda has quit IRC17:39
openstackgerritSean McGinnis proposed openstack/releases master: Automate review inbox dashboard link  https://review.opendev.org/75930917:46
openstackgerritMerged openstack/releases master: New bugfix release for openstackdocsthemes.  https://review.opendev.org/75928617:52
*** ricolin has quit IRC17:54
openstackgerritMerged openstack/releases master: New bugfix release for oslo.messaging for ussuri.  https://review.opendev.org/75928918:02
openstackgerritMerged openstack/releases master: New feature release for oslo.messaging on wallaby.  https://review.opendev.org/75929718:02
*** e0ne has joined #openstack-release18:59
*** e0ne has quit IRC19:53
*** slaweq has quit IRC20:26
openstackgerritSean McGinnis proposed openstack/releases master: Automate review inbox dashboard link  https://review.opendev.org/75930920:49
openstackgerritSean McGinnis proposed openstack/releases master: Automate review inbox dashboard link  https://review.opendev.org/75930920:52
*** slaweq has joined #openstack-release21:08
*** slaweq has quit IRC21:27
*** armstrong has quit IRC22:24
*** tosky has quit IRC22:54

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