15:02:00 <amotoki> #startmeeting horizon
15:02:01 <openstack> Meeting started Wed Jan 22 15:02:00 2020 UTC and is due to finish in 60 minutes.  The chair is amotoki. Information about MeetBot at http://wiki.debian.org/MeetBot.
15:02:02 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
15:02:04 <openstack> The meeting name has been set to 'horizon'
15:02:05 <e0ne> hi
15:02:09 <vishalmanchanda> hi
15:02:21 <tmazur> hi
15:03:13 <amotoki> let's start
15:03:21 <amotoki> the agenda is found at https://etherpad.openstack.org/p/horizon-release-priorities
15:03:27 <amotoki> #topic notices/annoucements
15:03:59 <amotoki> I proposed stable releases for rocky, stein and train
15:04:11 <amotoki> they will be released soon
15:04:14 <e0ne> great!
15:04:23 <vishalmanchanda> nice.
15:05:02 <amotoki> any other announcements?
15:05:39 <vishalmanchanda> nothing
15:05:45 <vishalmanchanda> from my side
15:05:48 <amotoki> move on
15:05:52 <amotoki> #topic General Priorities
15:06:13 <amotoki> Ussuri-2 milestone is the week of Feb 10
15:06:30 <amotoki> so I would like to check statuses of the general priorities.
15:06:51 <amotoki> you can find them around L.26 of the etherpad https://etherpad.openstack.org/p/horizon-release-priorities
15:07:17 <amotoki> first one is mine. Catch up the new policy mechanism
15:08:08 <amotoki> I am implementing it. perhaps it takes one week but I believe we can land it by milestone-3 at latest.
15:08:22 <amotoki> the second one "Bump and clean up Django versions" is almost completed.
15:08:34 <vishalmanchanda> yeah.
15:08:46 <amotoki> I don't think we need to cover it in the meeting.
15:09:06 <vishalmanchanda> I am working on third.
15:09:06 <amotoki> I've also sent a notice to the mailing list this week.
15:09:18 <amotoki> the third one is "Error message refactoring".
15:09:49 <vishalmanchanda> Right now i have write some code for https://blueprints.launchpad.net/horizon/+spec/cinder-user-facing-messages
15:10:08 <vishalmanchanda> will push it soon once completed.
15:10:21 <amotoki> vishalmanchanda: it is not directly related to the third one.
15:10:35 <amotoki> is my understanding right?
15:10:40 <vishalmanchanda> yeah
15:10:40 <e0ne> amotoki: +1
15:10:47 <amotoki> it is a part of feature gaps.
15:10:50 <vishalmanchanda> there are 2 bps
15:11:17 <vishalmanchanda> https://blueprints.launchpad.net/horizon/+spec/refactor-error-messages
15:11:49 <amotoki> cinder-user-facing-message is a blueprint related to feature gaps. the blueprint refactor-error-messages is only related to the third one.
15:12:16 <vishalmanchanda> ok.
15:12:42 <amotoki> we don't necessarily discourage you to work on the cinder-user-facing-mesasge
15:12:56 <amotoki> I just woudl like to clarify what is categorized into whta.
15:13:04 <amotoki> *what.
15:13:31 <vishalmanchanda> ok. gotcha.
15:13:50 <amotoki> moving on the medium priorities
15:14:09 <amotoki> the first one is xstatic updates
15:14:24 <amotoki> I see one xstatic update from rdopiera this week
15:14:24 <e0ne> there are some patched from rdopiera
15:14:45 <e0ne> #link https://review.opendev.org/#/q/(project:%5Eopenstack/xstatic-.*%20status:open)%20OR%20(project:%5Ex/xstatic-.*%20status:open)
15:15:32 <amotoki> I missed other onces, thanks.
15:15:37 <e0ne> I'm courious if we can test these patches on gates with integration tests
15:15:54 <amotoki> I thought the same thing
15:16:17 <amotoki> what is the good way to test them before releasing them?
15:16:30 <amotoki> rdopiera: you around?
15:17:02 <e0ne> it's pretty risky to release them without testing
15:17:29 <amotoki> exactly
15:18:39 <amotoki> I have another question: is x/xstatic-angular-fileupload related to us?
15:19:06 <e0ne> I thinks, yes
15:19:07 <e0ne> https://github.com/openstack/horizon/blob/master/lower-constraints.txt#L137
15:19:30 <e0ne> I don't  why it's not in openstack namespace
15:19:40 <amotoki> yeah, it looks like related to us as we have XStatic-Angular-FileUpload in our requirements
15:19:52 <amotoki> but it looks maintained separately
15:22:08 <rdopiera> amotoki: sorry, yes
15:22:35 <amotoki> rdopiera: welcome. we are discussing xstatic updates now.
15:22:48 <rdopiera> amotoki: well, I'm doing a smoke test by installing them in the venv in master and looking for a place where they are used
15:23:13 <rdopiera> amotoki: and making sure it still works and there are no errors in the console
15:23:51 <rdopiera> it's not perfect, but it's something
15:24:15 <amotoki> rdopiera: yeah, I think local testing is the only thing we can do now.
15:24:37 <amotoki> potentially we can propose a gate with the master branch of xstatic repositories.
15:24:53 <e0ne> rdopiera: could you please run integration tests locally with all updated package installed?
15:25:27 <e0ne> amotoki: +1 to make it in a experimental queue
15:25:41 <amotoki> our integration test coverage is not so good, so it might not work well for this purpose, but it is better than nothing.
15:25:51 <e0ne> amotoki: +1
15:25:57 <rdopiera> e0ne: I will try
15:26:04 <e0ne> rdopiera: thanks
15:26:25 <amotoki> rdopiera: thanks
15:26:56 <amotoki> I will prepare an experimental job with xstatic repos so that we can test it.
15:27:08 <e0ne> ok
15:27:38 <amotoki> rdopiera: another thing is x/xstatic-angular-fileupload. do you know we can release it?
15:28:07 <amotoki> it is not under the openstack governance, so I guess it was released manually.
15:28:36 <amotoki> it seems nobody here knows why it is in the x namespace.
15:28:48 <rdopiera> amotoki: it's owned by Rob on pypi, I assume he added openstack user ot it
15:29:02 <rdopiera> https://pypi.org/project/XStatic-Angular-FileUpload/
15:29:09 <rdopiera> he did
15:29:17 <rdopiera> openstackci is there in maintainers
15:29:19 <amotoki> yeah, I see it too.
15:30:16 <rdopiera> probably slipped through the cracks at some point
15:30:20 <amotoki> we seem to need to check whether we can still use zuul jobs to publish it to PyPI in zuulv3 era.
15:30:48 <rdopiera> that is going to be another fun part
15:31:49 <amotoki> and we might need to consider inclusion of xstatic-angular-fileupload repo into the horizon governance.
15:32:18 <e0ne> amotoki: sounds reasonable to me
15:33:49 <amotoki> we have several action items now. the priorities look like the order we discussed. let's tackle them one by one.
15:34:03 <amotoki> I will add note to the etherpad after the meeting.
15:34:28 <amotoki> anything to discuss on xstatic?
15:35:14 <rdopiera> I'm still working on it, probably will have something next week to discuss, but for now no
15:35:45 <amotoki> rdopiera: thanks for leading it. let's continue.
15:36:09 <amotoki> the second medium one is "ini-based-configuration".
15:36:45 <amotoki> it's mine but there is no good progress as the policy stuff is prioritized
15:36:53 <amotoki> it is still in my todo list though.
15:37:39 <amotoki> the last one is "Chinese translation handling"
15:38:11 <amotoki> e0ne: any update?
15:38:22 <e0ne> I didn't have update on it:(. I'm going to test currect master to see what is going this week
15:38:48 <amotoki> thanks
15:39:28 <amotoki> perhaps we also need to check LOCALES_PATHS issue raised by you and Gloria is resolved with the new chinese lang codes.
15:39:44 <e0ne> +1
15:40:40 <amotoki> It needs a coordination with the i18n team, so I think we need to clarify steps.
15:41:22 <amotoki> I think the first step is we test it with the new lang codes.
15:41:35 <e0ne> agree
15:41:39 <e0ne> agreed
15:41:43 <amotoki> and confirm changing the lang codes solves what would like to solve.
15:42:42 <e0ne> that's what I'm going to test
15:42:58 <amotoki> I can test the new lang codes but I cannot check the LOCALES_PATH issue as I failed to repro it :(
15:43:11 <e0ne> I'll do it
15:43:23 <amotoki> so I depend e0ne on it
15:43:25 <amotoki> thanks
15:44:14 <amotoki> we've covered all priority items
15:44:38 <amotoki> it was a good discussion. I will add notes on them to the etherpad.
15:44:50 <e0ne> amotoki: thanks!
15:45:05 <amotoki> #topic On-Demand Agenda
15:45:19 <amotoki> we focus on the priority items in this meeting.
15:45:34 <amotoki> All other stuffs can be covered by this topic.
15:45:45 <amotoki> is there anything to discuss?
15:45:52 <e0ne> nothing from me
15:47:15 <amotoki> I just would like to remind you to review +2'ed changes
15:47:28 <amotoki> they were not reviewed one week after +2'ed.
15:47:44 <e0ne> will do it after the meeting
15:47:59 <amotoki> thanks
15:48:09 <e0ne> amotoki, rdopiera: thanks for reviewing my backports!
15:48:59 <amotoki> e0ne: one question on your policy backport
15:49:07 <e0ne> sure
15:49:18 <amotoki> in case of maintained versions, we can raise a notice by incrementing a minor version
15:49:28 <amotoki> but how about EM branches?
15:49:42 <amotoki> do we agree a release note is enough?
15:49:50 <e0ne> AFAIK, we don't do releases for EM
15:50:15 <amotoki> e0ne: yeah, we no longer cut releases for EM.
15:50:36 <e0ne> it means we shouldn't do version bump
15:52:18 <amotoki> IMHO it is enough with a release note as the proposed one matches the glance policy file we have in their stable branches.
15:52:29 <amotoki> I just wanna double check.
15:52:40 <e0ne> +1
15:53:18 <amotoki> that's all from my side.
15:54:00 <amotoki> let's wrap up the meeting.
15:54:06 <amotoki> thanks for joining, all!
15:54:12 <amotoki> #endmeeting