Open Stack

Hello Everyone,

As discussed at this weekly meeting[1] and Shanghai PTG[2], Horizon team is
going to bump default version of Django to the next LTS release which is
2.2.
Django 2.2 support is already added in Horizon and all its plugins [3].
Thanks to all for taking this at the priority and quick approvals on the
patches.

After Switching the default version of Django to 2.2(latest LTS), We will
drop
Django 1.11 in the next step(as its extended supports ending soon [4]).
Also, Horizon usually supports LTS version of Django[5].


Please find below plan for coming weeks:
Step 1: Switch the default version to Django 2.2 in upper-constraints till
milestone-1.
Additionally, Due to these changes, there might be a possibility of
potential risks.
Horizon and horizon plugins already support Django 2.2 as unit tests,
but they are not tested in the real deployments with Django 2.2.
So After switching the default version, if anything breaks we will keep
working on fixing those issues.
Step 2: Drop Django 1.11 during milestone-2.

In case of any issue, please feel free to reach-out to Horizon channel
#openstack-horizon.

[1]
http://eavesdrop.openstack.org/irclogs/%23openstack-meeting-alt/%23openstack-meeting-alt.2019-11-27.log.html#t2019-11-27T15:27:23
[2] https://etherpad.openstack.org/p/horizon-u-ptg#45
[3]
https://review.opendev.org/#/q/topic:django22+(status:open+OR+status:merged)
[4] https://www.djangoproject.com/weblog/2015/jun/25/roadmap/
[5]
https://docs.openstack.org/horizon/latest/contributor/policy.html#django-support
[6] https://docs.djangoproject.com/en/2.2/releases/2.2/

cheers,
Vishal Manchanda
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-discuss/attachments/20191204/9d55dcd7/attachment.html>