Test against precise, Django 1.5
Bug #1302844 reported by
Allan LeSage
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| qa-coverage-dashboard |
Won't Fix
|
Medium
|
Unassigned | ||
Bug Description
If we wish to merge with the qa-dashboard, we'll have to tick back to precise and Django 1.5 from trusty and Django 1.6. Use our fabfile.py script to deploy to a Canonistack instance, stipulate Django 1.5 in that script.
| Changed in qa-coverage-dashboard: | |
| importance: | Undecided → Medium |
Revision history for this message
| Allan LeSage (allanlesage) wrote | #1 |
| Changed in qa-coverage-dashboard: | |
| status: | New → Won't Fix |
To post a comment you must log in.
I'm told that we'll no longer be deploying within the qa-dashboard context so this is no longer important.