With the release of Django 5.2 in April and the recent 5.2.2 bugfix, it’s time to look ahead to our next feature release: Django 6.0. You can find the timeline and roadmap on the 6.0 roadmap wiki page.
A few quick notes:
Feature freeze is scheduled for September 17. If you’re working on something that’s close to ready, feel free to flag it. We’ll do our best to support progress, though realistically not all in-progress features will land. Anything that doesn’t make it will be reconsidered for 6.1 or later.
At this stage, most of the bigger features expected for 6.0 are already in motion. In particular, we’re aiming to land support for Django tasks, and bring Content Security Policy (CSP) support into core.
DjangoCon US (September 8-12) happens just before the freeze, which may affect availability for reviews and final pushes. Please keep that timing in mind.
As always, testing the main branch, reporting bugs, reviewing tickets, and helping with blockers makes a big difference. Thanks to everyone who’s able to help!
#35956 (Add composite foreign keys) – Django Csirmaz Bendegúz has already done the heavy lifting here in their original PR but they ran out of spare time. I took a look at it and did some testing and discovered a couple of things that also needed updating. Additionally I think we need to finalise the decision on the API. I have a full rundown ready to go up on the ticket or PR very soon. This one should definitely be ready by feature freeze
I have been working on #28586 (Automatically prefetch related for “to one” fields as needed.) for a while. It has evolved over time, with a new name in the PR, “Model field fetching modes”, a new QuerySet-based design as encouraged by Simon Charette. A few other folks have dipped in to check on the PR, and I think it’s ready for wider review now. Any help appreciated!
Announcement: 
Release notes:
Announcement: 
Release notes: