Thursday, 2020-04-09

*** bauzas has quit IRC01:01
openstackgerritShogo Saito proposed openstack/releases master: Release final python-cyborgclient for ussuri
*** bauzas has joined #openstack-release01:29
*** corvus has quit IRC01:48
*** corvus has joined #openstack-release01:49
openstackgerritAkihiro Motoki proposed openstack/releases master: xstatic packages: first release via the releases repo
*** evrardjp has quit IRC04:37
*** evrardjp has joined #openstack-release04:37
*** udesale has joined #openstack-release04:40
*** ykarel|away is now known as ykarel04:47
*** _mlavalle_1 has joined #openstack-release04:50
*** mlavalle has quit IRC04:53
*** jbadiapa has quit IRC05:20
*** armax has quit IRC05:28
*** slaweq_ has quit IRC06:36
*** slaweq_ has joined #openstack-release06:37
*** slaweq_ has quit IRC06:41
*** _mlavalle_1 has quit IRC06:41
*** sshnaidm|afk is now known as sshnaidm06:55
*** jtomasek has joined #openstack-release06:57
*** jtomasek has quit IRC06:59
*** jtomasek has joined #openstack-release06:59
*** vishalmanchanda has joined #openstack-release06:59
*** ricolin has quit IRC06:59
*** slaweq_ has joined #openstack-release07:00
*** zxiiro has quit IRC07:01
*** slaweq_ is now known as slaweq07:03
*** dtantsur|afk is now known as dtantsur07:06
*** rpittau|afk is now known as rpittau07:18
openstackgerritSlawek Kaplonski proposed openstack/releases master: Add Ussuri cycle highlights for Neutron
openstackgerritDmitry Tantsur proposed openstack/releases master: Cycle highlights for ironic
*** tosky has joined #openstack-release07:42
*** ricolin has joined #openstack-release07:44
*** e0ne has joined #openstack-release08:33
*** tobias-urdin has quit IRC09:02
openstackgerritSlawek Kaplonski proposed openstack/releases master: Add Ussuri cycle highlights for Neutron
*** ykarel is now known as ykarel|lunch09:09
openstackgerritMark Goddard proposed openstack/releases master: Release ironic-ui 3.5.4 for Train
openstackgerritMerged openstack/reno master: Update hacking for Python3
openstackgerritMerged openstack/releases master: Release final python-karborclient for ussuri
*** tobias-urdin has joined #openstack-release09:30
openstackgerritMerged openstack/releases master: Drop email content weekly link from tracking template
*** udesale_ has joined #openstack-release09:34
*** udesale has quit IRC09:38
*** ykarel|lunch is now known as ykarel09:51
ttxPrepared release tasks leading to final release in
*** rpittau is now known as rpittau|bbl10:13
openstackgerritThierry Carrez proposed openstack/releases master: Release ironic-ui 3.5.5 for Train
openstackgerritThierry Carrez proposed openstack/releases master: Fix formatting issues in R-2 week
openstackgerritMerged openstack/releases master: Release python-saharaclient 3.1.0
openstackgerritMerged openstack/releases master: Release final python-troveclient for ussuri
openstackgerritMerged openstack/releases master: Release final python-qinlingclient for ussuri
openstackgerritMerged openstack/releases master: Release final python-searchlightclient for ussuri
openstackgerritMerged openstack/releases master: Release final python-designateclient for ussuri
openstackgerritMerged openstack/releases master: Release final python-congressclient for ussuri
openstackgerritMerged openstack/releases master: Release final python-mistralclient for ussuri
openstackgerritlicanwei proposed openstack/releases master: Release final python-watcherclient for ussuri
*** mgoddard has quit IRC11:02
openstackgerritSlawek Kaplonski proposed openstack/releases master: Add Ussuri cycle highlights for Neutron
openstackgerritBalazs Gibizer proposed openstack/releases master: Release final python-novaclient for ussuri
*** rpittau|bbl is now known as rpittau11:57
openstackgerritEmilien Macchi proposed openstack/releases master: train: release tripleo-ansible 0.5.0
openstackgerritBalazs Gibizer proposed openstack/releases master: nova: ussuri cycle highlights
openstackgerritDmitry Tantsur proposed openstack/releases master: Cycle highlights for ironic
EmilienMttx: hey, would it be possible to expediate please?12:27
EmilienMsmcginnis: thanks :-)12:30
EmilienMsmcginnis: hope everything is fine for you12:30
EmilienMlong time no see...12:30
smcginnisEmilienM: Any time. I hope you're doing well too.12:30
smcginnisIt has been awhile!12:30
smcginnisStill in Canada?12:30
EmilienMsmcginnis: all good here :)12:30
EmilienMsmcginnis: yes, in Quebec City.12:31
smcginnisHope you and your family are staying safe. Will be nice to run into each other at an event again some day.12:32
EmilienMsmcginnis: same for you :)12:32
smcginnisttx: For the PTL-approved code, would it make sense to change that from looking at ['owner']['name'] to ['author']['name']?12:44
smcginnisThe two issues I see is a ptl can submit a patch, someone else can modify it, but it will say PTL approved even though they may have changed it to something the PTL doesn't agree with.12:44
ttxthat is a fair remark12:45
smcginnisAnd second case, non-ptl can submit the original patch, PTL updates it with a preferred hash, but it doesn't reflect approval until the PTL actually leaves +1 because it doesn't register that the PTL is the one that udpated it.12:45
ttxBut I think anyone can set the author12:46
smcginnisOh, I didn't realize that.12:46
ttxSo to get PTL+1 you just need to pretend to be the PTL12:46
smcginnisAnything in the gerrit json that is reliable to show who actually is submitting the patch?12:46
ttxIf PTL updates it, they need to +1 it12:46
ttxah... hmm12:47
smcginnisOK, fair enough.12:47
ttxthere probably is something12:47
ttxI'll have a look. Not right now though12:47
smcginnisYeah, not high priority by any means.12:47
openstackgerritDmitry Tantsur proposed openstack/releases master: Cycle highlights for ironic
*** ykarel is now known as ykarel|afk13:11
EmilienMif anyone has a chance to approve this simple release request:
EmilienMit would unblock our upgrade jobs in CI. Thanks a lot13:18
evrardjpI am still in the middle of the review13:18
evrardjpI am rushing :)13:18
EmilienMoh thanks; i didn't want you to rush your meeting13:19
EmilienMwhich is why I asked here :)13:19
evrardjpwell it was a 30 minutes meeting, I was still in it 2 minutes ago, after 75 minutes being in it.13:19
EmilienMouch :D13:20
evrardjpyeah that changes the planning13:20
evrardjpthough we made progress, so there is that.13:20
evrardjpthere are quite some big changes, but if it breaks, you can pin it on me! :p13:21
EmilienMI'm not sure what would break13:21
EmilienMwe just need a tag so our packaging gets a new version number13:22
EmilienMit's that simple for us...13:22
evrardjpI pressed the button13:23
evrardjpEmilienM: that seems a lot of effort and checking for something as simple as a version number....13:23
evrardjpI definitely have to finish writing up my releases change in the "ideas" framework...13:24
evrardjpIf anyone asks, I haven't seen any major removal that would warrant a
evrardjpperfect timing, ready for my next meeting!13:26
openstackgerritMerged openstack/releases master: train: release tripleo-ansible 0.5.0
*** priteau has joined #openstack-release13:49
*** e0ne has quit IRC13:53
*** e0ne has joined #openstack-release13:54
*** ykarel|afk is now known as ykarel14:02
gmanndiablo_rojo_phon: if i read correctly in your email. we cannot amend the Highlights for FFE features in existing because text of highlights are used by marketing team not the link of highlights. -
*** dave-mccowan has joined #openstack-release14:14
*** Jeffrey4l has quit IRC14:22
*** Jeffrey4l has joined #openstack-release14:23
gibismcginnis: hi! How hard the today's client release deadline? nova has two API patches approved but not merged yet, both needs a trivial client change to land _after_ the API change landed. Based on the speed of the gate the nova API changes won't land today14:30
*** dave-mccowan has quit IRC14:30
smcginnisgibi: As long as things are in flight, we should be OK holding off a little bit to give those time.14:35
ttxgmann: you can update the highlights whenever you want. The trick is that we point the marketing team to the contents, and they start to work on release messaging. The latter you add, the less likely it is to be mentioned and shape the overall message14:35
smcginnisIf there's anything that is not already on its way, it might be good to decide whether that should wait for V or not.14:35
ttxThe later ?14:35
gibismcginnis: thanks. everything is in flight (approved) I will keep the release patch updtadet14:35
gibismcginnis: tomorrow I'm off but bauzas will be my standin regarding the release14:36
smcginnisgibi: Perfect. Thanks for the heads up.14:36
bauzasgibi: yup, just shoot the tracking etherpad and I'll just update the release patch if needed14:37
gmannttx: thanks. ack.14:37
* bauzas still has its release management suit14:37
bauzascycle highlights are only due by RC1, right?14:37
gibibauzas: nope, due today14:38
bauzasoh man14:38
bauzasin the same patch then I guess14:38
bauzasoh actually no14:38
bauzashonestly, cutting M-2 the eve of Easter Friday wasn't great :)14:38
gibiM3 :D14:39
bauzasI'm doomed14:39
gibibauzas: I updated the highlights today, I will do another update before I leave if we accept gmann's FFE on the today's nova meeting14:39
bauzasgibi: actually, good question, which kind of exception we're about to talk ? a few days, say Monday/Tuesday at least ?14:40
bauzasthis being said, the policy thing is a large cross-project effort, so I won't veto the exception (that's a huuge spoiler)14:41
gibibauzas: we have 3 weeks until RC114:41
gibibauzas: I would say that next week is OK for FFE14:41
bauzasgibi: I only count 2 weeks or I am blind14:42
bauzasR-5 to R-3 makes me count 2 weeks14:43
gibish*t yo are right, I was blind14:43
gibithen a full week is out of question14:43
bauzasand we have Easter in the while14:43
gibiI would day Wednesday due to Easter14:43
bauzasbut let's not overload this channel14:43
bauzasthis is a nova thign14:43
gmannttx: if I am correct its text being used for various marketing forum not the link to release page of highlights right ?14:50
openstackgerritSean McGinnis proposed openstack/releases master: Add stable/ussuri for python-designateclient
smcginnismugsie: Branching is part of the lib freeze, but we were working on getting some job template updates in place. That should be ready now (knock on wood). Would you mind being a guinea pig for that and giving your ack on the designate client branching? ^14:54
mugsiesmcginnis: sure, no problem14:56
smcginnismugsie: Thanks!14:57
*** armstrong has joined #openstack-release14:58
mugsiedone - just waiting for CI :)14:58
smcginnisI'll watch it through the gate to make sure it all works.14:58
smcginnisWorst case scenario if it does not is the ussuri job templates won't get updated to the victoria template automatically.14:58
*** zxiiro has joined #openstack-release15:05
*** slaweq has quit IRC15:06
*** vishalmanchanda has quit IRC15:09
*** armax has joined #openstack-release15:10
*** slaweq has joined #openstack-release15:21
openstackgerritdharmendra kushwaha proposed openstack/releases master: Release final python-tackerclient for ussuri
*** ykarel is now known as ykarel|away15:33
openstackgerritMerged openstack/releases master: Add stable/ussuri for python-designateclient
ttxgmann: yes. Just the page is just raw input, to be messaged into themes15:49
ttxnot my domain :)15:49
gmanni see.15:51
*** diablo_rojo has joined #openstack-release15:57
*** rpittau is now known as rpittau|afk15:59
smcginnis#startmeeting releaseteam16:00
openstackMeeting started Thu Apr  9 16:00:08 2020 UTC and is due to finish in 60 minutes.  The chair is smcginnis. Information about MeetBot at
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: ttx armstrong diablo_rojo, diablo_rojo_phon16:00
smcginnis#link Agenda16:00
smcginnisWe are at R-5 in the tracking etherpad.16:01
smcginnis#topic Review week tasks completion16:01
*** openstack changes topic to "Review week tasks completion (Meeting topic: releaseteam)"16:01
smcginnisProcessing remaining lib freeze patches16:01
smcginnisThat went surprisingly well. I think I did the last one on Sunday.16:01
smcginnisEmail ML for cycle-highlights.16:02
smcginnisI saw diablo_rojo got that out and patches have been coming in.16:02
smcginnisPropose autoreleases for cycle-with-intermediary client libraries which had commits that have not been included in a release16:02
smcginnisI did that one.16:02
smcginnisI did leave out stable branching with the plan to follow up later.16:02
smcginnisI wanted to get in the branching job updates to propose the victoria job template updates.16:03
smcginnisThat is now mostly working, one small update just proposed before this meeting.16:03
smcginnisI will follow up with patches to do the branching now that that is in place.16:03
smcginnisAny help getting those patches through once we get PTL ack is appreciated.16:04
smcginnisAt least nova has already communicated that it may not be until Monday due to waiting on patches to make their way through the gate.16:04
ttxbeen working through them16:04
smcginnisNext item -16:04
smcginnisEvaluate any libraries that did not have any change merged over the cycle to see if it is time to transition them to the independent release model.16:05
ttxwhere i didn't approve immediately that was because I would welcome second opinion16:05
openstackgerritMerged openstack/releases master: Release final python-ironic-inspector-client for ussuri
ttxsmcginnis: in some cases because the patch was modified and I want to make sure you still are ok with it16:05
smcginnisOK, I will try to take a look through if no one else gets to it by then.16:05
ttxso feel free to +2a your own patches if they have a +2 from me16:05
smcginnisDoesn't hurt to have more eyes on these patches now that we are getting to the freeze.16:05
smcginnisI did not check which libs didn't have any releases this cycle yet.16:06
smcginnisBeen waiting to get some of the final releases through first. Actually seems like maybe we should move this step in the process to the next week16:06
smcginnisThough I suppose we want to do it now to make sure the communication happens with the team and they are able to quickly do a release if they need to?16:07
ttxlet's see what that email said16:08
smcginnisI think actually with our proposing releases for everyone, most should not have gone this far without any releases.16:08
ttxit's not just libs16:08
ttxIt's actually not libs16:09
ttxThe goal is to warn people with enough lead time befroe RC1 week yes16:09
ttxSo on this week we warn those that haven't done any release16:09
smcginnisOK, I will make sure to look at that later today or in the morning tomorrow.16:09
ttxThen next week we warn those who did not make a *recetn* release16:09
ttxthat's why it's staged16:10
openstackgerritMerged openstack/releases master: Release final python-blazarclient for ussuri
smcginnisOK, makes sense.16:10
smcginnisNext - list c-w-i deliverables that have not been released.16:10
ttxI mean, we could totally skip this one, they would get caught next week. But it acts as a good reminder16:10
smcginnishberaud put together that list and tagged each team on the ML.16:10
smcginnisYeah, good to have as much warning as possible so they have time.16:11
ttxOh I'm confused16:11
ttxYou mean the lib release model change16:11
ttxline 53916:11
ttxyeah that could be moved to next week16:12
smcginnisI'll still plan on taking a look before then just to make sure I understand where things are with those.16:12
ttxbut usually they are caught this week16:12
ttxas the leftover of those we autoreleased16:12
ttxI mean, they will still be around next week :)16:13
smcginnisThe only ones I can think of would be anything that hadn't merged any changes at all this cycle. That should be very rare, but it's possible.16:13
ttxyes rare with python2 changes16:13
ttxlike probably none16:13
smcginnisI hope so.16:13
smcginnisOK, Friday, remind requirements team to freeze changes.16:13
smcginnisI will make sure to sync with prometheanfire on that.16:14
smcginnisAnd last task, send out the weekly email. On my todo list for tomorrow morning.16:14
ttxmodel at
smcginnis#topic Assign next weeks tasks16:15
*** openstack changes topic to "Assign next weeks tasks (Meeting topic: releaseteam)"16:15
smcginnisProcess remaining client releases. I think that can be all of ours.16:15
smcginnisFreeze all cycle-based lib releases.16:16
smcginnisAfter the current batch, we should have FFE requests going to the ML with the requirements PTL OK before we process any new lib releases.16:16
smcginnisSo I guess this is a task for everyone again. If you see any of those, please direct the requestor to follow that process.16:16
smcginnisPropose stable/$series branch creation for all client and non-client libraries that had not requested it at freeze time.16:17
smcginnisI will take that one.16:17
elodthis patch is not yet merged:
ttxyep, no more lib releases -- check16:17
elodI guess that is needed for this task16:17
elod(set up ussuri)16:18
smcginnisI think it must default to master or something.16:18
smcginnisBut might be good to ping the QA team to get that through now.16:18
elodOk, I'll ping some more cores from devstack-gate :)16:19
smcginniselod: Thanks!16:19
smcginnisHaha, and done. :)16:19
elodgmann: thanks :D16:19
smcginnisNext task - List cycle-with-intermediary deliverables that have not been refreshed in the last 2 months.16:19
smcginnisThis is the one that picks up services and anything else.16:19
smcginnisAnyone want to volunteer for that one?16:20
smcginnisOK, I will put my name down, but if anyone ends up with extra free time, feel free to grab it.16:21
smcginnisAnd send weekly email - I've got that one.16:21
smcginnis#topic Ironic release model16:21
*** openstack changes topic to "Ironic release model (Meeting topic: releaseteam)"16:21
smcginnisI thought I had a link to the mailing list thread in there, but I must have forgotten that.16:22
smcginnisHopefully you've all seen the discussion.16:22
smcginnisWondering ideas from the team on how we can meet that teams needs while still making sure we are able to communicate to downstream what to expect.16:22
smcginnisThey would like one release at the end of the cycle, but have the option to do more if needed.16:23
smcginnisSo basically, c-w-i, without being hassled to actually do intermediate releases if they don't want to.16:23
ttxI posted options on the etherpad16:23
ttxI think we can take two roads16:23
ttxOne is a minor change -- Evolve cycle-with-intermediary to allow 0+ releases.16:24
ttxIf none are produced, stable branch at last-available release16:24
prometheanfirefor the freeze, ya, though given gate's slowness there will likely be some straglers16:24
ttxThe other is a more dramatic change -- collapse with-rc and with-intermediary16:24
smcginnisprometheanfire: Yeah, that's likely. Thanks!16:24
ttxI like that it goves flexibility for teams to have a cycle with one release, then another with 416:25
ttxwithout us having to juggle release model changes16:25
ttxwhich is a waste of time for everyone16:25
ttxsmcginnis: could you expand on poor communication?16:25
ttx(personally I think we need to simplify)16:26
smcginnisWell, with the current release models, that commicates what and when to expect new code to be released and potentially packaged.16:26
ttxsmcginnis: we have that at final release though16:26
smcginnisUnder this proposal, it makes it harder for anyone creating packages to know whether to expect anything or not.16:26
ttxso we guarantee they will have somethign every 6 months16:26
openstackgerritColleen Murphy proposed openstack/releases master: Add keystone Ussuri cycle highlights
ttxbut not more16:26
ttxsmcginnis: true16:27
ttxI'm not sure they anticipate our moves though16:27
smcginnisYeah, probably not a big issue, but something we should be aware of.16:27
ttxBasically I think the ship has sailed for those cons16:27
smcginnisWe would just have to communicate what to expect under the new changes.16:27
ttxWe do not really drive best practices anymore with cycle-with-i16:27
ttxwe do not really need test releases anymore16:27
smcginnisI'm actually very in favor of simplifying things, especially with resources.16:28
ttxand nobody looks at release model before packaging16:28
ttxthe only thing we need to assess is the risk of drift16:28
ttxi.e. bitrot, making sure things actually work16:28
ttxbefore we include them16:28
ttxwith "0" being an option, there is potential for bitrot16:29
smcginnisOn our end, we can plan to do release-test releases at each milestone to test our automation.16:29
smcginnisBut that doesn't address issues on the project's end.16:29
smcginnisI'd be a little concerned getting rid of RC releases.16:30
ttxyes, to me that's the only potential drawback. With the current process we kinda force minimal activity16:30
smcginnisThat seems to be good practice to branch and control what then gets backported to the soon-to-be stable branch.16:30
ttxOh we'd keep that16:31
smcginnisWe could say if no releases by that point, then do an RC. Otherwise if there has been other releases done during the cycle, up to the teams if they just want to do one final release.16:31
ttxJust not .0rc1 etc16:31
ttxWe'd still have an early release and branch stable at that16:32
ttxlike we do for c-w-i currently16:32
smcginnisSo lib freeze, client freeze, service freeze dates?16:32
ttxthat's what we curently have (service freeze being the RC1 deadline really)16:32
ttxWe'd still advise teams to have a feature freeze and all16:33
ttxbut not enforce it with a release model16:33
ttxThat said, i suspect some teams actually like the cycle-with-rc model16:33
ttxin which case I guess we could keep it16:34
smcginnisIf things aren't quite ready, I think it would be good to give teams the option to have that service freeze date release be either an actual full release, or an RC release with the plan to follow up with a final release.16:34
ttxallowing 0+ in c-w-i will go a long way to eliminate release model change churn anyway16:34
ttxIt's really a topic for PTG16:34
smcginnisYeah, this would be a good one to sit down and talk through with a whiteboard.16:35
ttxvirtually or not16:35
smcginnisI don't think we can properly do it here in this meeting.16:35
ttxBut yes, good to statr thinking about it16:35
smcginnisThis is a good start though.16:35
smcginnisDefinitely something we should ponder for a little while before making any changes.16:35
*** udesale_ has quit IRC16:35
smcginnisLet's revisit this topic later. I think this has been a good start to get everyone thinking.16:36
smcginnisAnything else to say before I move along?16:36
*** evrardjp has quit IRC16:37
*** evrardjp has joined #openstack-release16:37
smcginnis#topic Stable branch name enforcement for independent deliverables16:38
*** openstack changes topic to "Stable branch name enforcement for independent deliverables (Meeting topic: releaseteam)"16:38
smcginnisttx: I might need your historical perspective on this.16:38
smcginnisBut to recap.16:38
smcginnisWe currently enforce branches need to have feature/ or stable/ prefixes.16:38
smcginnisAnd even in independent, we require that stable/X be the name of a series.16:39
smcginnisWhich seems odd to me for independent deliverables.16:39
ttxyes that is odd16:40
ttxsince they don;t have to have stable branches16:40
smcginnisSo for the ones that would like it, I think it makes sense to have them named stable/X, but I don't think we should enforce that X = a series name.16:40
openstackgerritMichał Dulko proposed openstack/releases master: Add kuryr-kubernetes cycle-highlights for Ussuri
smcginnisIf there isn't a historical reason that we wanted that, I can put it on my list to someday look at changing that validation code to allow independent to have more flexibility on those branch names.16:42
openstackgerritMichał Dulko proposed openstack/releases master: Add kuryr-kubernetes cycle-highlights for Ussuri
smcginnisIn the meantime, we do have the option to do what was done there and add specific deliverables to the list that are ignored.16:42
smcginnisAny other thoughts?16:43
ttxI'm surprised taht we do16:43
ttxswift has stable/2.0 things iirc16:43
fungiceilometer also did it before it was cool16:43
fungior that may have been gnocchi16:44
ttxsmcginnis: would be good to check why that check was added16:44
smcginnisIt looks like things have been refactored multiple times since it was added, so it will just take some digging to get to where and why it was added.16:44
smcginnisMy guess is multiple unrelated changes accidentally ended up making it being enforced for independent, when that was not the orginal intent.16:45
smcginnisBut I can try to figure that out.16:45
smcginnisI'll let everyone know if I find out more.16:46
smcginnis#topic Review countdown email16:46
*** openstack changes topic to "Review countdown email (Meeting topic: releaseteam)"16:46
smcginnis#link Countdown draft16:46
*** dtantsur is now known as dtantsur|afk16:46
smcginnisRe-reading the draft, nothing stands out to me.16:48
openstackgerritSlawek Kaplonski proposed openstack/releases master: Add Ussuri cycle highlights for Neutron
smcginnisIf anyone finds anything wrong, please update in the next ~18 hours or so.16:48
smcginnisI will send it out tomorrow.16:49
diablo_rojoWill do.16:49
smcginnis#topic AOB16:49
*** openstack changes topic to "AOB (Meeting topic: releaseteam)"16:49
ttxthat's the wrong email16:50
ttxThe right one starts with "We just passed feature freeze!"16:51
smcginnisShoot, you are right.16:51
ttxnot teh week after16:51
smcginnisOK, updated. Please take a look at the new content.16:56
smcginnisThat's all I had. Anything else before we close?16:56
smcginnisOK, thanks everyone for all your help and work on the release team.16:57
*** openstack changes topic to "OpenStack Release Managers office - Come here to discuss how to release OpenStack components - Logged at"16:57
openstackMeeting ended Thu Apr  9 16:57:28 2020 UTC.  Information about MeetBot at . (v 0.1.4)16:57
openstackMinutes (text):
ttxThanks smcginnis !16:59
fungididn't want to interrupt the meeting, but did anything ever come of the request to delete the stable/stein branch from tripleo-ansible?17:00
smcginnisOh, I forgot to add that to the agenda.17:02
fungithe only explanation they'd give was that it was "breaking their ci" and they didn't want the stable/train branch deleted just stable/stein17:02
smcginnisttx: I think I pinged you in channel. See any reason to keep that deliverable file around if there wasn't really anything part of the stein coordinated release?17:02
fungii told them to make sure the branch wasn't listed in the releases repo so that automation wouldn't recreate it later17:02
smcginnisYeah, there's a patch up to remove it from the deliverable file, but I'm thinking we should just drop the entire file so the 0.1.0 release isn't listed on the releases site.17:03
smcginnisSince it sounds like it didn't actually contain anything of value.17:03
smcginnisfungi: Unrelated, but I'd love your eyes on
smcginnisLooks like that is all working, but it picked up a tox.ini~ file with the way it was being done before.17:04
fungii looked in their stable/stein branch and it seemed to have ansible content, so i was unsure what they meant by nothing of value17:04
smcginnisHmm, not sure.17:04
*** ricolin has quit IRC17:04
*** sshnaidm is now known as sshnaidm|afk17:12
openstackgerritBalazs Gibizer proposed openstack/releases master: nova: ussuri cycle highlights
evrardjpI am a little late to the game, but a few topics of today's meeting seem related to the Idea I wanted to propose. I am still refactoring it.17:20
evrardjpnews soon.17:20
*** priteau has quit IRC17:22
smcginnisevrardjp: OK, great!17:32
openstackgerritSean McGinnis proposed openstack/releases master: Branch stable/ussuri for oslo deliverables
smcginnisbnemec: Let me know if you are good with that ^17:46
*** mlavalle has joined #openstack-release17:52
*** sshnaidm|afk is now known as sshnaidm|off18:02
*** markmcclain has quit IRC18:27
*** markmcclain has joined #openstack-release18:29
*** mgoddard has joined #openstack-release18:46
*** e0ne has quit IRC18:49
*** e0ne has joined #openstack-release18:55
*** spsurya_ has quit IRC19:08
*** e0ne has quit IRC19:12
*** diablo_rojo has quit IRC19:16
*** diablo_rojo has joined #openstack-release19:17
openstackgerritSlawek Kaplonski proposed openstack/releases master: Add Ussuri cycle highlights for Neutron
*** markmcclain has quit IRC19:22
*** markmcclain has joined #openstack-release19:24
openstackgerritSean McGinnis proposed openstack/releases master: Add blazar lib stable branches
gmannsmcginnis: evrardjp ttx need release team input on oslo.policy FFE -
gmannthis is needed to ship the RBAC new defaults features for Nova and much helpful for operators to adopt the new policy system.19:52
smcginnisgmann: Is nova actually ready to start using that?19:52
gmannsmcginnis: yeah, once we have oslo release -
gmannand other new flag is for operators to switch to new defaults roles19:54
smcginnisIt's past both oslo freeze and non-client lib freeze. Seems a little too late at this point to introduce it. But if bnemec is OK with it on the oslo side, the impact should only be on nova at this point.19:54
*** priteau has joined #openstack-release19:55
gmannbnemec is ok for this, mentioned in ML.19:56
smcginnisShould also get prometheanfire to respond since it is past the requirements freeze for non-client lib, but sounds like it should be fine.19:57
bnemecYeah, the timing is not great, but it's something that came up late that is specific to work done this cycle.19:57
smcginnisSince we did make it a 1.0, I suppose it would be nice to have someone able to use it this cycle.19:57
*** armstrong has quit IRC19:57
gmannyeah, we thought of warning things are ok but those are too many in logs and too hard for operators to understand those.20:00
*** priteau has quit IRC20:05
gmannprometheanfire: I requested this oslo.policy FFE, need your opinion from requirement side as req freeze already done for lib -
openstackgerritMichael Johnson proposed openstack/releases master: Release python-octaviaclient 2.0.1 for ussuri
smcginnisbnemec, gmann, prometheanfire: I responded on the ML.20:17
smcginnisThere are a lot of projects with oslo.policy as a dependency. I was actually thinking of oslo.limit earlier.20:18
smcginnisSo I'd say if we are very confident this isn't going to introduce any other breakage, it should be OK.20:18
smcginnisBut we should be very cautious.20:18
bnemecIt shouldn't change the existing behavior except for projects that opt in or if a deployer explicitly sets the new config opt.20:21
smcginnisOK, that sounds safe then.20:22
gmannyeah and those flag are default to false means no change in old behavior20:22
*** jtomasek has quit IRC20:41
*** markmcclain has quit IRC20:42
*** markmcclain has joined #openstack-release20:42
openstackgerritMerged openstack/releases master: Release ironic-ui 3.5.5 for Train
openstackgerritMerged openstack/releases master: tripleo ussuri milestone 3 release
openstackgerritMerged openstack/releases master: Release final python-solumclient for ussuri
openstackgerritMerged openstack/releases master: Release final python-ironicclient for ussuri
openstackgerritMerged openstack/releases master: Release final python-watcherclient for ussuri
openstackgerritMerged openstack/releases master: Fix formatting issues in R-2 week
openstackgerritMerged openstack/releases master: xstatic packages: first release via the releases repo
*** hberaud has quit IRC21:25
*** hberaud has joined #openstack-release21:26
openstackgerritMerged openstack/releases master: Add blazar lib stable branches
*** slaweq has quit IRC22:14
*** slaweq has joined #openstack-release22:15
*** slaweq has quit IRC22:20
*** tosky has quit IRC23:08
*** diablo_rojo has quit IRC23:11

Generated by 2.15.3 by Marius Gedminas - find it at!