#26713 closed Cleanup/optimization (fixed)
Recommend running tests with deprecation warnings, prior to upgrade.
Reported by: | Tom Christie | Owned by: | nobody |
---|---|---|---|
Component: | Documentation | Version: | dev |
Severity: | Normal | Keywords: | |
Cc: | Triage Stage: | Accepted | |
Has patch: | yes | Needs documentation: | no |
Needs tests: | no | Patch needs improvement: | yes |
Easy pickings: | no | UI/UX: | no |
Description
Currently the upgrade docs recommend upgrading Django, and then working through the tests with deprecation warnings turned on.
Really we ought to recommend working through the tests with deprecation warnings turned on *first* prior to upgrading.
Further discussion on this at https://groups.google.com/forum/#!topic/django-developers/tz40MK4AOjo
Change History (6)
comment:1 by , 8 years ago
comment:2 by , 8 years ago
Also related - link prominently to the upgrade docs from the release notes.
comment:3 by , 8 years ago
Has patch: | set |
---|---|
Patch needs improvement: | set |
Triage Stage: | Unreviewed → Accepted |
I merged the second PR and left a few comments for improvement on the first.
Note:
See TracTickets
for help on using tickets.
PR: https://github.com/django/django/pull/6732