Hello hello 
Here are a few updates regarding the Django 5.2 release:
-
Feature freeze is scheduled for January 15th. If there are new features that you believe are close to being merged, please let us know. While we will do our best to push these forward, we cannot guarantee that all new features currently in progress will make it into 5.2. However, any features that do not make it into this release will certainly be considered in future releases like 6.0, and beyond.
-
You can help us by testing the dev branch, finding bugs early, triaging tickets, reviewing PRs, contributing fixes to release blockers, and more. Your assistance with these tasks is really valuable. If you’re able to do any of the above, we’d greatly appreciate it! 
15 Likes
Yesterday we conducted the feature freeze and cut the stable/5.2.x branch.
No new features will enter Django 5.2 
Today, we released Django 5.2 alpha 1: Django 5.2 alpha 1 released | Weblog | Django
This officially starts the bug fixing phase of the release.
If you get a chance, please test Django 5.2. It is both very valuable and very appreciated 
4 Likes
Today, we released Django 5.2 beta 1: Django 5.2 beta 1 released | Weblog | Django
This ends the “bug fixing phase”, in which bugs were backported to Django 5.2.
Going forward, only release blocking bugs will be backported.
All other bugs will be included in the next release, Django 6.0.
As always, if you get a chance, please test Django 5.2. It helps enormously
7 Likes
Today, we released Django 5.2 release candidate 1: Django 5.2 release candidate 1 released | Weblog | Django
This marks the string freeze for Django 5.2 and our call for translators to update translations. 
Django 5.2 is due to be released in 2 weeks time, April 2nd. 
6 Likes
Today, we release Django 5.2 (final): Django 5.2 released | Weblog | Django
Thank you for all the testing during the pre-release period 
5 Likes