-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 11/26/2013 08:41 AM, Pierre-Yves Chibon wrote:
On Mon, Nov 25, 2013 at 09:07:55AM +0100, Matthias Runge wrote:
Hey,
recently, I saw a few requests to update python-django to Django-1.6, the corresponding bug is [1].
As there are quite a few changes, I'd expect this update to be harmful, at least - python-django-openstack-auth - openstack-dashboard
will break, and won't even build any more (because they also execute sanity checks during build).
So, the current plan is, to fix both packages upstream and then to update python-django to Django 1.6 in rawhide. I'd expect this to happen within the next two weeks and I'd update python-django to Django-1.6 around Dec 16th.
Because of bad timing, we won't have Django-1.6 in f20.
Just an idea, but what about providing Django 1.6 via copr for F{20,19}? That might also help testing current apps against the new Django.
Just to bring this thread back to life, we're getting to a point where support for Django 1.6 is becoming more and more necessary. Is there an ETA on its inclusion in Rawhide or COPR?