Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Django] Display release date column #2180

Merged
merged 2 commits into from
Dec 30, 2022
Merged

[Django] Display release date column #2180

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
8837db1
[Django] Normalize page (#2124)
marcwrobel Dec 29, 2022
58f0eeb
[Django] Display release date column
marcwrobel Dec 29, 2022
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
51 changes: 32 additions & 19 deletions products/django.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -3,25 +3,29 @@ title: Django
category: framework
iconSlug: django
permalink: /django
versionCommand: python -c "import django; print(django.get_version())"
releasePolicyLink: https://www.djangoproject.com/download/#supported-versions
releaseImage: https://static.djangoproject.com/img/release-roadmap.3c7ece4f31b3.png
changelogTemplate: https://docs.djangoproject.com/en/__RELEASE_CYCLE__/releases/__LATEST__/
activeSupportColumn: true
versionCommand: python -c "import django; print(django.get_version())"
releaseDateColumn: false
auto:
- git: https://github.com/django/django.git
releaseDateColumn: true

identifiers:
- repology: python:django
- purl: pkg:github/django/django
- purl: pkg:pypi/django

auto:
- git: https://github.com/django/django.git

releases:
- releaseCycle: "4.1"
support: 2023-04-01
eol: 2023-12-01
latest: "4.1.4"
latestReleaseDate: 2022-12-06
releaseDate: 2022-08-03

- releaseCycle: "4.0"
support: 2022-08-01
eol: 2023-04-01
Expand Down Expand Up @@ -83,24 +87,33 @@ releases:

---

> [Django](https://www.djangoproject.com/) is a high-level Python Web framework that encourages rapid development and clean, pragmatic design.
> [Django](https://www.djangoproject.com/) is a high-level Python Web framework that encourages
> rapid development and clean, pragmatic design.

Django Release|Supported Python Versions
--------------|-------------------------
4.0 |3.8 ≥ 3.10
3.2 |3.6 ≥ 3.10
2.2 |3.5 ≥ 3.9
2.0 |3.4 ≥ 3.7
1.11.x |2.7 , 3.4 ≥ 3.7
| Django Release | Supported Python Versions |
|----------------|---------------------------|
| 4.0 | 3.8 ≥ 3.10 |
| 3.2 | 3.6 ≥ 3.10 |
| 2.2 | 3.5 ≥ 3.9 |
| 2.0 | 3.4 ≥ 3.7 |
| 1.11.x | 2.7 , 3.4 ≥ 3.7 |

Not all releases in a series will support all Python versions, the matrix above is for the latest patch release.
[For more up-to-date info](https://docs.djangoproject.com/en/4.0/faq/install/#what-python-version-can-i-use-with-django)
Not all releases in a series will support all Python versions, the matrix above is for the latest
patch release. [For more up-to-date info](https://docs.djangoproject.com/en/4.0/faq/install/#what-python-version-can-i-use-with-django).

**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. These can include documented backwards incompatibilities where a deprecation path isn’t possible or not worth the cost.
**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. These can include documented
backwards incompatibilities where a deprecation path isn’t possible or not worth the cost.

**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."
**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."

The last feature release for a major version will be designated as long-term support (LTS) release. These releases will get security and data loss fixes applied for a guaranteed period of time, typically three years. Deprecations started in an LTS release (say X.2) will be dropped in a non-dot-zero release (Y.1).
The last feature release for a major version will be designated as long-term support (LTS) release.
These releases will get security and data loss fixes applied for a guaranteed period of time,
typically three years. Deprecations started in an LTS release (say X.2) will be dropped in a
non-dot-zero release (Y.1).

See the [supported versions policy](https://docs.djangoproject.com/en/dev/internals/release-process/#supported-versions) for detailed guidelines about what fixes will be backported.
.
See the [supported versions policy](https://docs.djangoproject.com/en/dev/internals/release-process/#supported-versions)
for detailed guidelines about what fixes will be backported.