# Upgrade Django 2028

> **Heads up — new versioning scheme**
>
> Django 2028 is the first release under the annual, calendar-year cycle
> adopted in [DEP 20][dep20]. What would have been Django 7.0 is now
> Django 2028. Instead of X.Y version numbers, each release carries the
> year of its feature release: Django 2028, then Django 2029, and so on.
> 
> Each annual release gets three years of support: one year of bugfixes,
> followed by two years of security and data-loss fixes. Django 5.2 LTS
> (April 2025) and Django 6.2 LTS (April 2027) are the final releases
> under the old X.Y cycle.
> 
> See the [announcement blog post][blog] and [DEP 20 itself][dep20] for
> the full rationale and details.
> 
> [blog]: https://www.djangoproject.com/weblog/2026/aug/10/annual-release-cycle/
> [dep20]: https://github.com/django/deps/blob/main/accepted/0020-annual-release-cycle.rst

Source: https://upgradedjango.com/2028/