Commits on Dec 21, 2016

1. Upgrade Django to latest 1.9 bugfix release. …

   Upgrade Django to latest bugfix release on 1.9 branch. Prevent later
   major releases of Django from being installed, since some of our
   dependencies do not support Django 1.10+.

   

   martey committed Dec 21, 2016
   Configuration menu

   • View commit details
   • Copy full SHA for 0fa0c41
   • Browse repository at this point

   Copy the full SHA

   0fa0c41 View commit details

   Browse the repository at this point in the history

2. Upgrade various dependencies. …

     - Upgrade django-appconf to 1.0.2 (the first version to support Django
       1.9 - see
       https://django-appconf.readthedocs.io/en/v1.0.2/changelog/#id1) and
       loosen requirement to allow newer bugfix releases to be used but not
       new releases that might have backwards incompatible changes.
     - Upgrade django-model-utils minimum requirement to 2.5.1 - the first
       version to support Django 1.9
       (https://github.com/carljm/django-model-utils/blob/master/CHANGES.rst#251-20160803).
     - Upgrade django-reversion to latest 1.x.x release. We should upgrade
       to 2.x at some point in the future.
     - Upgrade django-sitetree to 1.6.0.
     - Upgrade django-taggit to 0.21.3, the latest bugfix release.
     - Upgrade django-timezone-field to 2.0, which supports Django 1.9. The
       only backwards incompatible change between these two releases is the
       removal of TimeZoneFieldBase, which we do not use.
     - Upgrade markdown to latest bugfix release (2.6.7).
     - Update pytz to latest version (2016.10).

   

   martey committed Dec 21, 2016
   Configuration menu

   • View commit details
   • Copy full SHA for b4bf08c
   • Browse repository at this point

   Copy the full SHA

   b4bf08c View commit details

   Browse the repository at this point in the history