Skip to content
Permalink
Branch: master
Find file Copy path
Find file Copy path
Fetching contributors…
Cannot retrieve contributors at this time
43 lines (37 sloc) 1.82 KB
title layout permalink link releaseImage changelogTemplate activeSupportColumn command releaseDateColumn sortReleasesBy releases
Django
post
/django
true
python -c "import django; print(django.get_version())"
false
releaseCycle
releaseCycle lts support eol latest
2.2
true
2019-12-01
2022-04-01
2.2.3
releaseCycle support eol latest
2.1
2019-04-01
2019-12-01
2.1.9
releaseCycle support eol latest lts
2.0
2018-08-01
2019-04-01
2.0.13
false
releaseCycle lts support eol latest
1.11
true
2017-12-02
2020-04-01
1.11.21

Django is a high-level Python Web framework that encourages rapid development and clean, pragmatic design.

Feature releases (A.B, A.B+1, etc.) will happen roughly every eight months. These releases will contain new features, improvements to existing features, and such.

Patch releases (A.B.C, etc.) will be issued as needed, to fix bugs and/or security issues. These releases will be 100% compatible with the associated feature release, unless this is impossible for security reasons or to prevent data loss. So the answer to "should I upgrade to the latest patch release?” will always be "yes."

Certain feature releases will be designated as long-term support (LTS) releases. These releases will get security and data loss fixes applied for a guaranteed period of time, typically three years.

See the supported versions policy for detailed guidelines about what fixes will be backported.

You can’t perform that action at this time.