#23861: IPAddressField removal will break migrations and test suites
-------------------------------+--------------------------------------
Reporter: spookylukey | Owner: nobody
Type: Bug | Status: new
Component: Uncategorized | Version: master
Severity: Normal | Resolution:
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------+--------------------------------------
Comment (by carljm):
I think that in fact, squashing old migrations does solve this problem,
and that's the solution we should recommend. Even third-party apps can
squash migrations and then later remove them without any problem. They
just need to get started on that process with enough lead time so that any
of their users who upgrade to Django 1.9 have already gotten through the
squashed migration set and upgraded to the version of the third-party app
that removes the old migrations.
--
Ticket URL: <https://code.djangoproject.com/ticket/23861#comment:2>
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/069.2b656ff165d847c24f3e6c2f6889f68b%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
