# Django 5.2.9 - dokumentacja

# Django’s release process

## Oficjalne wydania

Od wersji 1.0, numerowanie wydań Django działa w ten sposób:

- Wersje są numerowane w formie `A.B` lub `A.B.C`.

- `A.B` jest numerem wersji wydania funkcjonalnego. Każda wersja będzie przeważnie kompatybilna wstecz z poprzednim wydaniem. Wyjątki od tej reguły będą wypisane w informacjach o wydaniu.

- `C` jest numerem wersji wydania łaty, który jest zwiększany przy wydaniach z naprawami błędów i bezpieczeństwa. Te wydania będą w stu procentach kompatybilne wstecz z poprzednim wydaniem łaty. Jedynym wyjątkiem jest sytuacja, gdy problem bezpieczeństwa lub utraty danych nie może zostać rozwiązany bez złamania kompatybilności wstecz. Jeśli tak się wydarzy, informacje o wydaniu będą zawierały szczegółowe instrukcje upgrade’u.

- Przed nowym wydaniem funkcjonalnym, zrobimy alphę, betę i wydania „release candidate”. Są one w formie `A.B alpha/beta/rc N`, co oznacza `N-tą` alphę/betę/„release candidate” wersji `A.B`.

W gicie każde wydanie Django będzie miało tag określający jego numer wersji, podpisany kluczem wydań Django. Dodatkowo każda seria wydań ma swoją własną gałąź, nazwaną `stable/A.B.x` i wydania bezpieczeństwa lub bugfiksów będą tworzone z tych gałęzi.

For more information about how the Django project issues new releases for security purposes, please see our security policies.

Wydanie funkcjonalne

  Wydania funkcjonalne (A.B, A.B+1, itd.) będą wypuszczane średnio co osiem miesięcy – szczegóły w procesie wydawniczym. Te wydania będą zawierały nowe funkcjonalności, udoskonalenia istniejących funkcjonalności i tym podobne.

Wydanie łaty

  Wydania łat (A.B.C, A.B.C+1, itp.) będą wypuszczane w miarę potrzeb, by naprawiać błędy i/lub problemy z bezpieczeństwem.

  Te wydania będą w stu procentach kompatybilne z powiązanym wydaniem funkcjonalnym, o ile nie jest to niemożliwe z powodów bezpieczeństwa lub aby zapobiec utracie danych. Więc odpowiedzią na pytanie „czy powinienem upgrade’ować się do ostatniego wydania łaty?” zawsze będzie „tak”.

Wydanie „long-term support”

  Niektóre wydania funkcjonalne będą oznaczone jako wydania „long-term support” (LTS). Te wydania będą otrzymywały poprawki bezpieczeństwa i utraty danych przez gwarantowany czas, zazwyczaj trzy lata.

  Na stronie pobierania znajdziesz wydania, które zostały wyznaczone do „long-term support”.

## Rytm wydań

Starting with Django 2.0, version numbers will use a loose form of semantic versioning such that each version following an LTS will bump to the next „dot zero” version. For example: 2.0, 2.1, 2.2 (LTS), 3.0, 3.1, 3.2 (LTS), etc.

SemVer makes it easier to see at a glance how compatible releases are with each other. It also helps to anticipate when compatibility shims will be removed. It’s not a pure form of SemVer as each feature release will continue to have a few documented backwards incompatibilities where a deprecation path isn’t possible or not worth the cost. Also, deprecations started in an LTS release (X.2) will be dropped in a non-dot-zero release (Y.1) to accommodate our policy of keeping deprecation shims for at least two feature releases. Read on to the next section for an example.

## Deprecation policy

A feature release may deprecate certain features from previous releases. If a feature is deprecated in feature release A.x, it will continue to work in all A.x versions (for all versions of x) but raise warnings. Deprecated features will be removed in the B.0 release, or B.1 for features deprecated in the last A.x feature release to ensure deprecations are done over at least 2 feature releases.

So, for example, if we decided to start the deprecation of a function in Django 4.2:

- Django 4.2 will contain a backwards-compatible replica of the function which will raise a `RemovedInDjango51Warning`.

- Django 5.0 (the version that follows 4.2) will still contain the backwards-compatible replica.

- Django 5.1 will remove the feature outright.

The warnings are silent by default. You can turn on display of these warnings with the `python -Wd` option.

A more generic example:

- X.0

- X.1

- X.2 LTS

- Y.0: Drop deprecation shims added in X.0 and X.1.

- Y.1: Drop deprecation shims added in X.2.

- Y.2 LTS: No deprecation shims dropped (while Y.0 is no longer supported, third-party apps need to maintain compatibility back to X.2 LTS to ease LTS to LTS upgrades).

- Z.0: Drop deprecation shims added in Y.0 and Y.1.

See also the Deprecating a feature guide.

## Supported versions

At any moment in time, Django’s developer team will support a set of releases to varying levels. See the supported versions section of the download page for the current state of support for each version.

- The current development branch `main` will get new features and bug fixes requiring non-trivial refactoring.

- Patches applied to the main branch must also be applied to the last feature release branch, to be released in the next patch release of that feature series, when they fix critical problems:

  - Security issues.

  - Data loss bugs.

  - Crashing bugs.

  - Major functionality bugs in new features of the latest stable release.

  - Regressions from older versions of Django introduced in the current release series.

  The rule of thumb is that fixes will be backported to the last feature release for bugs that would have prevented a release in the first place (release blockers).

- Security fixes and data loss bugs will be applied to the current main branch, the last two feature release branches, and any other supported long-term support release branches.

- Documentation fixes generally will be more freely backported to the last release branch. That’s because it’s highly advantageous to have the docs for the last release be up-to-date and correct, and the risk of introducing regressions is much less of a concern.

As a concrete example, consider a moment in time halfway between the release of Django 5.1 and 5.2. At this point in time:

- Features will be added to the development main branch, to be released as Django 5.2.

- Critical bug fixes will be applied to the `stable/5.1.x` branch, and released as 5.1.1, 5.1.2, etc.

- Security fixes and bug fixes for data loss issues will be applied to `main` and to the `stable/5.1.x`, `stable/5.0.x`, and `stable/4.2.x` (LTS) branches. They will trigger the release of `5.1.1`, `5.0.5`, `4.2.8`, etc.

- Documentation fixes will be applied to main, and, if easily backported, to the latest stable branch, `5.1.x`.

## Release process

Django uses a time-based release schedule, with feature releases every eight months or so.

After each feature release, the release manager will publish a timeline for the next feature release. The timeline for an upcoming feature release can be found in the corresponding wiki roadmap page, e.g. https://code.djangoproject.com/wiki/Version6.0Roadmap.

### Feature release schedule and stages

#### Active development / Pre-feature freeze

Work begins on the feature release `A.B` after the feature freeze of the previous release, i.e. when the `stable/A.B-1.x` branch is forked.

You can find the current branch under active development in the Django release process on Trac.

#### Feature freeze / Alpha release

All major and minor features, including deprecations and breaking changes, must be merged by the feature freeze. Any features not done by this point will be deferred to the next feature release.

At this point, the `stable/A.B.x` branch will be forked from `main`.

#### Non-release blocking bug fix freeze / Beta release

After the alpha, all bug fixes merged in `main` are also backported to `stable/A.B.x`. Refactors are backported at the discretion of the merger. Mergers will be more and more conservative with backports, to avoid introducing regressions.

In parallel to this phase, `main` can continue to receive new features, to be released in the `A.B+1` cycle.

#### Translation string freeze / Release candidate release

If there is still a consistent stream of release blockers coming in at the planned release candidate date, a beta 2 will be released to encourage further testing and the release candidate date will be pushed out ~1 month.

The release candidate marks the string freeze, and it happens at least two weeks before the final release. Translators can then submit updated translations for inclusion in the final release. After this point, new translatable strings must not be added.

After the release candidate, only release blockers and documentation fixes are backported.

#### Final release

Ideally, the final release will ship two weeks after the last release candidate.

If there are major bugs still being found 2 weeks after the release candidate, there will be a decision on how to proceed (likely another release candidate would be issued and the final release date will be pushed out).

### Bug-fix releases

After a feature release (e.g. A.B), the previous release will go into bugfix mode.

The branch for the previous feature release (e.g. `stable/A.B-1.x`) will include bugfixes. Critical bugs fixed on main must also be fixed on the bugfix branch; this means that commits need to cleanly separate bug fixes from feature additions. The developer who commits a fix to main will be responsible for also applying the fix to the current bugfix branch.