https://www.djangoproject.com/download/
The world keeps spinning and Django keeps upgrading. 1.10 (the version this project is written on) ends mainstream support this month and ends extended support at the end of this year. 1.11 has just been released though, is the new LTS, and has support through mid-2020. Given the presence of unit tests the migration shouldn't be too hard. The one thing is - before rolling out changes to servers with data - you should test migration on a server running with a duplicate of their data to make sure there isn't data corruption.
Here's the release notes:
https://docs.djangoproject.com/en/1.11/releases/1.11/
https://docs.djangoproject.com/en/1.11/releases/1.11/#liveservertestcase-binds-to-port-zero
I gave them a glance and we're in conflict with at least one of the backwards incompatible changes, which will have to be addressed for unit tests to work. The use of the liveserver flag on the command line has been eliminated. So the networking between docker containers for testing will need to work differently as a consequence.
https://docs.djangoproject.com/en/1.11/releases/1.11/#pytz-is-a-required-dependency-and-support-for-settings-time-zone-none-is-removed
Probably need to set time zone.
https://docs.djangoproject.com/en/1.11/releases/1.11/#html-changes-in-admin-templates
Worth glancing through admin templates to make sure this doesn't break them but I think they're fine.
https://docs.djangoproject.com/en/1.11/releases/1.11/#miscellaneous
The new activation of ALLOWED_HOSTS during tests may cause problems. Shouldn't be much to solve it
https://www.djangoproject.com/download/
The world keeps spinning and Django keeps upgrading. 1.10 (the version this project is written on) ends mainstream support this month and ends extended support at the end of this year. 1.11 has just been released though, is the new LTS, and has support through mid-2020. Given the presence of unit tests the migration shouldn't be too hard. The one thing is - before rolling out changes to servers with data - you should test migration on a server running with a duplicate of their data to make sure there isn't data corruption.
Here's the release notes:
https://docs.djangoproject.com/en/1.11/releases/1.11/
https://docs.djangoproject.com/en/1.11/releases/1.11/#liveservertestcase-binds-to-port-zero
I gave them a glance and we're in conflict with at least one of the backwards incompatible changes, which will have to be addressed for unit tests to work. The use of the liveserver flag on the command line has been eliminated. So the networking between docker containers for testing will need to work differently as a consequence.
https://docs.djangoproject.com/en/1.11/releases/1.11/#pytz-is-a-required-dependency-and-support-for-settings-time-zone-none-is-removed
Probably need to set time zone.
https://docs.djangoproject.com/en/1.11/releases/1.11/#html-changes-in-admin-templates
Worth glancing through admin templates to make sure this doesn't break them but I think they're fine.
https://docs.djangoproject.com/en/1.11/releases/1.11/#miscellaneous
The new activation of ALLOWED_HOSTS during tests may cause problems. Shouldn't be much to solve it