15:03:05 <e0ne> #startmeeting horizon
15:03:05 <openstack> Meeting started Wed Mar 24 15:03:05 2021 UTC and is due to finish in 60 minutes.  The chair is e0ne. Information about MeetBot at http://wiki.debian.org/MeetBot.
15:03:06 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
15:03:09 <openstack> The meeting name has been set to 'horizon'
15:03:37 <e0ne> hi everybody
15:03:46 <vishalmanchanda> hi.
15:03:49 <tmazur> o/
15:04:28 <rdopiera> o/
15:05:25 <amotoki> hi
15:05:34 <e0ne> let's start
15:05:40 <e0ne> #topic Notices
15:06:44 <e0ne> tomorrow we'll reach Wallaby RC1 milestone
15:06:50 <e0ne> #link https://releases.openstack.org/wallaby/schedule.html
15:07:36 <e0ne> probably, we'll cut a horizon release  and create stable/wallaby branch
15:10:43 <e0ne> horizon uses other release model, it's not required for us to do it tomorrow
15:12:34 <e0ne> that's all updates from me
15:12:58 <e0ne> oh.. almost forgot to mention lower-requirements job update
15:13:22 <e0ne> TC decided that it's optional now
15:14:20 <amotoki> so, what's our decision?
15:14:28 <e0ne> so we can drop it in a next release
15:14:39 <e0ne> I'm fine with it until it works :)
15:14:55 <amotoki> if we drop l-c, how can we ensure lower requirements in (test-)requirements.txt?
15:15:06 <amotoki> that's my only question.
15:15:13 * e0ne remembers breakage with new pip20
15:15:47 <amotoki> the resolver enhanment in pip20 was a big change, so it is not surprising though.
15:16:23 <amotoki> I am okay if you can ensure lower requirements in (test-)requirements.txt. If so I am fine with l-c job drop.
15:18:09 <e0ne> does somebody uses l-c in production? AFAK, most people prefer upper-constraints
15:19:27 <amotoki> so what does our min ver in requirements.txt mean?
15:19:45 <amotoki> once l-c is dropped, I am not sure who can care min vers.
15:20:08 <e0ne> fair enough
15:20:13 <vishalmanchanda> IMO we can keep lower-constraints job as it is.
15:20:22 <e0ne> vishalmanchanda: +1
15:20:35 <vishalmanchanda> It is not so difficult to fix it if it fails atleast for horizon.
15:21:12 <amotoki> in neutron, we agreed and have dropped l-c in stable branches as we rarely change requirements.
15:21:22 <amotoki> thet's one possible compromise.
15:21:37 <e0ne> the same for cinder, but it will be a ptg topic
15:21:39 <amotoki> neutron still keeps l-c in the master branch.
15:22:41 <vishalmanchanda> We can follow the same approach in horizon as well.
15:24:41 <e0ne> +1
15:29:35 <e0ne> looks like we've got an agreement on it
15:30:02 <e0ne> let's move to the next topic
15:30:05 <e0ne> #link PTG planning
15:30:29 <e0ne> we need to decide which timeslots work for us until tomorrow
15:30:34 <e0ne> #link https://ethercalc.net/oz7q0gds9zfi
15:31:17 <e0ne> here is a poll with some proposed slots
15:31:18 <e0ne> #link https://doodle.com/poll/3yh2g6asbg9acaqt
15:31:37 <e0ne> amotoki: I hope, they don't conflict with neutron a lot
15:33:50 <amotoki> IIRC neutron will have sessions on 13-16UTC every day except Wed.
15:35:44 <amotoki> I did not notice the doodle poll till now. Was it announced?
15:36:00 <e0ne> actually, not
15:36:12 <e0ne> vishalmanchanda asked me about it before meeting
15:37:10 <e0ne> I'll keep it open until tomorrow
15:37:25 <e0ne> and will hope that our timeslots will be available
15:38:16 <amotoki> Only 14-15UTC slot looks available to me considering neutron and OSC/SCK sessions :)
15:38:31 <e0ne> :(
15:38:35 <amotoki> 14-15UTC Wed
15:40:03 <e0ne> neutron and cinder have a lot timeslots
15:40:15 <vishalmanchanda> We can add more options to the poll.
15:40:35 <vishalmanchanda> if that works for everyone.
15:41:37 <amotoki> I will be at horizon slot depending on topics for conflicing slots.
15:42:40 <amotoki> the poll have 05-07UTC slots on Tue, but unfortunately I have internal weekly meeting in these slots.
15:45:04 <e0ne> :(
15:47:18 <e0ne> amotoki: as I see poll results looks all slots work for everybody except you:(
15:47:38 <amotoki> e0ne: I think so.
15:48:45 <amotoki> so, you can select any slots for horizon. I will join horizon sessions depending on topics.
15:48:50 <e0ne> I understand you because cinder has a lot timeslots too
15:51:04 <vishalmanchanda> Ok let's book the most voted slot in PTG calendar https://ethercalc.net/oz7q0gds9zfi
15:51:34 <vishalmanchanda> because tomorrow is deadline for that http://lists.openstack.org/pipermail/openstack-discuss/2021-March/021239.html
15:52:10 <vishalmanchanda> I think 4-5 hours are enough for Horizon PTG discussion.
15:52:33 <vishalmanchanda> We can increase it depending on the topics if required.
15:53:00 <e0ne> +1
15:54:23 <vishalmanchanda> amotoki can join us depending on the topics in which he interested.
15:55:56 <e0ne> let's get a list of topic first and create a schedule
15:57:01 <vishalmanchanda> Could you create a etherpad where we can see how many topics we got for discussion.
15:57:08 <vishalmanchanda> e0ne: ^^
15:57:24 <e0ne> will do it and send a mail right after the meeting
15:57:44 <vishalmanchanda> e0ne: thanks:)
16:00:40 <vishalmanchanda> Guys we are out of time!
16:03:41 <e0ne> thanks for your participation!
16:03:44 <e0ne> #endmeeting