On Monday, June 15, 2015 at 7:49:32 AM UTC-6, Tim Graham wrote: > > Here are the cleanups for dropping Python 3.3: > https://github.com/django/django/pull/4861 > > To prevent users from getting stuck on a non-LTS version of Django with an > old version of Python (when they would have had longer support had they > stuck with an LTS), the policy I suggest we adopt is: > > Typically, we will support a Python version up to and including the first > Django LTS release that will receive security updates until after security > support for that version of Python ends. For example, Python 3.3 security > support ends September 2017 and Django 1.8 LTS security support ends April > 2018. Therefore Django 1.8 is the last version to support Python 3.3. >
I think this policy makes sense. It aligns nicely with the direction the new releases policy is heading, which is that the release right after an LTS is the one where more backwards-incompatible changes tend to concentrate (and the one where we bump the major version number). Carl -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/7021353c-7820-4333-a01e-834948db7ffe%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
