[PATCH 02/11] tox: Update versions of Django to be tested

Damien Lespiau damien.lespiau at intel.com
Wed Aug 19 23:31:08 AEST 2015

On Wed, Aug 19, 2015 at 12:25:43PM +0100, Damien Lespiau wrote:
> On Tue, Jun 30, 2015 at 09:52:00AM +0100, Stephen Finucane wrote:
> > Since patchwork now supports Django 1.8 and no longer support 1.5, we
> > should update the tox targets to validate this new subset of supported
> > Django versions.
> > 
> > In addition, the paths to the requirements.txt files were not updated
> > as part of a rebase. Correct this oversight.
> > 
> > Signed-off-by: Stephen Finucane <stephen.finucane at intel.com>
> A few comments based on the latest tree and the tries to make it work
> for me locally:
> - Because patchwork is now using migrations, we should restrict django
>   to 1.7+?
>   I appreciate that people may still have django 1.6 around, but that
>   means will need to maintain both manual SQL statements and the django
>   1.7+ migrations. Sounds like a good idea to have a cut off?

In addition, see section "Supported Versions" of:


Django 1.6 is already not supported, not even security fixes are going
to be backported by upstream. Next LTS version is 1.8, seems like a good
canditate as the preferred django dependency.


More information about the Patchwork mailing list