Open Stack

Great work!

Is there anything that can be done to help meet that July deadline and
get 1.11.x in? I'm more than happy to help with reviews or even fixes
for newer Django in Horizon, and we should try and get others involved
if it will help as I think this is a little urgent.

Running anything less than Django 1.11 leaves us in a weird spot because
of the point where support ends for any versions below it.

Looking at the release timelines, if we don't get 1.11 in for Pike,
we'll have released a version of Horizon that will be for an unsupported
version of Django in about 6 months time (8 if deployers stick with
django 1.8):
https://releases.openstack.org/pike/schedule.html
https://www.djangoproject.com/download/

It isn't as bad it could be, but it's an awkward situation to be in. 1.9
is no longer supported, 1.10 support stops at 2018, so realistically 1.8
is the only version to have Pike 'safe' until Queens thats not
particularly great either. Getting 1.11 support in would be ideal.


On 05/07/17 03:01, Rob Cresswell wrote:
> Hi everyone,
>
> I've put up a patch to global-requirements to raise the Django cap to
> "<1.11", with the upper-constraint at "1.10.7"
> (https://review.openstack.org/#/c/480215). Depending on the remaining
> time, I'd quite like to move us to "1.11.x" before Requirements
> Freeze, which will fall around the 27th of July.
>
> Rob
>
>
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20170705/c3706701/attachment.html>