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

[Neil Williams]

On Tue, 22 Jul 2014 23:51:27 +0800
Thomas Goirand <zigo at debian.org> wrote:

> > 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.

I'm looking at the same bugs for lava-server, lava-dispatcher and a
couple of other packages. So far, it doesn't look like it is a major
issue, yet.

> > 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]).

Python3 support is a much bigger issue and out of scope for release
discussions.

> No, Horizon 2014.1 is *not* compatible with Django 1.7, and it will
> *never* be compatible with it. 

Thomas - that sounds implausible. I've just done a migration from
django1.2 all the way up to 1.6. It was not a major issue and lava is
really *not* a small package.

> 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'm open to this, dependent on exactly how the porting goes. I'll know
more in the next few days.
 
> 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?

Release team: Just as a side-note, this decision affects more than just
openstack and I'm willing to reserve judgement on django1.7 until we've
done a bit more work on it. However, I agree that time is short if work
is required to migrate to 1.7 as lava upstream has other major work
ongoing between now and the end of the year - although that work won't
be done before the freeze, it nevertheless takes up time which might
be needed for a 1.7 fix, if any.

Raphael: please expand on why you want 1.7 in Jessie other than "it's
newest so must be best". I'm perfectly happy to have django1.7 and
later available from backports. Which specific *features* in django1.7
are to be considered as justifying the upload to unstable, bearing in
mind the reverse dependencies.

From the django release notes, there isn't a whole lot of "got to have"
stuff in 1.7.

-- 


Neil Williams
=============
http://www.linux.codehelp.co.uk/

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/openstack-devel/attachments/20140722/2997b6f8/attachment.sig>