Correct. Django 6.0 comes with a standardised API, with 2 testing backends (ImmediateBackend and DummyBackend). You need a third-party backend to store and execute tasks.

Good to know. So no need for Django Q2 or Celery anymore either. I guess unless one has a specific reason.

Has there been discussion about adopting/embedding django-tasks into Django 6.x?

django-tasks is the reference implementation for django.tasks, by the same author. It's up for discussion if and when the DatabaseBackend gets merged, and it seems likely to me that a Redis-based backend would be suggested at some point. It takes time and energy though!