15:00:07 #startmeeting horizon 15:00:07 Meeting started Wed Oct 27 15:00:07 2021 UTC and is due to finish in 60 minutes. The chair is vishalmanchanda. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:00:07 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 15:00:07 The meeting name has been set to 'horizon' 15:01:03 hi anyone around for horizon meeting? 15:01:35 hi 15:02:32 let's wait for few minutes if more people join us. 15:03:47 tmazur: e0ne : rdopiera : around? 15:04:14 o/ 15:04:45 ok Let's start the meeting. 15:05:27 First of all, thank you all for joining the PTG discussion. It's good to see you all. 15:05:44 In case if you are not able to join or missed any topic discussion please take a look at ptg eherpad 15:05:52 https://etherpad.opendev.org/p/horizon-yoga-ptg 15:06:04 #topic Notices 15:06:31 few notices from my side for this week. 15:06:48 This week is R-22, Yoga-1 milestone is R-19(Nov 15 - Nov 19) 15:06:51 do we have assignees for priority items? Or are they just listed? 15:06:58 Yoga Schedule https://releases.openstack.org/yoga/schedule.html 15:07:12 amotoki: I will come to that point. 15:08:00 I have cut first release for Yoga cycle so that all horizon plugins can consume django upper bump change and patch is merged today https://review.opendev.org/c/openstack/releases/+/815334 15:08:32 I have updated our release priority etherpad and priority items for Yoga cycle. 15:08:50 So please a look at etherpad and any other priority if I missed any. 15:09:03 vishalmanchanda: okay. we are now in the "Notices" topic, if more discussion is needed, let's cover later. 15:09:11 Also, If you are working on any task mentioned on the etherpad, please add your name so we ask the status throughout the cycle. 15:09:39 vishalmanchanda: where in which etherpad do you mean? 15:10:23 the PTG etherpad? the priority etherpad? or something other? 15:10:31 https://etherpad.opendev.org/p/horizon-release-priorities 15:10:47 amotoki: release priority etherpad 15:12:24 I have also updated the Weekly meeting Section in the release priority etherpad, so if you have topic to discuss please add it there. 15:13:35 that's all announcement from my side for this week, if anyone have any announcement to make go ahead. 15:14:39 moving to next topic 15:14:54 #topic Django 3.2 support 15:15:17 patch to update upper constraints to use new horizon release is up https://review.opendev.org/c/openstack/requirements/+/815628 15:15:34 sorry for being late 15:16:18 once above patch is merged I will purpose a patch to bump minimum django version to 3.2 in horizon and then cut a new release for horizon. 15:17:06 I was also thinking if I should drop code for Launch instance python based implementation and django 2 support together so we not have to cut two releases. 15:17:42 do we want to give some time to horizon plugins to bump the lower bound or want a new horizon release to force them to update their l-c? 15:18:29 the gray zone is whetherr we need a major version bump when we change the lower bound of Django. 15:20:14 I am not sure if horizon plugins are much active and they are going bump there lower bound. 15:21:33 You mean if we drop Django 2 support then we didn't need a major version bump. 15:22:23 vishalmanchanda: regrading the major version, yes. it is really a grayzone. 15:22:42 I cannot say which is better 15:22:45 but if I look at prometheanfire comment on my patch https://review.opendev.org/c/openstack/requirements/+/815096 it say we need to do a major version bump. 15:24:23 yeah, a major version bump should work. what I am not sure is that the semantic versioning requires the major version bump when our (major) dependency are changed 15:24:48 if we can do other changes which requires a major version change, it would be really nice to do them together 15:25:25 so it is nice to have the removal of django Launch instance form in a same release 15:26:02 amotoki: ok I will try to push a patch by next week. 15:26:04 it is not specific to Django 2 vs 3. it can happen every Django LTS change :-( 15:26:58 moving to next topic 15:27:06 IMO I don't want to see a major version bump more than once in a release :_ 15:27:08 :) 15:27:22 amotoki: sure. 15:27:46 #topic Bug deputy report 15:28:02 We have 3 new bugs reported from last 2 weeks. 15:29:06 one of them is already triaged 2 needs to be verify https://bugs.launchpad.net/horizon/+bug/1947295 and https://bugs.launchpad.net/horizon/+bug/1946534 15:29:42 I will take a look at these bug tomorrow. 15:29:58 regarding the first one https://bugs.launchpad.net/horizon/+bug/1947295, the bug author found a solution. 15:30:47 it looks like that the package they use still uses wsgi/django.wsgi unfortunately 15:30:54 I think it is a bug of the package. 15:31:10 I am not sure such kind of thing should be covered by the upstream team. 15:31:49 amotoki: yeah, thanks feel free to add your comment there. 15:32:27 will do if I don't forget it :p 15:33:12 amotoki: thanks or I will mark it as incomplete as it is not horizon bug. 15:33:54 where is a good place to report a bug on such package? 15:34:50 I don't know maybe zigo know more about that. 15:34:53 I only have an experience on ubuntu cloud archive as an OpenStack operator, so I don't know where is a right place for RPM package 15:34:57 Vadym Markov proposed openstack/horizon master: Fix for "Resize instance" button https://review.opendev.org/c/openstack/horizon/+/808102 15:35:15 ok moving to next topic 15:35:25 Vadym Markov proposed openstack/horizon master: WIP Fix for "Resize instance" button https://review.opendev.org/c/openstack/horizon/+/808102 15:35:42 #topic On demand agenda 15:35:48 vishalmanchanda: What package? 15:35:53 vishalmanchanda: I don't think zigo is the right contact as he is a Debian package maintainers 15:35:59 Do we have any other topic to discuss. 15:36:01 o/ 15:36:35 zigo: sorry for bugging you. we are just wonder where is the right place to file a bug on a wrong configuration of RPM package of horizon. 15:36:40 zigo: we are just discussing a bug and I thought maybe you know where to report it. 15:36:55 I'm not the right person for RPM stuff ... :) 15:37:10 zigo: perhaps you are not the right person as you are a debian guy and I know it well. 15:37:23 Indeed. 15:37:35 I suppose that would be me 15:37:43 cool. 15:39:11 rdopiera: where should we report a bug? RDO? 15:39:17 amotoki: yes 15:39:52 rdopiera: thanks. 15:40:05 as upstream, it is better to forward a bug on packaging rather than marking such as Incomplete/Invalid. 15:40:46 oh I forgot to mention I will not be able to host the next weekly meeting as it's the holiday for me. 15:41:07 I actually think he's following the wrong guide 15:41:08 Can someone else chair it or we can skip? 15:41:23 he didn't mention which one he followed, other than it is "official" 15:41:46 I think we can skip. I believe you discussed a lot in the PTG already. 15:42:43 rdopiera: We can ask him about the steps how to reproduce it and let' see. 15:42:48 rdopiera: good point. let's clarify it 15:44:36 ok I will send a mail on open-discuss about skipping next weekly meeting in case noone come forward to chair it. 15:45:11 I think we can end this meeting if we have nothing else to discuss. 15:46:30 Also, please add your name if you are going to work on any task mentioned in release etherpad for yoga cycle 15:46:52 https://etherpad.opendev.org/p/horizon-release-priorities line 6 15:48:20 Thanks everyone for joining! 15:48:33 #endmeeting