Support Django newer than Django-1.6
Horizon currently supports Django-1.6, which won't receive further security fixes once Django-1.8 is out (expected around April 1st, 2015.
Django-1.8 is the next planned LTS version (after Django-1.4)
Blueprint information
- Status:
- Complete
- Approver:
- David Lyle
- Priority:
- Essential
- Drafter:
- Matthias Runge
- Direction:
- Approved
- Assignee:
- Matthias Runge
- Definition:
- Approved
- Series goal:
- Accepted for kilo
- Implementation:
-
Implemented
- Milestone target:
-
2015.1.0
- Started by
- Matthias Runge
- Completed by
- David Lyle
Related branches
Related bugs
Sprints
Whiteboard
[mrunge, Feb 25 2015] If we can't make it for Django-1.8, 1.7 would work for now. There are about 2 tests not fixed.
[mrunge, Feb 27 2015] A new django-nose is required.
cf. https:/
Gerrit topic: https:/
Addressed by: https:/
Add Django-1.7 support
Review for global-
Gerrit topic: https:/
Addressed by: https:/
run compilemessages with runtime deps
Addressed by: https:/
remove django<1.7 from tests
Addressed by: https:/
Add reference to AUTH_USER_MODEL for tests
Addressed by: https:/
Use charset instead of _charset for dj18 response
Addressed by: https:/
Do not call _assertNotContains override in Django newer than 1.6
Gerrit topic: https:/
Addressed by: https:/
Use setUp() method for neutron rest test
Gerrit topic: https:/
Addressed by: https:/
Remove un-related nova quota in test data
Gerrit topic: https:/
Addressed by: https:/
Don't escape request.
Addressed by: https:/
Extend User from AbstractBaseUser and AnonymousUser
[robcresswell 2015-08-11]
bp doesn't appear to be tracking properly. Have manually updated the status of several patches, and added 167981. Be sure to double check when looking through this :)
Addressed by: https:/
Add todo regarding code removal in M
