What's the migration plan for when the database backend ships with Django itself?

[hmpf]

So, let's say I start using "django_tasks.backends.database.DatabaseBackend" now, before it is added to Django proper. When (I hope for when, not if) it is added to Django, what steps will be necessary to migrate the existing tasks? Just changing the name of the app and backend in settings and updating any potential import paths? (That should be scriptable even..)

[RealOrangeOne]

Currently, there isn't a timeline for when it will ship with Django core. There's lots of different ways we could do it. We can either keep the table name in Django core, so there's nothing to migrate, or have a migration to rename the table / copy the data over.

[hmpf]

I notice that there are 16 migrations so far, it would be clean if the the first django-included version squashed them, which would mean a "how to switch to the django-shipped app" procedure would be needed. migrate --fake django_tasks_database 0001 && migrate --fake django_tasks_database 0001_squashed` probably.

[RealOrangeOne]

Yes, they'll be squashed before merge. There's 16 now, but there'll likely be many more before upstreaming.