#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):
I agree this needs to be resolved by 1.8 final.
I don't think "separate migrations for each supported Django version" is a
reasonable requirement to place on third-party apps.
Tim, do you have any specific examples of changes that have been made to
the autodetector in 1.8 that would cause the problem you mention?
--
Ticket URL: <https://code.djangoproject.com/ticket/23892#comment:15>
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.2a7e3e0ca42c62ec80ca3cd8ee52b1e9%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
