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?
Basically, same drill as what I just did for the security release?
Bob confirms that this is the same routine; I'm going to schedule this for tomorrow afternoon/evening Pacific time.
Should this be marked resolved fixed?
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?
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.
This is superseded by bug 1261834.