Django 5.2 Roadmap
This document details the schedule and roadmap towards Django 5.2.
What features will be in Django 5.2?
Whatever gets committed by the alpha feature freeze!
Django 5.2 will be a time-based release. Any features completed and committed to main by the alpha feature freeze deadline noted below will be included. Any that miss the deadline won't.
If you have a major feature you'd like to contribute, please introduce yourself on the django-internals forum so you can find a shepherd for your feature.
Minor features and bug fixes will be merged as they are completed. If you have submitted a patch, ensure the flags on the Trac ticket are correct so it appears in the "Patches needing review" filter of the Django Development Dashboard. Better yet, find someone to review your patch and mark the ticket as "Ready for checkin". Tickets marked "Ready for checkin" are regularly reviewed by mergers.
Schedule
Major milestones along the way to 5.2 are scheduled below. See Process for more details. Dates are subject to change.
| Date | Milestone |
|---|---|
| Jan. 16, 2025 | Django 5.2 alpha; feature freeze. |
| Feb. 19, 2025 | Django 5.2 beta; non-release blocking bug fix freeze. |
| March 19, 2025 | Django 5.2 RC 1; translation string freeze. |
| April 2, 2025 | Django 5.2 final. |
Process
Any features not completed by the feature freeze date won't make it into 5.2.
The release manager will keep the schedule updated and ensure efficient routing of issues and reminders for deadlines.
Feature freeze / Alpha 1
All major and minor features must be merged by the Alpha 1 deadline. Any
features not done by this point will be deferred or dropped. At this time, we
will fork stable/5.2.x from main.
After the alpha, non-release blocking bug fixes may be backported at the mergers' discretion.
Beta 1
Beta 1 marks the end of changes that aren't release blocking bugs. Only release blocking bug fixes will be allowed to be backported after the beta.
RC 1
If release blockers are still coming in at the planned release candidate date, we'll release beta 2 to encourage further testing. RC 1 marks the freeze for translation strings; translators will have two weeks to submit updates. Release blocking bug fixes may continue to be backported.
Final
Django 5.2 final will ideally ship two weeks after the last RC. If no major bugs are found by then, 5.2 final will be issued; otherwise, the timeline will be adjusted as needed.
How you can help
Community effort is key. You can help by:
- Reading the guide to contributing and Django's release process.
- Working on patches and triaging tickets.
- Attending sprints.
- Testing release snapshots (alphas, betas) against your code and reporting bugs.
- Providing as many testers as possible to ensure a bug-free release.