Hi, On Tue, 22 Jul 2014, Neil Williams wrote: > Raphael: please expand on why you want 1.7 in Jessie other than "it's > newest so must be best". I'm perfectly happy to have django1.7 and > later available from backports. Which specific *features* in django1.7 > are to be considered as justifying the upload to unstable, bearing in > mind the reverse dependencies. > > From the django release notes, there isn't a whole lot of "got to have" > stuff in 1.7.
>From the features point of view, it's the support of database schema migration that I really want: https://docs.djangoproject.com/en/1.7/releases/1.7/#schema-migrations (I know South which provides something very close for Django 1.6) That said, it's also a matter of having proper security support during all the lifetime of Jessie: https://docs.djangoproject.com/en/1.7/internals/release-process/ The project provides security updates for the last two stable releases which are each supported for a period of around 9-12 months. Some releases get an extra LTS support period but 1.6 is not such a release. And Django is a package with regular security updates (7 updates so far in Wheezy, 10 in Squeeze), so this is a very important point for me. The progressive depreciation and clear schedule and instructions given by upstream makes it not too difficult to "upgrade" to newer Django versions. So I don't really buy your argument Thomas. Have you just tried to run it with Django 1.7? Cheers, -- Raphaël Hertzog ◈ Debian Developer Discover the Debian Administrator's Handbook: → http://debian-handbook.info/get/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
