#23892: Clarify forwards-compatibility policy for migrations
--------------------------------------+------------------------------------
Reporter: MarkusH | Owner:
Type: Cleanup/optimization | Status: new
Component: Documentation | Version: 1.7
Severity: Release blocker | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
--------------------------------------+------------------------------------
Comment (by carljm):
If this is a problem, it may be that we need a setting for "apps to ignore
when running `makemigrations`" (I don't think we should attempt to make
that decision in an automated way). I think we should wait to see whether
in practice that is needed, though. The reason I asked for specific
examples is because I'm having trouble imagining the sort of new feature
that would actually cause this problem. It would have to be something
where an unchanged model now gets a new migration generated under a new
Django version (that adds new in-memory migration state, and thus is
noticed by `makemigrations` if absent).
PR 3838 is unfortunate, but will only impact apps that have an `en-us`
translation which differs from the strings in the code. And the fix is
easy enough - remove that difference.
All in all, none of this changes my conclusion that our recommendation
should be to generate third-party app migrations using the lowest Django
version your app supports.
--
Ticket URL: <https://code.djangoproject.com/ticket/23892#comment:17>
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.06694c8182b4e6321d45599b0c8f75c8%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
