← Retour au blog
tech 10 August 2026

Django Moves to an Annual Release Cycle

Starting in 2028, Django will adopt an annual release cycle. This move promises better alignment with Python releases and extended support for each version.

Article inspired by the original source
Django is moving to an annual release cycle ↗ www.djangoproject.com

Introduction

Django, the web framework beloved by perfectionists, is about to undergo a significant change in how it handles updates. Starting January 2028, Django will move to an annual release cycle, a decision approved by the Django Steering Council through the DEP 20 enhancement proposal. This new strategy aims to offer better compatibility with Python versions while simplifying the upgrade process for developers.

Why an Annual Cycle?

Python, the language on which Django is built, releases a new version every October. Until now, Django had an eight-month release cycle, leading to misalignment in version compatibility and complicating support for outdated Python versions. With an annual cycle, each Django version will support the three latest Python versions available at the time of its release, making it easier to integrate new Python features as they appear.

Every Release is an LTS

Under this new model, each Django version will receive three years of support: one year of bug fixes and two years of security and data-loss fixes. This means every release is equivalent to a Long Term Support (LTS) version. Developers will no longer face gaps between LTS releases, making the upgrade process much smoother.

Benefits for Developers and Businesses

For developers and businesses, this change offers several significant advantages. First, it provides a clear roadmap with three supported versions at any given time, simplifying long-term planning and development. Second, API deprecation periods remain unchanged but become longer in calendar terms, offering more time to adapt to changes.

Implications for the Django Ecosystem

This new cycle is also expected to benefit the Django ecosystem as a whole. Third-party package developers will have a clearer target and a more predictable update cycle, encouraging better compatibility and faster updates. Moreover, end users will benefit from increased stability and enhanced security through regular and extended updates.

Transition Timeline

The transition to this new cycle will begin with the Django 2028 release, scheduled for January 2028. In the meantime, current versions, including Django 6.1 and 6.2 LTS, will continue to receive support according to previously established commitments.

Conclusion

By adopting an annual release cycle, Django positions itself to better meet the needs of developers and businesses while aligning with Python's rapid development pace. This decision should reinforce Django's position as one of the most reliable and modern web frameworks.

Let's discuss your project in 15 minutes.

Django annual release cycle Python compatibility LTS support web frameworks
Deepthix newsletter · 100% AI · every Monday 8am

An AI agent reads tech for you.

Our AI agent scans ~200 sources per week and ships the best articles to your inbox Monday 8am. Free. One click to unsubscribe.

Visit the newsletter page →

Want to automate your operations?

Let's talk about your project in 15 minutes.

Book a call