--- title: Django moves to an annual release cycle | daily.dev description: Django has officially adopted an annual release cycle, replacing its previous schedule that mixed short-lived feature releases with LTS releases. Under the new... canonical: https://daily.dev/posts/django-moves-to-an-annual-release-cycle-igrml3fxn twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: Django moves to an annual release cycle | daily.dev og:description: Django has officially adopted an annual release cycle, replacing its previous schedule that mixed short-lived feature releases with LTS releases. Under the new... og:url: https://daily.dev/posts/django-moves-to-an-annual-release-cycle-igrml3fxn og:image: https://api.daily.dev/og/posts/igrmL3FXn.png og:image:alt: Django moves to an annual release cycle og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # Django moves to an annual release cycle **[LWN.net](https://daily.dev/sources/lwn)** · 1 min read · 0 upvotes · 0 comments ## Summary Django has officially adopted an annual release cycle, replacing its previous schedule that mixed short-lived feature releases with LTS releases. Under the new model, every feature release receives three years of support: one year of mainstream bugfixes followed by two years of security and data-loss fixes. The LTS label is being retired since all releases now carry the same support commitment. This means three versions will always be supported simultaneously, giving third-party package maintainers a predictable rolling target. The change takes effect with the Django 2028 release, expected in January 2028. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### What is Django's new release cycle and how long will each release be supported? Starting with Django 2028, every feature release will be supported for three years: one year of mainstream bugfixes, then two years of security and data-loss fixes. The LTS label is retired because all releases now carry the same support commitment. Three versions will be supported simultaneously at any time, allowing one-year incremental upgrades instead of large multi-version jumps. _Python teams planning upgrade schedules around Django versions track policy changes like this on daily.dev._ ### When does Django's annual release cycle take effect? The annual release cycle takes effect with the Django 2028 release, expected in January 2028. Prior to this, Django used a more complex schedule that interleaved short-lived feature releases with designated long-term-support releases on a roughly eight-month cadence. _Developers maintaining Django projects can follow release timeline news on daily.dev to plan migrations without surprises._ ## Similar posts on daily.dev - [Issue 350: Django moves to an annual release cycle](https://daily.dev/posts/issue-350-django-moves-to-an-annual-release-cycle-ulipqy5ir) · Django News · 0 upvotes · 0 comments - [Twenty years of Django releases](https://daily.dev/posts/twenty-years-of-django-releases-ez74qwfdd) · Django · 4 upvotes · 0 comments - [Django 6.0 released\!](https://daily.dev/posts/django-6-0-released--hlksa4vxz) · Django News · 0 upvotes · 0 comments --- Tags: [#python](https://daily.dev/tags/python), [#django](https://daily.dev/tags/django) [View this post on daily.dev](https://daily.dev/posts/django-moves-to-an-annual-release-cycle-igrml3fxn) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"TechArticle","headline":"Django moves to an annual release cycle","url":"https://daily.dev/posts/django-moves-to-an-annual-release-cycle-igrml3fxn","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/django-moves-to-an-annual-release-cycle-igrml3fxn"},"datePublished":"2026-08-10T13:34:04.963Z","dateModified":"2026-08-10T13:35:00.555Z","description":"Django has officially adopted an annual release cycle, replacing its previous schedule that mixed short-lived feature releases with LTS releases. Under the new...","image":"https://media.daily.dev/image/upload/s--CxzD6vbw--/f_auto/v1722860399/public/Placeholder%2005","thumbnailUrl":"https://media.daily.dev/image/upload/s--CxzD6vbw--/f_auto/v1722860399/public/Placeholder%2005","isAccessibleForFree":true,"articleSection":"LWN.net","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"LWN.net","logo":"https://media.daily.dev/image/upload/s--4jjE7GIK--/f_auto,q_auto/v1774960833/logos/lwn?_a=BAMAMiWQ0","url":"https://daily.dev/sources/lwn"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/django-moves-to-an-annual-release-cycle-igrml3fxn","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"python,django","timeRequired":"PT1M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"LWN.net","item":"https://daily.dev/sources/lwn"},{"@type":"ListItem","position":3,"name":"Django moves to an annual release cycle"}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/django-moves-to-an-annual-release-cycle-igrml3fxn#faq","mainEntity":[{"@type":"Question","name":"What is Django's new release cycle and how long will each release be supported?","acceptedAnswer":{"@type":"Answer","text":"Starting with Django 2028, every feature release will be supported for three years: one year of mainstream bugfixes, then two years of security and data-loss fixes. The LTS label is retired because all releases now carry the same support commitment. Three versions will be supported simultaneously at any time, allowing one-year incremental upgrades instead of large multi-version jumps. Python teams planning upgrade schedules around Django versions track policy changes like this on daily.dev."}},{"@type":"Question","name":"When does Django's annual release cycle take effect?","acceptedAnswer":{"@type":"Answer","text":"The annual release cycle takes effect with the Django 2028 release, expected in January 2028. Prior to this, Django used a more complex schedule that interleaved short-lived feature releases with designated long-term-support releases on a roughly eight-month cadence. Developers maintaining Django projects can follow release timeline news on daily.dev to plan migrations without surprises."}}]} ```