Django is transitioning to an annual release cycle starting January 2028, with all feature releases receiving three years of support. This new model aligns better with Python's annual release schedule, ending Django's previous issue of supporting outdated Python versions. Each new Django release will support the three most recent Python versions available at that time. The distinction between regular and Long-Term Support (LTS) releases is being retired, as all feature releases will now have an LTS-level commitment. This change eliminates the need for users to undertake large, infrequent upgrades by allowing them to update annually. Three Django versions will be supported concurrently, providing a predictable target for third-party package developers. API stability and deprecation policies remain consistent, with deprecation periods effectively extended. The first release under this new cycle will be Django 2028. Current support commitments for Django 5.2 LTS and 6.2 LTS will remain in effect. The full details and reasoning are available in DEP 20.