Thursday, 2019-03-21

« Wednesday, 2019-03-20 Index Friday, 2019-03-22 »
*** lbragstad has quit IRC00:14
*** mriedem has quit IRC01:26
*** ricolin has joined #openstack-release01:29
*** lbragstad has joined #openstack-release01:35
openstackgerritRico Lin proposed openstack/releases master: Release stable branches for heat repos  https://review.openstack.org/64448602:08
*** ekcs has quit IRC02:19
openstackgerritRico Lin proposed openstack/releases master: Release stable branches for heat repos  https://review.openstack.org/64448602:30
openstackgerritRico Lin proposed openstack/releases master: Update document to provide more information for deliverable schema  https://review.openstack.org/64504502:37
openstackgerritJiao Pengju proposed openstack/releases master: Add karbor cycle highlights for Stein  https://review.openstack.org/64504602:49
*** binh_ has quit IRC02:51
*** binh_ has joined #openstack-release02:51
tonybsmcginnis: FWIW: I found several UPPER_CONSTRAINTS changes that are wrong.  So far they're all older than the new redirections work and dhellmann's fix.02:58
tonybsmcginnis: I've written a tool to find all of them (and any that have merged already that shouldn't) and I'll go through and fix them by hand.02:59
tonybIt's intersting in that I discover which repos have stable-maint-core and/or release managers as core 'correctly'03:02
tonybIt's only 8 changes to not too bad03:03
tonybthe last 3 merged so those branches are 'broken'03:04
tonybthey're slightly harder to fix03:04
*** whoami-rajat has joined #openstack-release04:11
*** diablo_rojo has quit IRC04:12
openstackgerritColleen Murphy proposed openstack/releases master: keystone release for stein rc1  https://review.openstack.org/64431705:06
*** ricolin has quit IRC05:15
*** ricolin has joined #openstack-release05:32
*** lbragstad has quit IRC06:06
*** e0ne has joined #openstack-release06:06
*** e0ne has quit IRC06:07
openstackgerritRico Lin proposed openstack/releases master: Release stable branches for heat repos  https://review.openstack.org/64448606:08
*** pcaruana has joined #openstack-release06:11
*** ifat_afek has joined #openstack-release06:56
*** e0ne has joined #openstack-release07:45
*** tesseract has joined #openstack-release08:02
*** ifat_afek has quit IRC08:04
*** openstackgerrit has quit IRC08:17
*** dtantsur|afk is now known as dtantsur08:24
*** tosky has joined #openstack-release08:27
*** jpich has joined #openstack-release08:31
*** jtomasek has quit IRC08:32
*** ifat_afek has joined #openstack-release08:39
*** e0ne has quit IRC08:48
*** e0ne has joined #openstack-release08:51
*** whoami-rajat has quit IRC09:10
*** whoami-rajat has joined #openstack-release09:18
*** pcaruana has quit IRC09:45
*** pcaruana has joined #openstack-release09:46
*** zbr has quit IRC10:08
*** huats has joined #openstack-release10:08
*** zbr has joined #openstack-release10:09
*** e0ne has quit IRC10:14
*** zbr has quit IRC10:16
*** electrofelix has joined #openstack-release10:16
*** e0ne has joined #openstack-release10:17
*** cdent has joined #openstack-release10:21
*** zbr has joined #openstack-release10:21
*** zbr has quit IRC10:22
*** openstackgerrit has joined #openstack-release10:51
openstackgerritMark Goddard proposed openstack/releases master: Add cycle highlights for kolla and kolla ansible  https://review.openstack.org/64450610:51
*** jaosorior has quit IRC10:53
*** e0ne has quit IRC10:58
*** e0ne has joined #openstack-release10:59
*** whoami-rajat has quit IRC11:30
openstackgerritDmitry Tantsur proposed openstack/releases master: Release sushy-tools 0.5.0  https://review.openstack.org/64513811:31
*** whoami-rajat has joined #openstack-release11:34
*** zbr has joined #openstack-release11:38
openstackgerritTom Barron proposed openstack/releases master: manila release for stein rc1  https://review.openstack.org/64431911:42
openstackgerritTom Barron proposed openstack/releases master: Manila stable/rocky 7.2.0 release  https://review.openstack.org/64514711:47
*** dave-mccowan has joined #openstack-release11:48
*** jaosorior has joined #openstack-release11:51
openstackgerritTom Barron proposed openstack/releases master: Manila stable/queens 6.2.0 release  https://review.openstack.org/64514911:52
*** dave-mccowan has quit IRC11:53
*** ifat_afek has quit IRC12:00
*** cdent has quit IRC12:04
openstackgerritTom Barron proposed openstack/releases master: Manila stable/rocky 7.2.0 release  https://review.openstack.org/64514712:07
openstackgerritDmitry Tantsur proposed openstack/releases master: Release virtualbmc 1.5.0  https://review.openstack.org/64515612:11
*** jtomasek has joined #openstack-release12:12
*** ifat_afek has joined #openstack-release12:17
*** ifat_afek has quit IRC12:17
dhellmanntonyb : are they broken in the gate? or just locally?12:35
*** mriedem has joined #openstack-release12:38
*** e0ne has quit IRC12:51
*** dtantsur is now known as dtantsur|brb12:52
*** lbragstad has joined #openstack-release12:54
*** irclogbot_2 has quit IRC13:07
*** irclogbot_1 has joined #openstack-release13:09
smcginnistonyb: Thanks for digging in to that. Let me know if I can help.13:13
smcginnisI did wonder if we should "fix" those official projects to make sure stable-maint-core is part of their gerrit groups.13:13
dhellmannyes, I think we probably should13:19
*** altlogbot_1 has quit IRC13:23
*** e0ne has joined #openstack-release13:23
*** altlogbot_0 has joined #openstack-release13:24
tbarrontonyb when you have a chance we need to remove zhongjun from manila-stable-maint - she's no longer contributing to OpenStack13:29
smcginnistbarron: I've removed her.13:31
tbarronsmcginnis: ty!13:31
smcginnisWhat about this Swartzlander guy. I think I remember him. :)13:31
tbarronsmcginnis: he's still occasionally useful :)13:32
tbarronsmcginnis: I rely on him for a smart contrary opinion ...13:32
smcginnisHah13:33
*** ifat_afek has joined #openstack-release13:33
tbarronsmcginnis: seriously, he's quite careful about backports, backwards-compat, etc. so no problem having him on stable-maint13:34
smcginnistbarron: Yeah, I was just kidding. I know he's off doing other things, but I don't think we need to drop him because OpenStack isn't his main focus anymore.13:34
tbarronsmcginnis: agree.  And I hope to get him reviewing the big manila CSI PR: https://github.com/kubernetes/cloud-provider-openstack/pull/53613:37
*** e0ne has quit IRC13:37
tbarronsmcginnis: back more on topic, I updated https://review.openstack.org/644319 but how much time do we have if I workflow -1 this while we try to land one more bugfix?13:38
*** altlogbot_0 has quit IRC13:39
smcginnistbarron: Today is the deadline, so if you think you can land it yet today, we can wait to approve until late in the day.13:39
tbarronsmcginnis: thanks13:39
smcginnisIf you ask really nicely, and you think otherwise you will just need to do an RC2 soon after, we can probably wait until the morning too. But we'd like to avoid that if we can. ;)13:40
*** whoami-rajat has quit IRC13:40
tbarronsmcginnis: yup, I'd rather avoid rc213:41
*** altlogbot_2 has joined #openstack-release13:41
openstackgerritDivya K Konoor proposed openstack/releases master: PowerVMStackers Stein rc1 releases  https://review.openstack.org/64517413:42
*** irclogbot_1 has quit IRC13:45
*** e0ne has joined #openstack-release13:45
*** irclogbot_0 has joined #openstack-release13:47
openstackgerritGuilherme  Steinmuller Pimentel proposed openstack/releases master: Add openstack-ansible cycle-highlights  https://review.openstack.org/64517713:49
openstackgerritIvan Kolodyazhny proposed openstack/releases master: horizon release for stein rc1  https://review.openstack.org/64431613:49
openstackgerritDivya K Konoor proposed openstack/releases master: PowerVMStackers Stein rc1 releases  https://review.openstack.org/64518013:55
openstackgerritGuilherme  Steinmuller Pimentel proposed openstack/releases master: Add openstack-ansible cycle-highlights  https://review.openstack.org/64517713:59
openstackgerritJay Bryant proposed openstack/releases master: cinder release for stein rc1  https://review.openstack.org/64430714:04
*** mlavalle has joined #openstack-release14:05
*** jaosorior has quit IRC14:15
*** whoami-rajat has joined #openstack-release14:23
*** altlogbot_2 has quit IRC14:35
openstackgerritJeremy Freudberg proposed openstack/releases master: sahara-dashboard release for stein rc1  https://review.openstack.org/64434914:36
*** altlogbot_3 has joined #openstack-release14:37
*** dtantsur|brb is now known as dtantsur14:37
*** irclogbot_0 has quit IRC14:38
*** irclogbot_0 has joined #openstack-release14:39
openstackgerritJeremy Freudberg proposed openstack/releases master: sahara release for stein rc1  https://review.openstack.org/64435714:42
openstackgerritJeremy Freudberg proposed openstack/releases master: sahara release for stein rc1  https://review.openstack.org/64435714:42
openstackgerritMerged openstack/releases master: keystone release for stein rc1  https://review.openstack.org/64431714:46
mriedemsmcginnis: i put some alternative words in the nova highlights patch https://review.openstack.org/#/c/644697/14:47
mriedemmelwitt: ^14:47
*** efried has joined #openstack-release14:47
efriedo/14:47
*** cdent has joined #openstack-release14:53
openstackgerritEric Fried proposed openstack/releases master: nova: add stein cycle highlights  https://review.openstack.org/64469714:55
efriedmriedem: ^14:55
openstackgerritMatt Riedemann proposed openstack/releases master: nova: add stein cycle highlights  https://review.openstack.org/64469714:57
mriedemit's VMware geez eric14:57
openstackgerritMichael Johnson proposed openstack/releases master: octavia release for stein rc1  https://review.openstack.org/64434314:58
cdentI shalle report the effort being extended here, internally, and years of sadness will evaporate14:59
openstackgerritMichael Johnson proposed openstack/releases master: octavia-dashboard release for stein rc1  https://review.openstack.org/64434215:03
mriedemheh does their 3rd party ci still work?15:10
*** ekcs has joined #openstack-release15:33
*** armstrong has joined #openstack-release15:34
*** armstrong has quit IRC15:42
*** luizbag has left #openstack-release15:44
smcginnis#startmeeting releaseteam16:00
openstackMeeting started Thu Mar 21 16:00:11 2019 UTC and is due to finish in 60 minutes.  The chair is smcginnis. 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
smcginnisPing list: smcginnis ttx dhellmann diablo_rojo hberaud evrardjp fungi armstrong16:00
hberaudo.16:00
hberaudo/16:00
smcginnis#link https://etherpad.openstack.org/p/stein-relmgt-tracking Agenda16:00
evrardjpo/16:00
dhellmanno/16:00
fungialoha16:00
ricolino/16:00
smcginnisWay down on R-3.16:00
smcginnisMan time flies.16:00
evrardjpyeah16:00
evrardjpvery bottom16:01
ttxo/16:01
*** diablo_rojo has joined #openstack-release16:01
ttxwoohoo16:01
smcginnis#topic Review missing RC1 PTL feedback16:01
*** openstack changes topic to "Review missing RC1 PTL feedback (Meeting topic: releaseteam)"16:01
smcginnis#link  http://tiny.cc/a1mkwy16:01
ttxWe've had decent participation, I feel like posting "by default" helped16:02
smcginnisI think we've gotten quite a few PTL acks, but a lot without yet.16:02
* ttx counts16:02
diablo_rojoO/16:02
ttxabout 20 without -1 or +116:03
ttxout of...16:03
smcginnisNo so bad really.16:03
*** ifat_afek has quit IRC16:03
ttx6616:04
ttxFor Thursday it's not bad at all16:04
smcginnisI think we can process the ones that have had an ack so far.16:04
ttxI guess the uestion is when would we force-approve16:04
ttxtomorrow?16:04
smcginnisAnd either wait until way late tonight, or maybe even tomorrow morning to do the ones that haven't had any response.16:05
ttxThe ones I +2ed should be ok to merge16:05
fungiwe usually release stuff on thursdays, right?16:05
ttxfungi: RCs are ok any time16:05
smcginnisYeah, and Thursday is the stated deadline.16:05
ttxFriday is a way to do EOD Thursday16:05
fungiahh, yeah and i guess if today is the deadline then waiting until tomorrow is fine to consider those have missed it16:05
smcginnisBut we've been a little lenient the last couple cycles I think.16:05
dhellmannI think our past goal has been no later than monday?16:06
smcginnisWe always have had a couple Friday morning from folks not paying enough attention to realize that Thursday is the deadline and not the end of RC1 week.16:06
smcginnisdhellmann: ++16:06
dhellmannwe used to do them "after the release meeting on friday" but that's on thursday now16:06
ttxsmcginnis: how about sending an email today to the list highlighting the ones still needing feedback16:06
smcginnisWhat do folks think, tomorrow or wait until Monday?16:06
dhellmannso maybe 24 hrs from now?16:06
ttxlast chance before forcemerge16:06
ttxdhellmann: ++16:06
smcginnisttx: That's a good idea. I'll mention in the countdown email, then send a separate full list of projects.16:07
smcginnis#action smcginnis to send ML post for projects with no ack16:07
ttxSince it's the first time we do it, i wonder if a specific email warning that we'll do it would be preferable16:07
efriedo/ question on that16:08
ttxI mean, both is good16:08
ttxefried: hello!16:08
efriedWhen stuff is ready, do I update the hash in the patch or do you?16:08
dhellmannefried : you should do it16:08
smcginnisefried: That's up to the projects to do.16:08
efriedack, thx16:08
ttxwe just propose a default in case nobody talks to us16:08
dhellmannthe proposed patches are the "it's better than nothing" version16:08
* ttx fetches an example16:09
efriedIt's cool, I understand.16:09
efriedthanks16:09
smcginnisWe can also do some spot checks before approving the un-ack'd releases to see if anything has merged since we generated them. Though that could take some time to do.16:09
ttxhttps://review.openstack.org/#/c/644317/16:09
ttxThat's exactly how it should work (thanks cmurphy) ^16:09
efriedack16:10
*** e0ne has quit IRC16:10
dhellmannsmcginnis : that feels scriptable16:10
smcginnisYeah, I suppose it could be.16:10
smcginnisOr at least run our unreleased commit script to have an easy reference.16:11
dhellmanngit review -d $patch && list_unreleased_changes.sh $deliverable16:11
smcginnisOh yeah, that should do it.16:11
evrardjpoh yeah16:11
ttxnext topic?16:12
smcginnisYep, I think we have a plan on this one.16:12
smcginnis#topic Post-deadline tasks16:12
*** openstack changes topic to "Post-deadline tasks (Meeting topic: releaseteam)"16:12
dhellmannhmm, that might not work, because the unreleased script looks at actual tags16:12
ttxyeah so I wanted to discuss when to start post-deadline tasks16:12
smcginnisMaybe we could tweak the script.16:12
ttxFriday is not an awesome day to land those16:12
smcginnisMaybe Monday after we approve the remaining RC's?16:13
ttxMaybe prepare them on Friday, land them on Monday?16:13
smcginnis++16:13
ttxsmcginnis: I thought we would approve remaining RCs on Friday16:13
smcginnisWe state "minimum set of projects" for the devstack branching, but do we have that set defined?16:13
dhellmannI think it's whatever is in the integrated-gate16:14
ttxIt's the one that are devstack-integrated16:14
ttxones*16:14
smcginnisttx: OK, I asked what folks thought but don't think we really said. Friday is good. I like sticking closer to the stated deadline.16:14
ttxI mean, it's not the end of the world really16:14
dhellmann+1 for friday16:14
ttxThey can ask for an RC216:14
smcginnisYeah16:14
ttxworst case scenario the RC1 is unusable16:15
ttxBut that would be indicative of a deeper problem16:15
smcginnisProbably wouldn't be the first time.16:15
smcginnisWe do kind of miss the visibility that missing milestones gave us.16:15
smcginnisI think gmann has taken care of the devstack branching in the past.16:16
ttxThere are a bunch of comments on those post-deadline tasks16:16
smcginnisGrenade too?16:16
ttx"IS THIS STILL RIGHT?: "16:16
smcginnisI think we had the same question in Rocky, so we should get some clarification on that.16:17
smcginnisReally a QA task I think.16:17
gmannsmcginnis: you mean after branch cut work right ?16:18
smcginnisgmann: Yeah, we are looking at the Post-deadline Tasks on line 464 here: https://etherpad.openstack.org/p/stein-relmgt-tracking16:18
ttxhttps://opendev.org/openstack-infra/devstack-gate/src/branch/master/devstack-vm-gate-wrap.sh#L29916:18
ttxLooks like that task is still relevant16:18
smcginnisgmann: First 4 (?) tasks I think have usually been done by the QA team, IIRC.16:18
gmannttx: smcginnis yes16:19
dhellmannttx: yeah, I just kept hearing that devstack-gate was deprecated so I wasn't sure. it looks like we need that change.16:19
gmanndhellmann: ttx yeah we still need that change in d-g as grenade still depend on that.16:20
gmannthose bits has not separated out yet16:20
smcginnisgmann: OK, do you have those tasks covered? I think we have it listed in the release process guide just to make sure all the necessary things get done.16:20
gmannsmcginnis: not yet. we are at L464 ? i mean all projects branch already cut ?16:21
ttxLooks like all the "IS THIS STILL RIGHT" is still right16:22
dhellmanngmann : we have not cut all of the branches, but we want to make sure we have these other patches lined up and ready for when we do cut them16:22
gmannyeah16:22
ttxI ceommented on teh etherpad pointing to segments that seem to be branch-sensitive and need updating16:22
smcginnisgmann: Right, not yet. But asking if you have those tasks or if anything is needed from the release team to follow through.16:22
dhellmannttx: ++16:22
gmannsmcginnis: L465 will be release team right? i have not done that in past16:23
* ttx tries to find what L465 aligns with with myopic etherpad alignment16:24
smcginnisgmann: That's this, right? https://review.openstack.org/#/c/591563/16:24
smcginnisOr am I looking at the wrong thing?16:25
gmannsmcginnis: ah sorry i read it wrongly16:25
gmannsmcginnis: yeah i am on those.16:25
smcginnisgmann: OK, thanks!16:26
gmanni see March 22 as deadline for Post-deadline Tasks ?16:26
ttxgmann: to prepare patches yes16:26
gmannttx: cool, I will do it tonight.16:27
ttxWe'd rather not break everything on Friday, so will likely approve them on Monday16:27
gmannok16:27
*** jaosorior has joined #openstack-release16:27
fungithat does seem safer16:27
smcginnis++16:27
openstackgerritMatt Riedemann proposed openstack/releases master: nova: release rocky 18.2.0  https://review.openstack.org/64522716:28
mriedemefried: ^16:28
smcginnisDo we need to reach out to Frank for the translation branching?16:28
smcginnisThat's another one that seemed like the team just knew to do in the past.16:28
fungior ianychoi now16:29
smcginnisDepends when you consider the hand over.16:29
fungiyep16:29
smcginnisBut yeah, either. :)16:29
* ttx dusts off his "release steward" proposal from 201616:29
ttxthe infamous overlapping PTLs proposal16:30
smcginnisWe can ping prometheanfire on the release branching too (see what I did there016:30
* evrardjp has no idea what ttx means16:30
evrardjpttx: you can fill me in after the meeting :D16:30
smcginnisevrardjp: There's been a lack of clarity or differing assumptions on whether the newly elected PTL takes over as soon as the election is done or on the cycle transition.16:30
evrardjpI mean would you mind explaining this proposal to me later?16:31
evrardjpoh16:31
evrardjpthat16:31
efriedIMO previous PTL should continue to do things related to the old release, new PTL should do things related to the new release.16:31
ttxevrardjp: just an idea I floated some time ago that we should ahve people caring for a release before, during and after development cycle16:31
efriedIn cases where the distinction is not clear, new PTL takes over as soon as election ends16:31
smcginnisefried: That's always been my take.16:31
efriedin cases where race is uncontested, arguably when noms close16:31
efriedor by agreement between outgoing and incoming16:32
evrardjpthat's what I've been doing in the past -- worked fine for me16:32
smcginnisExcept when the previous PTL just disappears to a hippy fest and doesn't tell the new PTL that he has to do everything to wrap up the release for the first time ever.16:32
smcginnis:)16:32
ttxThat was back when Forums happen in the middle of the cycle -- the same person would handle that, then the PTG and development cycle, then stable branch releases16:32
evrardjpsmcginnis: haha that happened to me too. :D16:32
smcginnisAnyway, back on topic. ;)16:32
efriedyeah, smcginnis that's people being responsible citizens16:32
ttxpeople were not that happy with the years-long commitment16:32
prometheanfireohai16:32
*** tobias-urdin has quit IRC16:32
smcginnisprometheanfire: We're going through the post-RC1 tasks. One of them is the requirements branching and lifting of the freeze.16:33
smcginnisprometheanfire: Assuming you've got that all covered.16:33
smcginnisprometheanfire: Even though your freeze meme game was sadly lacking this time around. :P16:33
prometheanfireya, if we are branched, have a script to run for that (from releases repo)16:33
evrardjpif?16:34
dhellmanna script?16:34
smcginnisprometheanfire: We are going to process the last of the RC1 and branching tomorrow, so by Monday we should be good to go.16:34
evrardjpa wild confusion appears!16:34
prometheanfiresmcginnis: kk16:34
smcginnisprometheanfire: Thanks16:34
smcginnisLast thing there is the addition of the new branch to openstack-zuul-jobs.16:35
smcginnisI can take that one unless someone else wants it. (?)16:35
fungihappy to review it, just ping me16:36
smcginnisfungi: Will do, thanks16:36
smcginnisThat's it for the list of remaining tasks.16:36
smcginnisAnything else there?16:37
ttxWe also have next week tasks!16:37
ttxah that was what you just discussed16:37
dhellmannit's a shame some of these tools don't look at the series list to determine which branches are valid. maybe we could work on that during train, to cut the number of steps in this process16:37
smcginnis#link https://releases.openstack.org/reference/process.html#between-rc1-and-final16:37
smcginnisdhellmann: That's a good idea.16:37
dhellmannthe devstack-gate scripts in particular seem like they could be candidates, if we produced a CLI they could call16:38
* ttx copy pastes tasks16:38
smcginnisAdded a few of those to the countdown email since they were for that.16:40
smcginnisTwo big tasks there are probably making sure all stable/stein branches are created and adding release note links.16:43
ttxIt's really almost all finalrc week tasks16:44
smcginnisYeah16:44
smcginnisttx: I think it looks good how you've moved things around.16:44
smcginnisWe could maybe update process.rst, but probably not a bad thing to review them ahead of time like this anyway.16:44
ttxDid we discuss "Force missing cycle-with-intermediary releases" ?16:44
smcginnisNo, not really16:45
smcginnisevrardjp or diablo_rojo: Want to take that for next week?16:46
* diablo_rojo catches up on scrollback having just been finishing another simultanous meeting16:46
* diablo_rojo not sure what she's signing up for but..16:46
diablo_rojoSure :)16:46
smcginnisHah16:46
smcginnisdiablo_rojo: Just more generating release patches. Any cycle-with-intermediary deliverables that have had commits merged but no release done yet.16:47
smcginnisWell, I guess that would be only "other" and "service" types, right?16:47
smcginnisWe don't want to do more lib or client lib releases past the deadline.16:48
diablo_rojosmcginnis, so basically the same as I did Monday but with cycle with intermediary16:48
evrardjpwe'll take it and come beg for comments as usual :)16:48
evrardjp:D16:48
smcginnisdiablo_rojo: Basically, but they are only needed if they've committed anything since the last release.16:48
dhellmannit looks like most of the unreleased things are tempest plugins16:49
smcginnisOh right, we do need to make sure all the tempest plugins get released and branched.16:49
dhellmannevrardjp , diablo_rojo : I hope you're making notes about how to improve the details16:49
smcginnis:)16:49
* diablo_rojo knows where to find the meeting logs links :) 16:50
evrardjpdhellmann: We are opening this meeting log every time we do it.16:50
dhellmannsmcginnis : do we branch the tempest plugins?16:50
evrardjpdiablo_rojo: :)16:50
diablo_rojolol16:50
dhellmannevrardjp : we should get those improvements into the process doc16:50
evrardjp indeed16:50
smcginnisdiablo_rojo: Yeah, we started last cycle just mainly for the purpose of knowing which plugins are expected to work with which version of tempest.16:50
dhellmannnote that is the democratic "we" not the royal "we" (so "you")16:50
diablo_rojosmcginnis, that makes sense16:51
evrardjpdhellmann: :)16:51
smcginnisOK, I'll move on then.16:51
smcginnis#topic Ensuring stable-maint-core is in all official projects16:51
*** openstack changes topic to "Ensuring stable-maint-core is in all official projects (Meeting topic: releaseteam)"16:51
smcginnisWe have official projects that do not have stable-main-core in the ACL.16:51
ttxah?16:52
smcginnisttx: Is that something that could feasibly be added to the acl checker?16:52
ttxMaybe? I'll have to look16:52
ttxdo you have one example of missing?16:52
smcginnisOK, I just wanted to raise it. Not super important. Most have been like this for a long time.16:52
smcginnisneutron-lib was one I noticed.16:52
ttxHow about adding that to the list of things to improve, if it's not urgent16:53
dhellmannif we work out how to do that, we could add it to the branch validation rules in the releases repo16:53
smcginnisOh, down at the bottom?16:53
ttxyes16:53
ttx++16:53
smcginnisDone16:53
ttxthat will basically be our PTG agenda16:54
smcginnisLast thing quick, though not necessarily have to cover it in the meeting.16:54
smcginnis#topic Placement idea to use cycle-with-intermediary16:54
*** openstack changes topic to "Placement idea to use cycle-with-intermediary (Meeting topic: releaseteam)"16:54
ttxcan you summarize the idea?16:54
evrardjpoh16:54
smcginnisChris had some questions about releasing per microversion bump in placement.16:54
smcginnisSince it's basically all an API.16:54
smcginnisSo if they bump microversion 1.35, release version 1.35.16:55
ttxIIRC there was some difference between API microversioning and semver16:55
cdentoh hi. it's a very speculative idea at this point, but wondered about the feasability16:55
dhellmannthey can release as often as they want, but to start every cycle they have to tag a new minor version at least in order to provide space for bug fixes, so things may come out of alignment quickly16:55
ttxlike x.y vs. x.y.z16:55
ttxI guess it could be 1.35.0 for microversion 1.3516:56
smcginnisOnly drawbacks I could see are 1) if anything backward incompatible they would need to do a major bump, and 2, we currently require c-w-i at least every milestone and it's possible development stabilizes enough not to need a microversion bump each milestone period.16:56
cdentttx, if (and it is a big if) we did this: microversion 1.35 would be 1.35.016:56
cdentjinx16:56
ttxif really all features are reflected in the API16:56
dhellmannyeah, the problem isn't within the cycle, it's at the cycle boundaries16:56
smcginnisAnd then still room for bugfixes.16:56
ttxOne issue that was raised in the past is that in some cases we twist the rule for the release number, but keep the microoversion honest. Imagine this scenario16:57
cdentit sounds like more trouble than it is worht16:57
ttxWe are in the middle of U16:57
ttxA security issue is found in T16:57
smcginnisI should have stated, it was just an idea cdent was pondering, so I wanted to bring it up for issues I wasn't thinking of with doing it.16:58
*** ricolin has quit IRC16:58
ttxhmm beh16:58
ttxlost my thought16:58
smcginnisStable backport?16:58
ttxISTR there was this case where you would bump major API version but only bump .z in version number16:59
ttxlike the rules were just different16:59
cdentI think the only way it would work, in any real way, would be if we stopped doing stable branches, which is possible in a microversioned world since they are opt in. If you want a security fix, you must upgrade, but you don't have to use the new features. In the context of the way openstack projects normally work that would be a non-starter...16:59
smcginnisOh well, it was an idea worth exploring.17:00
cdentI reckon there are multiple ideas to take from it17:00
cdentbut not something that is immediately actionable17:00
dhellmanndropping stable branches would break the ability for downstream consumers to deal with fixes without also breaking co-installability as dependency versions increase17:00
smcginnisI'm going to end the meeting since we're over the time, but we can continue discussing.17:01
smcginnisThanks all!17:01
smcginnis#endmeeting17:01
ttxrandom end-of-meeting question: should I single approve the bunch of RC1s that have PTL+1? Or would you rather have another pair of eyes on them ? Approved a bunch this morning already17:01
*** 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:01
openstackMeeting ended Thu Mar 21 17:01:23 2019 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/releaseteam/2019/releaseteam.2019-03-21-16.00.html17:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/releaseteam/2019/releaseteam.2019-03-21-16.00.txt17:01
openstackLog:            http://eavesdrop.openstack.org/meetings/releaseteam/2019/releaseteam.2019-03-21-16.00.log.html17:01
ttxjinx17:01
smcginnisttx: Single approve is fine I think.17:01
fungithanks smcginnis!17:01
* ttx gets wild17:01
smcginnisI have been if the PTL has given their ack.17:01
smcginnis:)17:01
dhellmann++17:01
*** tesseract has quit IRC17:02
openstackgerritDmitry Tantsur proposed openstack/releases master: Release ironic 12.1.0 and create stable/stein  https://review.openstack.org/64523417:02
cdentdhellmann: that's what I meant by "non-starter"17:03
cdentBut I suspect things like this are going to come up more and more as more projects start thinking about ways they can engage with non-openstack projects/products.17:04
ttxfire in the hole17:04
smcginnisNice, that will get a lot of them out of the queue.17:07
*** ekcs has quit IRC17:08
openstackgerritDmitry Tantsur proposed openstack/releases master: Release ironic-tempest-plugin 1.3.0  https://review.openstack.org/64523717:09
*** ifat_afek has joined #openstack-release17:12
fungicdent: i don't think it's a non-starter *if* you sufficiently dispose of a tight coupling between versions of placement and other software such that it's just treated as a versioned dependency, but you'd still need to come up with a scheme for backporting fixes to earlier versions in wide use17:13
*** ifat_afek has quit IRC17:13
cdentfungi: the full version of what I said was that backporting wouldn't happen: if you wanted fixes you'd have to upgrade, but choose to not opt in to some microversions17:14
fungiand ultimately you'd end up mostly reinventing our current stable branch management, i expect17:14
cdentso no stable branches, no backports17:14
fungiand then placement 1.35 ends up in rhel 8 and someone has to do the backporting work to that version anyway17:15
fungiwhich it's valid to say is up to the distros to just take care of17:15
fungibut then multiple distros are doing the same work needlessly, so they ask upstream for a branch to coordinate those backports on17:16
openstackgerritMerged openstack/releases master: Release Vitrage deliverables for Stein  https://review.openstack.org/64482017:16
openstackgerritMerged openstack/releases master: nova: add stein cycle highlights  https://review.openstack.org/64469717:16
openstackgerritMerged openstack/releases master: Release Puppet OpenStack Stein RC1  https://review.openstack.org/64445617:16
openstackgerritMerged openstack/releases master: PowerVMStackers Stein rc1 releases  https://review.openstack.org/64518017:16
openstackgerritMerged openstack/releases master: cinder release for stein rc1  https://review.openstack.org/64430717:16
*** mriedem is now known as mriedem_grooming17:16
openstackgerritMerged openstack/releases master: sahara-dashboard release for stein rc1  https://review.openstack.org/64434917:16
fungicdent: and then bingo, you've just rediscovered why we have stable branches17:16
openstackgerritMerged openstack/releases master: sahara release for stein rc1  https://review.openstack.org/64435717:17
cdentfungi: I'm sure I keep saying "non-starter" but maybe it's not landing. I'm off in theoretical land of a world where legacy things like distros and operating systems really are legacy17:17
cdentto me, placement is a thing you install from pypi and put in a container17:18
fungiahh17:18
fungiyes, from what i've seen so far, that model is popular with start-ups who are looking to get bought in 2 years time and let someone else deal with the mess their wild west server management has resulted in17:19
fungiless so for established organizations who would like to have a server run for years and hardly be touched except for critical security updates17:20
dtantsurfolks, out of curiosity, why does 'list-deliverables --team ironic' include tempest-horizon? :)17:20
openstackgerritMerged openstack/releases master: octavia-dashboard release for stein rc1  https://review.openstack.org/64434217:20
openstackgerritMerged openstack/releases master: octavia release for stein rc1  https://review.openstack.org/64434317:20
openstackgerritdharmendra kushwaha proposed openstack/releases master: tacker release for stein rc1  https://review.openstack.org/64436317:21
fungidtantsur: great question. almost certainly a bug since governance says it's part of horizon17:21
cdentfungi: destroying those organizations is my long term raison d'etre17:22
fungidown with the man! ;)17:22
smcginnisdtantsur, fungi: Looks like somehow the team tag in the placeholder deliverable file is "team: ironic"17:22
dtantsurlol17:23
*** jpich has quit IRC17:23
fungicool, you found it where i was working on looking, so i was on the right track17:23
dtantsurnova is too old-school, ironic is the default openstack now!17:23
smcginnisLooks like Ivan must have copied an existing deliverable yaml and forgot to update that one.17:23
smcginnisdtantsur: :)17:24
fungiperhaps he found it ironic that horizon has a tempest plugin17:24
dtantsurLOL17:24
smcginnisHaha17:24
cdentdtantsur++17:24
dtantsurTheJulia: ^^ ironic jokes for your pleasure17:24
openstackgerritMerged openstack/releases master: horizon release for stein rc1  https://review.openstack.org/64431617:25
openstackgerritSean McGinnis proposed openstack/releases master: Fix tempest-horizon team  https://review.openstack.org/64526217:25
TheJulialol17:25
smcginnisIt will probably get updated when the tempest plugin is released, but just to be safe we can switch it quick. ^^17:25
*** dtantsur is now known as dtantsur|afk17:30
*** gmann is now known as gmann_afk17:43
openstackgerritMerged openstack/releases master: Add cycle highlights for kolla and kolla ansible  https://review.openstack.org/64450617:49
*** ekcs has joined #openstack-release17:49
openstackgerritdharmendra kushwaha proposed openstack/releases master: tacker release for stein rc1  https://review.openstack.org/64436317:59
*** dkushwaha_ has joined #openstack-release18:03
cmurphywe seem to be missing our current series/stein release notes https://docs.openstack.org/releasenotes/keystone/unreleased.html what did we do wrong there? I see other projects have release notes for their rc1 (cc lbragstad)18:04
*** e0ne has joined #openstack-release18:05
lbragstadthanks for pinging cmurphy - i was going to do that earlier and the release meeting was underway18:08
*** e0ne has quit IRC18:12
dtruongdiablo_rojo smcginnis I noticed that senlin-dashboard does not have a stein branch yet.  Do I need to propose that change myself or will the release team do that? https://opendev.org/openstack/releases/src/branch/master/deliverables/stein/senlin-dashboard.yaml18:20
*** whoami-rajat has quit IRC18:23
dkushwaha_smcginnis: Tacker has cycle-with-rc , So Do I needs to create stable/Stein right now(in RC-1) or is it ok if I make a release candidate now and stable/Stein later (anytime before final rc 1April-5April)18:26
*** gmann_afk is now known as gmann18:40
*** electrofelix has quit IRC18:43
*** mriedem_grooming is now known as mriedem18:53
openstackgerritLuka Peschke proposed openstack/releases master: cloudkitty release for stein rc1  https://review.openstack.org/64430818:56
smcginnisdtruong: If you would like to propose that now you can. Otherwise we will catch anyone that missed it next week.19:00
smcginnisdkushwaha_: The stable/stein branch would be created along with RC1.19:00
smcginniscmurphy, lbragstad: The right release notes should show up when the final release is done and the deliverable has a diff-start telling it to go from 14.0.0.0rc1 to the 15.0 tag.19:03
openstackgerritdharmendra kushwaha proposed openstack/releases master: tacker release for stein rc1  https://review.openstack.org/64436319:05
lbragstadaha19:06
dkushwaha_smcginnis: Thanks19:06
lbragstadso - around the first week of april we should see that?19:06
smcginnisdkushwaha_: Thanks for the update.19:07
smcginnislbragstad: Does that unreleased not have any of the stein notes?19:07
lbragstadnope19:07
smcginnislbragstad: Are they there if you build the release notes locally?19:08
* lbragstad checks19:08
smcginnisLooks like the Cinder ones are showing up in the published unreleased notes.19:09
smcginnisNot sure why there would be a difference.19:09
lbragstadsome show up - but i don't think all of them do?19:12
smcginnisI've seen something similar, but they always seem to clear up in the end.19:13
*** cdent has quit IRC19:13
smcginnisNot sure why. Maybe dhellmann can explain it.19:13
lbragstadfwiw - i know all of these fixes have release notes http://tinyurl.com/y53dwtt219:13
smcginnisHmm, I would expect the output to be a lot longer then for sure.19:14
lbragstadat the very least - https://launchpad.net/keystone/+milestone/stein-319:14
cmurphyi see a lot of release notes in unreleased.html when i build them, i see none in https://docs.openstack.org/releasenotes/keystone/unreleased.html19:15
*** dkushwaha_ has quit IRC19:15
*** cdent has joined #openstack-release19:15
smcginnisThat's really odd. They should at least be the same, even if incomplete.19:15
cmurphyoh, refreshed and some are there19:15
smcginnisBrowser caching has led me on some wild goose chases before. :)19:16
lbragstad63 bugs worth?19:16
cmurphy4 bugs19:16
smcginnisDo you include a release note with every bug fix?19:16
lbragstadfor the most part, yeah19:17
cmurphy$ git log --oneline --no-merges stable/rocky..HEAD releasenotes/notes/ | wc -l19:17
lbragstadif it impacts end users or operators, we try and include release notes19:17
cmurphy6919:17
lbragstadnice19:17
cmurphysome where around that is how many we should have19:17
* lbragstad puts that in his back pocket19:17
cmurphydefinitely >419:17
cmurphyoh i think i get it, there's now a stable/stein branch and all those release notes are there, those 4 are the ones we just merged in the last few hours19:19
cmurphybut there's no Stein series link in https://docs.openstack.org/releasenotes/keystone/19:20
lbragstadaha19:20
lbragstadyeah19:20
smcginnisOh, yep!19:20
lbragstadhttps://docs.openstack.org/releasenotes/keystone/stein.html19:20
smcginnisThe branching should have triggered some patches to add the stein link.19:20
smcginnisSince there's nothing linking to it, I think sphinx doesn't include it.19:21
smcginnisSomething like that.19:21
openstackgerritDuc Truong proposed openstack/releases master: Reword Senlin cycle highlights to more clear  https://review.openstack.org/64530619:21
dhellmannthe branch creation process adds the stein page to the release notes (via a review)19:21
smcginnislbragstad, cmurphy: Approving this should fix it for you: https://review.openstack.org/#/c/645201/119:22
smcginnisdhellmann: Mind taking a quick poke at https://review.openstack.org/#/c/645262/19:22
dhellmannhttp://git.openstack.org/cgit/openstack-infra/project-config/tree/roles/copy-release-tools-scripts/files/release-tools/make_branch.sh#n7119:22
cmurphyoh look at that19:22
lbragstadit *even* has a descriptive title and commit message19:23
dhellmannsmcginnis : approved19:23
smcginnisThanks19:23
lbragstadthanks smcginnis19:23
cmurphythanks smcginnis !19:23
smcginnisEasy to forget how all these cogs fit together to keep the machine going. ;)19:23
dhellmannwe need fewer cogs19:23
dhellmannor more obvious ones19:24
smcginnisThey work pretty good, just gotta pull out the schematics from time to time.19:24
smcginnisAnd remember to keep the blinker fluid full.19:24
cdentdon't put the blinker fluid in the brake fluid19:25
smcginnisDisasterous19:25
*** whoami-rajat has joined #openstack-release19:26
* dhellmann makes a note19:26
*** e0ne has joined #openstack-release19:30
openstackgerritMerged openstack/releases master: Fix tempest-horizon team  https://review.openstack.org/64526219:33
openstackgerritAde Lee proposed openstack/releases master: Add cycle highlights for Barbican  https://review.openstack.org/64531419:38
edmondswanyone else seeing openstack-tox-lower-constraints failing with "AttributeError: module 'appdirs' has no attribute 'system'"?19:38
openstackgerritMerged openstack/releases master: Release ironic-tempest-plugin 1.3.0  https://review.openstack.org/64523719:39
edmondswI'm just noticing this on the automatic patches to stable/stein e.g. https://review.openstack.org/#/c/645245/19:40
smcginnisHmm, I wonder if that's a side effect of the zuul update with a newer ansible.19:40
smcginnisedmondsw: You're referring to this, right? http://logs.openstack.org/45/645245/1/check/openstack-tox-lower-constraints/dbd4f19/job-output.txt.gz#_2019-03-21_17_38_26_80186019:41
edmondswyes19:41
smcginnisAny idea on that one fungi? We can just ask in -infra if that's better.19:41
edmondswyeah, I wasn't sure whether to start here or there19:41
smcginnisI'm guessing we're going to need some ansible expertise here that they might be better able to answer. Let's move over there.19:42
edmondswsure19:42
fungiyes, please19:42
fungibut i suspect you're right about what's exposed it19:43
openstackgerritAde Lee proposed openstack/releases master: Release barbican 8.0.0.0  https://review.openstack.org/64531819:47
*** e0ne has quit IRC19:49
openstackgerritGuilherme  Steinmuller Pimentel proposed openstack/releases master: Add openstack-ansible cycle-highlights  https://review.openstack.org/64517719:50
*** e0ne has joined #openstack-release19:52
openstackgerritMerged openstack/releases master: Release ironic 12.1.0 and create stable/stein  https://review.openstack.org/64523419:52
openstackgerritMerged openstack/releases master: Add Blazar cycle highlights for Stein  https://review.openstack.org/64502519:53
openstackgerritMerged openstack/releases master: Add karbor cycle highlights for Stein  https://review.openstack.org/64504619:53
openstackgerritSpyros Trigazis proposed openstack/releases master: magnum release for stein rc1  https://review.openstack.org/64431819:57
*** e0ne has quit IRC20:04
openstackgerritMerged openstack/releases master: designate release for stein rc1  https://review.openstack.org/64431320:08
*** ekcs has quit IRC20:10
openstackgerritMerged openstack/releases master: Oslo Stein Cycle Highlights  https://review.openstack.org/64501920:11
*** ekcs has joined #openstack-release20:11
openstackgerritFeilong Wang proposed openstack/releases master: magnum release for stein rc1  https://review.openstack.org/64431820:14
openstackgerritMerged openstack/releases master: barbican release for stein rc1  https://review.openstack.org/64430320:16
openstackgerritTom Barron proposed openstack/releases master: manila release for stein rc1  https://review.openstack.org/64431920:16
openstackgerritMerged openstack/releases master: cloudkitty release for stein rc1  https://review.openstack.org/64430820:19
*** cdent has quit IRC20:24
*** e0ne has joined #openstack-release20:28
openstackgerritAde Lee proposed openstack/releases master: Add cycle highlights for Barbican  https://review.openstack.org/64531420:31
dtroyersmcginnis: is python-openstackclient included in any of your batch branching process?  Or should I just submit the stable branch request as usual?  I'm having a hard time keeping this process in my head…20:32
*** armax has joined #openstack-release20:32
smcginnisdtroyer: If it is ready, then it would be good if you can propose it.20:33
dtroyerwill do, thanks20:33
smcginnisdtroyer: Otherwise early next week we will go through all the cycle-with-intermediary deliverables and get the branches added for any that missed them.20:33
openstackgerritMerged openstack/releases master: tacker release for stein rc1  https://review.openstack.org/64436320:34
openstackgerritDean Troyer proposed openstack/releases master: stable/stein branch for python-openstackclient  https://review.openstack.org/64533820:34
openstackgerritSean McGinnis proposed openstack/releases master: panko release for stein rc1  https://review.openstack.org/64434420:37
*** jtomasek has quit IRC20:55
*** armax has quit IRC21:00
openstackgerritMiguel Lavalle proposed openstack/releases master: networking-midonet release for stein rc1  https://review.openstack.org/64432821:07
openstackgerritMerged openstack/releases master: networking-bagpipe release for stein rc1  https://review.openstack.org/64432621:10
openstackgerritMerged openstack/releases master: networking-bgpvpn release for stein rc1  https://review.openstack.org/64432721:10
tonybsmcginnis: Yeah I keep meaning to audit offical projecst with stable:follow-policy and ensure they contain the stable-maint-core21:11
smcginnistonyb: I was thinking afterwards, some of the ones I've seen without it might not actually be stable:follows-policy.21:12
smcginnisCould explain at least some of it.21:13
smcginnisBut I thought neutron-lib was due to the team, but maybe not?21:13
*** e0ne has quit IRC21:17
*** armax has joined #openstack-release21:17
tonybsmcginnis: Yeah I'm not sure it is because they want to be able to break internal APIs which is a bad idea etc and I kinda think that it means that anything that depends on neutron-lib violates the stable-policy by association but I'm not going to really try anf make that argument21:17
tonybI like my friends and don't want to lose them ;p21:18
smcginnis;)21:18
smcginnistbarron: Just double checking - your update of https://review.openstack.org/#/c/644319/ means manila is good to go, right?21:19
openstackgerritMerged openstack/releases master: neutron-dynamic-routing release for stein rc1  https://review.openstack.org/64433321:26
openstackgerritMerged openstack/releases master: magnum release for stein rc1  https://review.openstack.org/64431821:30
tonybDo we have a plan for the chnages in https://review.openstack.org/#/q/status:open+project:openstack/releases+branch:master+message:rc1 that have neither an +/-1 vote from PTL?21:33
*** pcaruana has quit IRC21:33
tonybAcxtually that's probably in the meeting logs that I haven't read yet21:33
* tonyb goes to do that21:33
openstackgerritMerged openstack/releases master: networking-midonet release for stein rc1  https://review.openstack.org/64432821:36
tonybSo y'all said 'Monday' is that mine or yours ;P21:36
tonybsmcginnis, dhellmann: Can we discuss http://eavesdrop.openstack.org/meetings/releaseteam/2019/releaseteam.2019-03-21-16.00.log.html#l-186 at the PTG?21:40
* tonyb is all for making tools smarter21:40
tonybsmcginnis: do we have a PTG planning etherpad yet?21:40
dhellmanntonyb : we started making a list of topics at the bottom of https://etherpad.openstack.org/p/stein-relmgt-tracking21:41
dhellmann"Things to fix"21:41
tonybdhellmann: Thanks21:42
tbarronsmcginnis: well if it sat there a couple more hours I'd probably bump the hash again but I don't want to hold things up21:42
tbarronsmcginnis: we have a bug fix that's going to require a microversion bump but they're having issues getting it just right21:43
tbarronsmcginnis: i.e. it will require a microversion bump if it's not included in stein21:44
openstackgerritTobias Urdin proposed openstack/releases master: Release puppet-ceph 2.6.0 and branch stable/mimic  https://review.openstack.org/64459921:44
tbarronsmcginnis: not the end of the world but either we do an rc2 to avoid that or maybe a quick extra stable/stein release21:45
tonybtbarron: Well we can hold RC1 or you can do an RC2 with it in21:45
tonybtbarron: snap21:45
*** whoami-rajat has quit IRC21:45
*** armax has quit IRC21:45
tonybtbarron: RC1 would be better if you can clear the gate issue21:45
tbarrontonyb: agree, so we've got a bit more time then?21:46
*** gouthamr has joined #openstack-release21:48
tonybtbarron: Yeah at least your Friday (and the weekend) IIUC21:49
dhellmannleave notes about that on the relevant RC patch, please21:50
tbarrondhellmann: tonyb got it, putting notes on the patch now.21:50
smcginnisYeah, today's the deadline, but if we have to hold a bit to make sure the RC is good, that's fine.21:51
openstackgerritMiguel Lavalle proposed openstack/releases master: neutron-fwaas release for stein rc1  https://review.openstack.org/64433521:52
tbarronsmcginnis: tonyb: dhellman: thanks21:53
openstackgerritMerged openstack/releases master: networking-sfc release for stein rc1  https://review.openstack.org/64433222:04
*** irclogbot_0 has quit IRC22:05
*** mgoddard has quit IRC22:08
*** armax has joined #openstack-release22:09
*** mgoddard has joined #openstack-release22:09
efriedAfter 6h in the check queue, https://review.openstack.org/642863 is allllmost ready to move to the gate queue.22:11
efriedThis is the last thing we're awaiting for nova rc22:11
openstackgerritMiguel Lavalle proposed openstack/releases master: networking-odl release for stein rc1  https://review.openstack.org/64432922:19
tonyb[m]Wow 6h in check :-(22:19
*** armax has quit IRC22:20
openstackgerritMiguel Lavalle proposed openstack/releases master: networking-ovn release for stein rc1  https://review.openstack.org/64433022:24
*** armax has joined #openstack-release22:27
*** armax has quit IRC22:32
*** armax has joined #openstack-release22:35
*** armax has quit IRC22:38
*** mriedem is now known as mriedem_afk22:50
efriedmriedem_afk and others: I need to leave for at least three hours. https://review.openstack.org/642863 is in the gate, finished the easy jobs, still queued for the slow ones. It might land while I'm gone. If anyone wishes to repropose the rc1 patch22:57
efriedhttps://review.openstack.org/#/c/644341/22:57
efriedat that time, please do. Otherwise I will do it when I return.22:57
*** tosky has quit IRC22:59
*** armax has joined #openstack-release23:09
*** armax has quit IRC23:26
openstackgerritMichael Johnson proposed openstack/releases master: Release octavia-tempest-plugin for Stein  https://review.openstack.org/64539923:32
openstackgerritMerged openstack/releases master: networking-odl release for stein rc1  https://review.openstack.org/64432923:37
*** lbragstad has quit IRC23:46
« Wednesday, 2019-03-20 Index Friday, 2019-03-22 »

Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!