On Fri, 2015-11-06 at 08:36 +0100, Matthias Runge wrote: > If I got the context right here, the question is, when (and if) there > will be a Django upgrade for epel7 to Django-1.8.x, right?
Yeah that would be the most obvious "question" here. I wasn't even sure that it was going to be possible to do that, so the lesser question would have been "is it even going to happen" :) > Currently, an upgrade there is blocked by applications, e.g. > reviewboard, which don't support Django-1.8.x yet. Ok. Do you have any idea if there's any work going on to address that, or so? > My plan is still, to push an LTS Django version there asap. Until then, > I'll make sure, the Django-1.6.x version in EPEL7 is still secure (i.e. > backport security fixes). Right. The thread is really about patchwork removing Django 1.6 compatibility, for various reasons (migrations being one, Django upstream support being another, perhaps more) > With respect to migrations, I guess, the only way to do it right now is > to use Django-south, which is integrated e.g. in Django-1.8. > > On a side note, Red Hat OpenStack Platform 7 comes with Django-1.8 > packages. The same goes for rdoproject.org. They are distributing > Django-1.8 packages for their Kilo and Liberty release, and they should > cleanly install on RHEL7/CentOS7 nodes with EPEL enabled. But, I would > expect issues with Django packages installed from EPEL7 and with > Django-1.8 version from those OpenStack related repositories. Yeah, though I think the kernel.org admins won't be installing anything from outside RHEL7/EPEL7. > Does that answer your question? It does, thanks. johannes _______________________________________________ Patchwork mailing list Patchwork@lists.ozlabs.org https://lists.ozlabs.org/listinfo/patchwork
