Merge lp:~cjwatson/isitdeployable/django-1.8 into lp:isitdeployable
Proposed by
Colin Watson
Status: | Merged |
---|---|
Approved by: | Colin Watson |
Approved revision: | 274 |
Merge reported by: | Otto Co-Pilot |
Merged at revision: | not available |
Proposed branch: | lp:~cjwatson/isitdeployable/django-1.8 |
Merge into: | lp:isitdeployable |
Prerequisite: | lp:~cjwatson/isitdeployable/drop-django-factory |
Diff against target: |
171 lines (+15/-22) 8 files modified
django_project/settings_base.py (+1/-7) requirements.txt (+4/-4) revtracker/data.py (+1/-3) revtracker/tests/factory.py (+1/-1) revtracker/tests/test_views.py (+2/-2) revtracker/urls.py (+1/-1) revtracker/views.py (+3/-3) setup.py (+2/-1) |
To merge this branch: | bzr merge lp:~cjwatson/isitdeployable/django-1.8 |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Ricardo Kirkner (community) | Approve | ||
Daniel Manrique (community) | Approve | ||
Review via email: mp+336784@code.launchpad.net |
Commit message
Upgrade to Django 1.8.
To post a comment you must log in.
Wow was this really all that was needed? (other than the prereq branches you've already taken care of) How about lingering deprecation warnings? Did it behave properly while manual-testing? (I know the deployable test suite is not super thorough).
LGTM, I do recall the main sticking point was the django_comments thing but that seems to be solved here.
Also, I don't see updates to https:/ /code.launchpad .net/~ubuntuone -hackers/ isitdeployable- dependencies/ trunk, I don't recall the situation here because we're now building a docker image and I don't remember if we still use that dependencies branch with wheels. Just curious; the need for updating that branch will be apparent if the docker image fails to build :)
In any case, +1, since this looks good in general, I have a couple of comments but they shouldn't be blocking.