Migration to Django 1.3
Django 1.3 provides significant enhancements to handing views, contains the latest set of security and bug fixes and is generally backwards compatible across the board. We should upgrade our base web framework to reduce time spent on writing views of growing complexity.
Blueprint information
- Status:
- Complete
- Approver:
- Paul Larson
- Priority:
- Low
- Drafter:
- Zygmunt Krynicki
- Direction:
- Approved
- Assignee:
- Fathi Boudra
- Definition:
- Review
- Series goal:
- Accepted for linaro-11.11
- Implementation:
-
Implemented
- Milestone target:
-
2011.11
- Started by
- Fathi Boudra
- Completed by
- Fathi Boudra
Related branches
Related bugs
Sprints
Whiteboard
[fboudra, 2011-10-25] Headline/Acceptance is missing.
[pwlars, 2011-11-16] This is mostly done I think since we migrated the server to oneiric, however we should review the patches in the lava-blessed version of django 1.2 and make sure nothing is missing from 1.3.1.
[fboudra, 2011-11-17] we need to figure out if we want to support packages from lucid. At the moment, only Oneiric packages is supported (and soon lava-deployment tool). In the meantime, Debian 1.3.1-2 packages have been backported.
Headline: Lava now depends on django 1.3
Acceptance: django package backports available for 1.3 and installed with lava
Work Items
Work items:
Decide on which django to move to 1.3.1, 1.3: DONE
Decide on which package to follow (debian 1.3.1, ubuntu 1.3 or our own 1.2.5 + special patches): DONE
backport django 1.3.x to lucid->natty: DONE
Deploy on v.l.o: DONE
