15:02:31 <e0ne> #startmeeting horizon
15:02:33 <openstack> Meeting started Wed Apr  3 15:02:31 2019 UTC and is due to finish in 60 minutes.  The chair is e0ne. Information about MeetBot at http://wiki.debian.org/MeetBot.
15:02:34 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
15:02:37 <openstack> The meeting name has been set to 'horizon'
15:02:53 <e0ne> hi. is anybody around for horizon meeting?
15:03:06 <vishalmanchanda> e0ne: hi
15:04:27 <amotoki> hi
15:04:49 <rdopiera> hi
15:06:13 <e0ne> seems we've got good team to start
15:06:59 <e0ne> #topic Stein release
15:07:27 <e0ne> we need to cut the final RC this week
15:07:29 <e0ne> #link https://releases.openstack.org/stein/schedule.html
15:07:49 <e0ne> here is our bug list:
15:07:53 <e0ne> #link https://launchpad.net/horizon/+milestone/stein-rc2
15:08:24 <e0ne> amotoki has a valid argument against sync policies now
15:08:26 <e0ne> #link https://review.openstack.org/#/c/648631/2
15:10:12 <e0ne> amotoki: do you suggest to not sync only keystone policies?
15:11:58 <amotoki> e0ne: I think that's a possible solution.
15:12:24 <amotoki> e0ne: we can discuss how to handle the new keystone policies later.
15:12:28 <e0ne> I tried to test as much, as I can but I can't be sure that nothing is broken
15:13:02 <amotoki> perhaps we need to discuss it with keystone team including the motivation of this chagne.
15:13:09 <e0ne> amotoki: +1
15:13:26 <amotoki> I know there is the ongoing effort on system-scope and reader role
15:13:48 <e0ne> in scope of Stein release, let's skip keystone policy sync for now
15:14:08 <e0ne> amotoki: are you OK with neutron policies sync?
15:14:19 <amotoki> I am okay with it.
15:14:28 <rdopiera> users are going to sync the policy files anyways, if they make any changes, because all guides tell them to
15:14:36 <amotoki> do we need some note in the release notes?
15:15:12 <amotoki> rdopiera: good point. totally agree
15:15:34 <e0ne> amotoki: I'll update my patch with release notes info right after the meeting
15:16:19 <e0ne> rdopiera, amotoki: probably, we can sync it to stable/stein a bit later after release
15:16:43 <e0ne> rdopiera, amotoki: to keep consistency and have more time to test such changes
15:21:30 <e0ne> are we agree with this plan?
15:22:28 <amotoki> I have a bit concern on the plan of backport. does it mean the change in the default policies?
15:22:44 <amotoki> I am not sure this is a valid backport or not.
15:23:11 <e0ne> amotoki: I think we can decide it later once new policies will be in master
15:23:28 <e0ne> amotoki: we should not break anything
15:23:37 <amotoki> yes
15:24:46 <e0ne> if we can backport policies without breaking default behaviour, propably it will be ok to backport them
15:25:10 <e0ne> but it's pretty risky, so we need to test them in master first
15:25:56 <e0ne> I'm not fan of backporting such things
15:26:52 <e0ne> open patches for stable/stein
15:26:57 <e0ne> #link https://review.openstack.org/#/q/project:openstack/horizon+branch:stable/stein+status:open
15:27:42 <e0ne> I would like to have at least https://review.openstack.org/648909 and https://review.openstack.org/648152 before RC2
15:28:20 <e0ne> AFAIR, all core teams should have +2 on stable/stein until final RC or release are published
15:29:16 <e0ne> we'll have final RC (RC2 in our case) this Thursday and Stein release will be available next week
15:30:09 <e0ne> also, I'll propose policies sync to stable/stain once it will be merged in master
15:31:42 <e0ne> do you have anything else related to Stein release?
15:33:54 <e0ne> let's move to the next topic
15:34:02 <e0ne> #topic Notices
15:34:52 <e0ne> PTG planning
15:35:09 <e0ne> We'll have half of day on May, 2nd
15:35:27 <e0ne> please, add you name and topics you would like to discuss into the etherpad
15:35:29 <e0ne> #link https://etherpad.openstack.org/p/horizon-train-ptg
15:38:35 <e0ne> I was disconnected due to the networkinng issues:(
15:38:41 <e0ne> I proposed to add vishalmanchanda to the horizon-core team today
15:38:42 <e0ne> #link http://lists.openstack.org/pipermail/openstack-discuss/2019-April/004502.html
15:38:56 <e0ne> vishalmanchanda: thank you for your contributions
15:39:33 <e0ne> that's all updates I have this week
15:40:15 <e0ne> #topic Open Discussion
15:40:18 <vishalmanchanda> e0ne: thanks  for nominating me.
15:40:37 <e0ne> anything else to discuss today?
15:41:14 <vishalmanchanda> amotoki: e0ne rdopiera : I need your opinion on this patch https://review.openstack.org/#/c/649401/ . Since we have move to bionic,So we don't need nodejs4 job anymore as it's running on xenial.
15:42:40 <amotoki> vishalmanchanda: IMHO the change should happen gradually. first we add nodejs10 jobs and then drop nodejs4 after confirming nodejs10 jobs are stable.
15:42:53 <e0ne> I'm OK with it once https://review.openstack.org/#/c/648315/ will be running
15:42:58 <e0ne> amotoki: +1
15:43:24 <amotoki> vishalmanchanda: I am not familiar with this area, so input from folks who are familiar with this area would be apprciated.
15:43:30 <amotoki> *appreciated
15:43:37 <vishalmanchanda> amotoki: +1, agreed.
15:47:58 <e0ne> looks like we've done for this week
15:48:14 <e0ne> thanks everybody for your contributions! see you next week
15:48:33 <vishalmanchanda> bye all...
15:48:37 <e0ne> #endmeeting