+++ This bug was initially created as a clone of Bug #1141023 +++ We'll want to update django to 1.8. We'll need all our infra to be on python 2.7x for that, though. 1.8 is the next LTS, so it's important to be at least on that one for security updates. New in 1.7: schema migrations, ohoh. New field api. django.setup(). at least, more on https://docs.djangoproject.com/en/dev/releases/1.7/ New in 1.8: Drops mysql support below 5.5, need to check. The deprecation list is long.
Commits pushed to develop at https://github.com/mozilla/elmo https://github.com/mozilla/elmo/commit/e14acab87b9438002c267fd4c188ffba5bd95676 bug 1147814, step 1, update to Django 1.7.x This is just the dependency, the actual work is coming in the following commits. https://github.com/mozilla/elmo/commit/de8039f33bab4cb35a5578935b2ebd3f61a75605 bug 1147814, update django to 1.8.x, 1.8.13 in particular. There's some follow-ups still, but this patch updates Django, and fixes a few fall-outs. For one, SafeString isn't the same as SafeUnicode, use the latter. Some select_related never worked, and were replaced with prefetch_related. There's something weird with ldap, I had to uncomment the cert file. It still seems to work locally, let's test on stage. ManyToMany models now warn about null being a useless option, fixing that. Keeping the blank, as there's no requirement for Milestones to have Signoffs to start with.
Status: NEW → RESOLVED
Last Resolved: 2 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.