[PATCH] RFC: Monkey-patch Django performance bug
stephen at that.guru
Fri Sep 8 18:41:37 AEST 2017
On Fri, 2017-09-08 at 07:14 +1000, Stephen Rothwell wrote:
> Hi Stephen,
> On Thu, 07 Sep 2017 19:41:36 +0100 Stephen Finucane <stephen at that.guru>
> > What version of Django is the Ozlabs instance using? Would it be possible
> > to work with the upstream Django folks to get this backported to those
> > versions? If nothing else, this patch is there and I'd be OK to add a
> > pointer in the docs about it. I just don't want to merge it in Patchwork,
> > heh.
> Ozlabs.org is currently running v1.10.7 of Django. The latest version
> available is in Debian is v1.11.4 (for testing that ozlabs.org runs) or
> v1.11.5 for unstable (which will be in testing soon).
I don't know what Django's backport policy actually is, but it would appear
both 1.8 (LTS) and 1.10 are still in extended support . This performance
regression does seem like a viable candidate for v1.10.8 (based on how we do
thing in OpenStack land at least). I can chase this up if no one else fancies
doing it. I am also happy to add this to the documentation until that happens.
> However, Patchwork is only documented to support v1.10 (as far as I know).
Correct. However, Django v1.11 support should be Patchwork v2.1, which I'd
expect to be releasing before years end (the 1.11 support patches are already
there, but I need to track down a potential performance regression first).
PS: Without a clear user, I think we should probably drop Django 1.6 and 1.7
support now. Will probably do that once 1.11 support is in there.
More information about the Patchwork