#26078: Docs: DB Meta Migration Guildlines: More explicit "old" vs "new"
--------------------------------------+------------------------------------
Reporter: guettli | Owner: nobody
Type: Cleanup/optimization | Status: closed
Component: Documentation | Version: 1.9
Severity: Normal | Resolution: fixed
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 1
Easy pickings: 0 | UI/UX: 0
--------------------------------------+------------------------------------
Comment (by Tim Graham <timograham@…>):
In [changeset:"f619b72815fd8d0bb6f65921ef07ac4bc8a12e29" f619b728]:
{{{
#!CommitTicketReference repository=""
revision="f619b72815fd8d0bb6f65921ef07ac4bc8a12e29"
[1.9.x] Fixed #26078 -- Clarified "old vs. new" in model._meta upgrade
guide.
Thanks Thomas Güttler for the suggestion.
Backport of 28acc0d6df844ccfc8de6f4e7d5883eb4841e946 from master
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/26078#comment:4>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/065.c33ab56d6c4eb8431b7a4dec33464b38%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
