Closed Bug 935538 Opened 11 years ago Closed 10 years ago

Upgrade solitude and webpay to Django 1.6 or maybe even 1.7

Categories

(Marketplace Graveyard :: Payments/Refunds, defect, P3)

Product:
Marketplace Graveyard
Component:
Payments/Refunds
Platform:
x86
macOS
Type:
defect

Tracking

(Not tracked)

Status:
VERIFIED FIXED
Milestone:
2015-01-06

People

(Reporter: andy+bugzilla, Assigned: andy+bugzilla)

Details

(Whiteboard: [qa+]) 

Let's upgrade to the latest and greatest. Since solitude uses database transactions, might be worth checking the changes for that.
Priority: -- → P4
Assignee: nobody → amckay
Priority: P4 → P3
Summary: Upgrade solitude and webpay to Django 1.6 → Upgrade solitude and webpay to Django 1.6 or maybe even 1.7
Solitude done: https://github.com/mozilla/solitude/pull/302/files

Seems daft to do webpay until a huge chunk of the post spartacus code is cleaned out.
Blocks: 1014075
No longer blocks: 1014075
Depends on: 1014075
Not really a qa+, but I'd like to just do a smoke test of payments that it works ok. All unit tests pass, but the move from Django 1.5 > 1.7 was relatively big. So just a normal smoke test that you'd in a week will suffice.
No longer depends on: 1014075
Whiteboard: [qa+]
Target Milestone: --- → 2015-01-06
Seperating out from the webpay upgrade to get on QA's radar.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
No regressions were found in our smoke tests. Verified as fixed.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.