Upgrade One and Done to Django to 1.9.4 (bugfix release)

VERIFIED INCOMPLETE

Status

Mozilla QA
One and Done
P2
normal
VERIFIED INCOMPLETE
2 years ago
2 years ago

People

(Reporter: bsilverberg, Assigned: kthiessen)

Tracking

Version 4
Milestone 1

Details

(URL)

(Reporter)

Description

2 years ago
Per https://www.djangoproject.com/weblog/2016/mar/05/bugfix-releases/ it's probably a good idea to keep our version of Django up to date by upgrading to this bugfix.

This isn't critical, but nice to get done at some point.

Karl, do you want to try this?
(Reporter)

Updated

2 years ago
No longer depends on: 1252675
Flags: needinfo?(kthiessen)
Priority: -- → P2
Target Milestone: --- → Milestone 1
(Assignee)

Comment 1

2 years ago
Basically, same drill as what I just did for the security release?
Flags: needinfo?(kthiessen)
(Assignee)

Comment 2

2 years ago
Bob confirms that this is the same routine; I'm going to schedule this for tomorrow afternoon/evening Pacific time.
Assignee: nobody → kthiessen
Status: NEW → ASSIGNED
Should this be marked resolved fixed?
(Assignee)

Comment 4

2 years ago
I am not sure this work has actually been done; is there an obvious way to get the Django version out of a running webapp?
(Reporter)

Comment 5

2 years ago
You could check the requirements.txt file in the repo to see which version of Django is meant to be installed. You could also ssh into the account (using `heroku run bash`) and then issue a `pip freeze` which will show you which packages are installed.
(Assignee)

Comment 6

2 years ago
This is superseded by bug 1261834.
Status: ASSIGNED → RESOLVED
Last Resolved: 2 years ago
Resolution: --- → INCOMPLETE
Verified; thx.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.