Jeremy/All,
With the latest version (v5) of the Django 1.7 series (found here:
https://lists.ozlabs.org/pipermail/patchwork/2015-April/001295.html), I now
consider Django 1.7 support in patchwork functionally complete and well tested.
I'm going to look at implementing a few of the more important things I'd like
to see in patchwork, but I'm curious about the upgrade plan for patchwork.
As mentioned in the cover letter for same, patchwork support two now-deprecated
versions of Django (1.5, 1.6). On the other hand, it does not yet support 1.8,
which is the latest LTS version of Django. While it would be irresponsible to
drop support for two versions of Django in a short time span, I suggest
dropping support for version 1.5 followed by adding of support for 1.8.
However, I have little to no say in this of course :)
Similarly, Python 2.7 is now approaching five years and Python 3 has developed
and grown in popularity during that time. The addition of Python 3 support is
probably a good idea at this point. I've begun looking into this but it's going
to be a lot of work and I'd like to know if there's demand for patches before
beginning anything. I think the addition of tox should make testing of this a
cinch. I suggest dropping support for Python < 2.7 (I'm unsure if 2.6 support
is still expected (Django 1.7 doesn't support it) and I can't test it on Fedora
21) and adding support for Python 3.0 at the very minimum.
What are people's opinions on the? Is there a roadmap anywhere that I should
look at?
Regards,
Stephen
_______________________________________________
Patchwork mailing list
Patchwork@lists.ozlabs.org
https://lists.ozlabs.org/listinfo/patchwork
