Closed
Bug 1211464
Opened 10 years ago
Closed 10 years ago
Upgrade One and Done to Django 1.8
Categories
(Mozilla QA Graveyard :: One and Done, defect, P2)
Tracking
(Not tracked)
RESOLVED
FIXED
Milestone 3
People
(Reporter: bsilverberg, Assigned: bsilverberg)
References
Details
We should get One and Done onto the most recent version of Django, which right now is 1.8.5. This will involve a few significant changes.
| Assignee | ||
Updated•10 years ago
|
| Assignee | ||
Updated•10 years ago
|
Assignee: nobody → bob.silverberg
| Assignee | ||
Comment 1•10 years ago
|
||
Commit pushed to master at https://github.com/mozilla/oneanddone
https://github.com/mozilla/oneanddone/commit/1865d2f2d0e6ab9927c134d4aefa81004daa3004
Merge pull request #301 from bobsilverberg/django1.8_logical_commits
Bug 1211464 - Upgrade One and Done to Django 1.8
| Assignee | ||
Comment 2•10 years ago
|
||
Rebecca, this will be automatically pushed to dev shortly. We should do some extensive testing of the dev site before pushing this to prod as this is a pretty huge change. No problem if you cannot get to it until some time next week.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Comment 3•10 years ago
|
||
I ran through https://oneanddone-dev.allizom.org/ today as an admin and regular user, looks good.
Updated•7 years ago
|
Product: Mozilla QA → Mozilla QA Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•