Here is the second update with three weeks to go until alpha: #23861 - <https://code.djangoproject.com/ticket/23861> Fields referenced in migrations cannot be (re)moved, even if migrations have been squashed <https://code.djangoproject.com/ticket/23861> #23891 <https://code.djangoproject.com/ticket/23891> - Revise deprecation / removal timeline for IPAddressField <https://code.djangoproject.com/ticket/23891> Owner: ? This week: On ticket #23891 I proposed the idea of moving model field deprecation warnings to the system check framework. I am waiting for feedback on this approach before investing further. Last week's status: We need someone to investigate a strategy for how we can deprecate model fields while keeping them available in historical migrations. Any takers? If we cannot complete this, I propose we bump the deprecation of IPAddressField until the issue is solved.
#22340 - <https://code.djangoproject.com/ticket/22340> Legacy Table Creation Methods Not Properly Deprecated <https://code.djangoproject.com/ticket/22340> Owner: ? This week: I think the performance concerns are no longer a blocker to resolving this ticket (see the mailing list thread for details). I did research on the remaining work needed and left a comment on the ticket. I will work on the implementation next week if no one else picks it up. Last week's status: This issue is being discussed in the thread "Migrations in Django 1.7 make unit testing models harder". In short, we likely to need to solve the performance issues with migrations before we can proceed with the deprecation. If we cannot, we'll likely have to delay the deprecation. #23271 - <https://code.djangoproject.com/ticket/23271>Makemessages can corrupt existing .po files on Windows <https://code.djangoproject.com/ticket/23271> Owner: Ramiro This week: no update Last week's status: Ramiro said he would have some time to investigate the issue soon. #23745 - Migrations migrate is slow <https://code.djangoproject.com/ticket/23745> (new) Owner: Claude Status: Patch seems to need improvement so it doesn't cause a regression with swappable models. -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" 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]. Visit this group at http://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/b632fa62-3292-457c-bee0-87b1314d8a97%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
