● Covered by 1 source · 1 reportMedium impact1 neutral
Django Adopts Annual Release Cycle Starting 2028, All Releases to Receive Three Years of Support
Key points
- Django will release one feature version annually from January 2028.
- Each feature release will receive three years of support.
- Version numbers will align with the release year (e.g., Django 2028).
- Improved compatibility with Python's annual release schedule.
New Annual Release Schedule
Django is moving to an annual release cycle starting in January 2028, following the approval of Django Enhancement Proposal (DEP) 20 by the Django Steering Council. Under this new model, Django will release one feature version per year. These releases will be named after their release year, such as Django 2028 and Django 2029.
Extended Support for All Releases
A significant change is that every feature release will now receive three years of support. This includes one year of mainstream bug fixes, followed by two additional years of security and data-loss fixes. Consequently, the "LTS" (Long Term Support) label will be retired, as all feature releases will offer the same level of commitment.
Improved Python Version Alignment
The new annual cycle aims to better align with Python's own annual release schedule. Each Django version will support the three latest Python versions at its release and will incorporate the newest Python version during its first year. The support window for Django will conclude in conjunction with its oldest supported Python version, addressing previous issues where Django LTS releases supported Python versions past their upstream end-of-life.
Transition and Impact
The first release under this new cycle will be Django 2028. Existing support commitments for Django 5.2 LTS and 6.2 LTS will remain unchanged. This shift is intended to simplify upgrades for users, allowing them to update annually without facing a two-year gap of changes, and provides third-party packages with a consistent, rolling target for compatibility.
✨ This summary was generated by AI from the outlets' reporting listed below. It is not independently verified and may contain errors — check the original sources. How BrevFeed works →
The daily brief
One email each morning: the day's tech stories, clustered across outlets and summarized. No account needed.
One email a day. Unsubscribe in one click, any time.
Today's brief
Spend a few minutes, get the whole day. Every topic's top stories in one hands-free rundown — listen, watch, or read the transcript.
▶ Play today's brief
New every morning, and the back catalogue is archived by date.
Reporting from
The Django Steering Council has approved DEP 20, transitioning Django to an annual release cycle beginning in January 2028. This change means every feature release will receive three years of support, effectively retiring the "LTS" label and simplifying Python version compatibility.