Add Docs for Guidelines for Upgrading an Existing Project's Django
|Reported by:||Donald Stufft||Owned by:||anonymous|
|Has patch:||yes||Needs documentation:||no|
|Needs tests:||no||Patch needs improvement:||yes|
A decent addition to the docs would be a short page about the general process to go about replacing a projects version of django with a new one.
It would include any concerns/considerations that a developer should look at when doing the upgrade. One such thing is that starting with python 2.7, Deprecation warnings are silenced by default (the thinking being that end users don't care about them). So when upgrading Django you should use something like
python -Wall manage.py test
python -Wd manage.py test
to check for any warnings.