Closed Bug 797592 Opened 13 years ago Closed 13 years ago

Run tests and fix test failures for Django 1.5 upgrade

Categories

(developer.mozilla.org :: Security, defect)

Product:
developer.mozilla.org
Component:
Security
Platform:
x86_64
Linux
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED INVALID

People

(Reporter: openjck, Assigned: jbennett)

References

Details

(Whiteboard: [subtask] p=3 c=Security p=)

While upgrading to Django 1.4.1, we should run our tests and pay attention to what the biggest test failures are.
Whiteboard: p=3
Whiteboard: p=3 → p=3 s=2012-10-16
Priority: -- → P2
Removing the s= tag to work around Scrumbugs issue 99: https://github.com/mozilla/scrumbugz/issues/99
Whiteboard: p=3 s=2012-10-16 → p=3
Whiteboard: p=3 → p=3 c=Security
Assignee: nobody → jbennett
Anyone who's interested in watching progress on this can track this branch: https://github.com/ubernostrum/kuma/tree/django-upgrade I'll be rebuilding/rebasing it as needed to merge in updated kuma code, and to fix test failures.
Summary: Run tests and figure out what the biggest failures are → Run tests and fix test failures
Summary: Run tests and fix test failures → Run tests and fix test failures for Django 1.4.1 upgrade
Commit pushed to master at https://github.com/mozilla/kuma https://github.com/mozilla/kuma/commit/a6584b3fe260386b59b56e1e24074528672d3c16 Merge pull request #717 from ubernostrum/django-upgrade Bug 797592: Django upgrade
Whiteboard: p=3 c=Security → [subtask] p=3 c=Security
Summary: Run tests and fix test failures for Django 1.4.1 upgrade → Run tests and fix test failures for Django 1.5 upgrade
Whiteboard: [subtask] p=3 c=Security → [subtask] p=3 c=Security p=
Blocks: 834326
Priority: P2 → --
(for anyone watching this, the logging refactor from bug 731212 is done but not merge-able for reasons explained there; meanwhile, I'm doing some final test runs and spot-checking everything before calling this good to go)
Tracking this as a subtask in Kanbanery.
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.