Details are available on the Django project weblog: https://www.djangoproject.com/weblog/2016/jan/02/bugfix-releases-issued/
On a related note: Python 3.2 users, please be advised that we've decided to drop support for Python 3.2 in Django 1.8.x at the end of 2016. We won't break things intentionally after that, but we won't test subsequent releases against Python 3.2 either. Upstream support for Python 3.2 ends February 2016 so we don't find much value in providing security updates for a version of Python that could be insecure. To read more about the decision and to let us know if this will be problematic for you, please read the django-developers thread: https://groups.google.com/d/topic/django-developers/eMu5UQpUdWs/discussion. -- 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 django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at https://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/20b977e6-1264-4833-b759-079652489534%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
