The Django web framework project has accepted a proposal to transition to an annual major release cycle, moving away from what the project describes as a "somewhat complicated" previous schedule.
Under the new model, one major version will be released each year. Each release will receive three years of support: one year of mainstream bug fixes followed by two years of security and data-loss fixes. The previous Long-Term Support (LTS) designation is being retired; instead, all feature releases will receive the same uniform three-year support window. At any given time, three versions will be supported, giving third-party package authors a clear, rolling compatibility target.
The first release under the new schedule will be Django 2028, expected in January 2028. The proposal was formally accepted and documented through the project's Django Enhancement Proposal process.
Third-party package maintainers previously had to track and synchronize work across multiple concurrent release branches. The shift to a single annual cadence with uniform support periods is expected to simplify this compatibility work by providing a more consistent and predictable framework for planning upgrades and maintaining extensions.
The annual cycle aligns the project with a calendar-driven release philosophy, offering organizations a clearer timeline for planning deployment and upgrade cycles. Teams currently running Django in production are encouraged to review the updated release schedule and adjust their upgrade strategies to match the new three-year support windows.
Django 網頁框架項目已接受一項提案，將過渡至年度主要版本發布週期，擺脫項目描述為「相當複雜」的過往排程。
根據新模式，每年將發布一個主要版本。每個版本將獲得三年支援：首年提供主流錯誤修正，隨後兩年提供安全及資料遺失修正。過往的長期支援指定將被淘汰；取而代之的是，所有功能版本將獲得相同的統一三年支援窗口。在任何時間點，將會有三個版本同時獲得支援，為第三方套件作者提供一個明確且持續滾動的相容性目標。
新模式下的首個版本將是 Django 2028，預計於 2028 年 1 月推出。該提案已透過項目的 Django 增強提案流程正式通過並記錄在案。
第三方套件維護者此前必須跨多個並行發布分支進行追蹤和同步工作。轉向統一的年度節奏及支援週期，預計將透過提供一個更一致且可預測的框架，來簡化這項相容性工作，以便規劃升級和維護擴充套件。
此年度週期使項目與日曆驅動的發布理念保持一致，為機構提供更清晰的時間表，以規劃部署和升級週期。鼓勵目前在生產環境中使用 Django 的團隊檢視更新後的發布排程，並調整其升級策略以配合新的三年支援窗口。