Closed Bug 1141023 Opened 10 years ago Closed 10 years ago

Update django to 1.6

Categories

(Webtools Graveyard :: Elmo, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: Pike, Assigned: Pike)

References

Details

Attachments

(1 file)

We'll want to update django to 1.6 to benefit from its improved transaction management. In particular, we need this for bug 685512, moving all-locales data into the db. We'll want to clean up python dependencies in bug 1121496 before this. We might go to 1.7 right away, the big migration piece there is to switch away from South.
Depends on: 1141581
1.7 requires python 2.7, and our VM is on 2.6, so let's update to django 1.6 for now.
Summary: Update django to 1.6+ → Update django to 1.6
Depends on: 934547
Depends on: 1143676
Blocks: 1147814
Depends on: 1149237
Depends on: 1150466
Assignee: nobody → l10n
Status: NEW → ASSIGNED
Michael, we're not really doing PRs on elmo, but the patch list is the state of the art on my way to django 1.6. I'll probably need an intermediate integration branch, as I can't deploy 1.6 at this point (no security updates), and I can't move to 1.7 or 1.8 (stuck on py2.6).
(In reply to Axel Hecht [:Pike] from comment #3) > Michael, we're not really doing PRs on elmo, but the patch list is the state > of the art on my way to django 1.6. > > I'll probably need an intermediate integration branch, as I can't deploy 1.6 > at this point (no security updates), and I can't move to 1.7 or 1.8 (stuck > on py2.6). Reviewed the patch list, everything looks good to me! Left a few comments on some nits but otherwise it looks like you're doing great. Lemme know if/when you need me to look over anything else. :D
Thanks for the reviews, I've fixed the review comments, and rebased the whole shenanigon. I'm marking this FIXED, despite the fact that I'm only pushing to random branches on my personal clone so far. As long as I can't deploy even in stage, that's as good as it gets.
Status: ASSIGNED → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Commits pushed to develop at https://github.com/mozilla/elmo https://github.com/mozilla/elmo/commit/56a1c74f1218c4a87e0ed3bdbc9ca818fff052f6 bug 1141023, step 1, update to Django 1.5.12 Tests are unlikely to pass, this will be a series of commits per topic https://github.com/mozilla/elmo/commit/859da5afbbc4c3e07eef331ddb796baf0e1eacec url tags are now in the future, remove the import. part of bug 1141023 https://github.com/mozilla/elmo/commit/b048b50e69b54e50e3e65f73733f49d7cc93dc3d mock stdout for dumpdata, part of bug 1141023 dumpdata.handle used to return the string in 1.4.x, and doesn't with 1.5. mock stdout with a StringIO and get the output value from that. Also, use call_command, which handles arguments much better for us. https://github.com/mozilla/elmo/commit/a8f7f95588fd91503bbcdb152da548c0a0f60a8d Make l10n-changesets and friends explicitly non-streaming, part of bug 1141023 https://github.com/mozilla/elmo/commit/4ab427edb803e12e8b85683f82556fb573988295 bug 1141023, step 2, update to Django 1.6.11 https://github.com/mozilla/elmo/commit/0786cd8860c8c61d60b026fc67bbc9a5c9aa93c9 bug 1141023, make each push an atomic database transaction. Part of the update to django 1.6, and the new transaction handling there. If anything in getting the data for a push fails, we want to roll back the complete push so that we can try again.
Product: Webtools → Webtools Graveyard
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: