#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
--------------------------------------+------------------------------------
Changes (by timgraham):
* severity: Normal => Release blocker
Comment:
One problem with using the oldest supported version of Django to generate
your migrations will be autodetector changes in newer versions of Django.
For example, say I am using migrations generated from 1.7 from an app that
supports 1.7 and 1.8. If I am using 1.8, the autodetector will want to
generate new migrations for the new things it supports even if I don't
care about them.
A possible, albeit unfortunate solution would be to ship separate
migrations for each version of Django you want to support.
I think we need to resolve this issue at least by 1.8 final.
--
Ticket URL: <https://code.djangoproject.com/ticket/23892#comment:14>
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.6c3cfab08b69570a5b2536184ef31299%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
