15:04:54 #startmeeting horizon 15:04:54 Meeting started Wed Dec 18 15:04:54 2019 UTC and is due to finish in 60 minutes. The chair is amotoki. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:04:55 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 15:04:57 The meeting name has been set to 'horizon' 15:05:05 amotoki: hi. 15:05:20 vishalmanchanda: hi 15:05:40 e0ne cannot join today 15:05:52 ok. 15:05:59 let's wait for a while 15:06:04 yeah. 15:07:55 i think we can start. 15:08:01 yes 15:08:13 today's meeting would be short 15:08:21 #topic notices 15:08:49 I have nothing special to be announced here, but 15:09:03 I would like to discuss meetings in the upcoming weeks. 15:09:12 yeah fine. 15:09:23 we can skip it. 15:09:30 We will be in Christmas and new year holidays. 15:09:46 How about cancelling the next two meetings? 15:09:57 yeah 15:10:00 we can resume it at Jan 8 15:10:12 +1. 15:10:44 Ivan also +1'ed the idea. let's skip them 15:10:58 I will send a notice to the ML 15:11:04 cool. 15:11:40 #topic Community Goals 15:12:24 I see only one goal merged in the TC repo. 15:12:39 py27 will be completed soon. 15:13:01 moving on 15:13:15 #topic Django 2.2 support 15:13:56 we broke the docs job in some horizon plugins after bumping upper-constraints to 2.2 15:14:13 but horizon 17.1.0 release has solved it. 15:14:56 yeah. 15:15:06 we should be more careful... 15:15:19 we need to discuss upcap of Django vs Django<3 cap (major version cap), but it can be deferred 15:15:57 there is one problem related to Django 2.2 15:15:59 https://bugs.launchpad.net/horizon/+bug/1856540 15:15:59 Launchpad bug 1856540 in OpenStack Dashboard (Horizon) "djnago-babel is not compatible with Django 2.2" [High,New] 15:16:12 translation string extraction is broken now 15:16:57 I summarized what I checked in the bug 15:17:05 so what we gonna do now? 15:17:50 I just contacted one of the project maintainers I know. 15:18:03 I got a reply but there is no good news 15:18:30 it will take time for coordination at the moment. 15:19:18 there seems several options but there seems no silver bullet. 15:19:47 hmm. 15:20:18 Can we drop django1.11 support now? 15:20:59 current django-babel works with Django 1.11 only..... 15:21:43 if we run string extraction with Django 1.11, we can continue to update translation strings until we find a solution. 15:22:14 it is just applied to the translation update and extraction scripts in the zuul jobs. 15:23:33 so i have to wait till we find out how to fix this. 15:23:41 back to "drop django 1.11 support", are you sure horizon and plugins work with Django 2.2 fine? 15:24:25 I am not sure that only one or two weeks after u-c bump is enough time period. 15:25:10 ok. we can wait and drop it in mid January. 15:25:14 or later. 15:26:32 you are usually watching most? horizon plugin reviews. Are you running most of such pluigns in your env? 15:27:07 I usually run plugins when I review them, so I am asking it to you. 15:27:48 I only reviews community goals patches like drop and some trivial changes. 15:28:16 olay 15:28:22 I have just cloned all of horizon plugins in my env. 15:28:31 not deployed. 15:29:07 I have deployed few of them like heat, cloudkitty and tacker... 15:30:50 that would be fine. 15:31:11 it is nice if we try some of plugins which we know :) 15:31:54 +1. 15:33:17 so, the summary is: (1) Wait to drop django 1.11 support till the new yeat (2) continue to explore django-babel issue 15:34:00 yeah. 15:34:12 note that django 1.11 drop includes cleanup of unnecessary django version check. it applies to at least the horizon repo. 15:34:33 I will also explore how to fix django-babel issue. 15:35:21 yeah we can also drop django2.1 version entry from tox.ini. 15:35:38 2.0? 15:36:20 https://github.com/openstack/horizon/blob/master/tox.ini#L28 15:37:34 yeah 2.0 15:38:06 I think we can drop all of them: dj111, dj21. theoretically py3-dj22 can be dropped but perhaps it requires zuul.yaml change together. 15:39:31 horizon-non-primary-django-jobs runs horizon-openstack-tox-python3-django111 and horizon-openstack-tox-python3-django22 15:39:56 so we must explore the order of changes not to break the plugin gates. 15:40:55 yeah we need to be careful. 15:41:47 anything to discuss on django related topic? 15:41:58 nothing. 15:42:11 #topic on-demand agenda 15:42:13 too much of django. 15:42:35 I don't see the bug and review topics. 15:42:46 me too. 15:43:00 we can wrap the meeting. 15:43:45 "I don't see the bug and review topics." looks weird :( but I have nothing to discuss on them :) 15:44:05 we can save 15mins 15:44:11 thanks for joining 15:44:13 :) 15:44:21 #endmeeting