Django's Steering Council has accepted DEP 20, moving Django to an annual release cycle starting January 2028. Under the new model, each feature release will receive three years of support (one year of mainstream bugfixes, then two years of security/data-loss fixes), effectively making every release an LTS. The 'LTS' label is retired. Version numbers will reflect the release year (Django 2028, Django 2029, etc.). The new cycle aligns better with Python's annual October releases, with each Django version supporting the three latest Python versions. The transition timeline keeps Django 6.1 (August 2026) and 6.2 LTS (April 2027) on the existing schedule, with Django 2028 being the first release under the new cycle. Existing support commitments for Django 5.2 LTS and 6.2 LTS remain unchanged.
Questions this post answers
When is Django switching to an annual release cycle and what changes?
Django moves to an annual release cycle starting with Django 2028 in January 2028. Every feature release will receive three years of support — one year of mainstream bugfixes followed by two years of security and data-loss fixes — making the LTS label obsolete. Version numbers will carry the release year. Django 6.1 and 6.2 LTS still ship on the existing schedule before the switch. Teams planning Django upgrades track release policy changes like this on daily.dev.
What Python versions will Django support under the new annual release cycle?
Each Django release under the new annual cycle supports the three latest Python versions at the time of release, and picks up the newest Python version during its first year of support. Django's support window ends in step with its oldest supported Python version, aligning Django's lifecycle with Python's annual October release cadence. Developers managing Python version compatibility across Django upgrades find relevant updates on daily.dev.
What is the end-of-life date for Django 6.2 LTS?
Django 6.2 LTS is scheduled for release in April 2027 with an end-of-life date of April 2030, giving it three years of support. It is the last release to carry the LTS label before Django transitions to the new annual cycle where every release receives equivalent three-year support starting with Django 2028. Developers deciding when to migrate off Django 6.2 LTS can follow the transition discussion on daily.dev.