> 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?
That might be true that django has a clear deprecation schedule but it is still relatively fast compared to the release frequency of many other upstream projects. For example, I have now been trying to get pootle back into Debian for 3 years and at no time during this period has the version of django in sid been compatible with the current pootle release. Now python doesn't support versioned modules but it would be possible to have two (conflicting) packages in the archive that at least gave us a little flexibility in these jumps. cheers Stuart -- Stuart Prescott http://www.nanonanonano.net/ [email protected] Debian Developer http://www.debian.org/ [email protected] GPG fingerprint 90E2 D2C1 AD14 6A1B 7EBB 891D BBC1 7EBB 1396 F2F7 -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected] Archive: https://lists.debian.org/[email protected]
