[PKG-Openstack-devel] Bug#755651: Bug#755651: horizon: Please ensure it works with Django 1.7

[Thomas Goirand]

On 07/22/2014 04:08 PM, hertzog at debian.org wrote:
> Source: horizon
> Version: 2014.1.1-3
> Severity: important
> User: python-django at packages.debian.org
> Usertags: django17
> 
> Hello,
> 
> your package horizon depends on python-django. As you might
> know, Django 1.7 will be soon available and as each new upstream major
> version, it brings many changes, some of them which are backwards
> incompatible (after a deprecation period covering 2 major versions):
> https://docs.djangoproject.com/en/1.7/releases/1.7/
> https://docs.djangoproject.com/en/1.7/releases/1.7/#backwards-incompatible-changes-in-1-7
> 
> We intend to upload Django 1.7 to unstable as soon as it is available
> because we really want the latest version in jessie and the freeze is
> approaching fast. In preparation of that, I have uploaded a release
> candidate in experimental.
> 
> Please test your package against Django 1.7 in experimental. If a new
> upstream version of your package is required, please package it now.
> If you can't upload it to unstable because it only works with Django 1.7,
> feel free to upload it to experimental too.
> 
> If the current package works fine, please close this bug (or retitle it as
> a suggestion to implement Python 3 support and drop its severity to
> wishlist[1]). If it's broken, please tag it as confirmed. If it's not
> broken, but would benefit from further work, please tag it as confirmed
> but reduce the severity.
> 
> If you have experimental in your sources.list you can install the latest
> version easily:
> $ sudo apt-get install -t experimental python-django python3-django
> 
> [1] We have recently added Python 3 support with the addition of
> python3-django. Consider doing the same if your package is a Django
> application/library.
> 
> Thank you for your help!
> 
> PS: I will raise the "confirmed" bugs that are still of severity
> "important" to "serious" once we upload Django 1.7 to unstable.

Hi,

No, Horizon 2014.1 is *not* compatible with Django 1.7, and it will
*never* be compatible with it. My current plan is to leave OpenStack
Icehouse in Debian Sid before the freeze, and not to upgrade to
OpenStack Juno when it is released. The reason is:

OpenStack Icehouse is included in major long therm support distributions
like Ubuntu 2014.4, which is an LTS, and also in RHELOS, made by RedHat.
Therefore, there's going to be some efforts to keep it up-to-date with
security. This will *not* be the case for OpenStack Juno which will be
released in October.

Also, having OpenStack Juno released only on the 16th of October makes
it very tight to have it to reach Jessie before the freeze in a
reasonable shape. I do not wish to attempt this, and I am sure that the
release team will agree with me.

I don't even think that OpenStack Juno will be ready to work with Django
1.7 anyway.

While I salute your effort to bring the latest version of Django to
Jessie, I am afraid that I have to oppose to it. This is *already too
late* to make it to Jessie, especially considering that we had lots of
changes to deal with Django 1.6, and if history repeats, that's really
too many reverse dependencies to fix.

Release team: could you as well voice your opinion on this? Would you
agree that it's too late already?

Cheers,

Thomas Goirand (zigo)