On Wed, 2017-05-24 at 13:14 +0000, Scott Kitterman wrote: > On May 24, 2017 8:30:00 AM EDT, Ben Hutchings <ben@decadent.org.uk> wrote: [...] > > I've always understood that the exceptional cases justify backporting a > > newer version that is currently only in unstable, not an older version. > > > > I think we should have an additional exception for cases where it > > becomes impractical to backport newer versions but a maintainer is > > willing to support it with important fixes. But from what I've read, > > that doesn't seem to be the case with Django 1.10. > > Other than breaking lots of user applications, no. > > Upgrading from 1.7 in Jessie to 1.10 is highly likely to break user > code (even if it doesn't break things in the archive). That is a normal risk when using a non-stable suite. Ben. > Removal would be better. If we can't fix 1.8, we should just get rid > of the backport. -- Ben Hutchings In a hierarchy, every employee tends to rise to his level of incompetence.
Attachment:
signature.asc
Description: This is a digitally signed message part