I wrote a "Django 5.0 is out" post.
Other people have covered new features well, so I focused on a few other things: understanding Django's version numbering system, how to upgrade a simple project, and a small section on deployment.
@ehmatthes I recently learned about https://jefftriplett.com/django-release-cycle/ which is easier to search for than django's current equivalent.
@CodenameTim I think I'd seen this once before. 4.2 and 5.0 are not categorized correctly at the moment, are they?
@ehmatthes I thought they were. What were you expecting?
@CodenameTim @ehmatthes I have been meaning to update this. I'll do that tonight.
I was meaning to move this to Django Packages along with a readiness check, but first I'll update my blog's
@webology @CodenameTim This is a much better visualization than the static one on the Downloads page.
It's updated now: https://jefftriplett.com/django-release-cycle/
It took me longer to clear the cache than to update it, but once I move it over to Django Packages, it'll be updated more in realtime. (soon)
@webology @CodenameTim @ehmatthes This https://endoflife.date/django and the API endpoint https://endoflife.date/api/django.json are my main uses for endoflife.date, but I watch most of my projects dependencies there.
@webology @jbeimler @CodenameTim Thanks Jeff, I updated the post to include this.
@CodenameTim It currently shows 4.2 and 5.0 as prereleases, just like 5.1 and 5.2.
This visualization is more interesting than the one for Python, because it shows the overlap between various LTS and non-LTS releases so clearly.