... simultaneous releases -- e.g. 3.2.x, 4.0.x, and, depending on timing, perhaps a 4.1.x. Regular version releases: either a final release (e.g. 4.1) or a bugfix update (e.g. 4.1.1). Pre-releases: e.g. 4.2 alpha, beta, or rc. The short version of the st ... Release entries for the next version in the admin on djangoproject.com . Add one for each milestone (alpha, beta, rc, and final), leaving is active unset to mark them as unreleased. Set target dates per the agreed schedule, and set the LTS flag if ap ... ccess to the production DB can still run an up-to-date copy of the docs site ( example PR ). This will be merged after the final release. Actually rolling the release ¶ OK, this is the fun part, where we actually push out a release! If you're issuing ... ... simultaneous releases -- e.g. 3.2.x, 4.0.x, and, depending on timing, perhaps a 4.1.x. Regular version releases: either a final release (e.g. 4.1) or a bugfix update (e.g. 4.1.1). Pre-releases: e.g. 4.2 alpha, beta, or rc. The short version of the st ... Release entries for the next version in the admin on djangoproject.com . Add one for each milestone (alpha, beta, rc, and final), leaving is active unset to mark them as unreleased. Set target dates per the agreed schedule, and set the LTS flag if ap ... ccess to the production DB can still run an up-to-date copy of the docs site ( example PR ). This will be merged after the final release. Actually rolling the release ¶ OK, this is the fun part, where we actually push out a release! If you're issuing ... ... e 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 transl ... able 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 b ... he 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). バグフィックスリリース ¶ フィーチャーリリース (たとえば、A.B) の後、最新のリリースはバグ ... ... e 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 transl ... able 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 b ... he 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). バグフィックスリリース ¶ フィーチャーリリース (たとえば、A.B) の後、最新のリリースはバグ ... ... れら 新しいバージョンの Django へのアップグレード では、後方互換性が無くなったすべての変更点と、現在使っているバージョンの 'final' リリースから新しいバージョンまでの各 'final' リリースで 廃止された機能 をチェックしてください。 Final リリース ¶ 以下のリ ... トが追加されます。 それ以外に、 公表されたセキュリティ上の問題のアーカイブ がメンテナンスされています。 目次 リリースノート Final リリース 6.1 release 6.0 release 5.2 リリース 5.1 リリース 5.0 リリース 4.2 リリース 4.1 リリース 4.0 リリース 3.2 リリース ... jango 6.1.3 release notes 関連キーワード Django リリースノート release リリース notes バージョン 後方 互換性 変更点 すべて final 公式 それぞれ アップグレード 現在 廃止 チェック Final リスト パッチ クイック検索 Last update: 2026年10月08日 « previous | ... ... れら 新しいバージョンの Django へのアップグレード では、後方互換性が無くなったすべての変更点と、現在使っているバージョンの 'final' リリースから新しいバージョンまでの各 'final' リリースで 廃止された機能 をチェックしてください。 Final リリース ¶ 以下のリ ... トが追加されます。 それ以外に、 公表されたセキュリティ上の問題のアーカイブ がメンテナンスされています。 目次 リリースノート Final リリース 6.1 release 6.0 release 5.2 リリース 5.1 リリース 5.0 リリース 4.2 リリース 4.1 リリース 4.0 リリース 3.2 リリース ... へ 用語集 次のトピックへ Django 6.1.3 release notes 関連キーワード リリースノート release リリース notes 後方 互換性 変更点 final 公式 アップグレード 廃止 チェック Final パッチ ドキュメント リリースノー クイック検索 Last update: 2026年10月09日 « previo ... ... fter Django 1.5 alpha 1 was tagged, the branch stable/1.5.x was created and all further work on preparing the code for the final 1.5 release was done there. These branches also provide bugfix and security support as described in サポートバージョン . F ... main repository branch. Thus, no new feature development work for the next release of Django could be committed until the final release happened. For example, shortly after the release of Django 1.3 the branch stable/1.3.x was created. Official suppo ... history generic-auth multiple-db-support per-object-permissions schema-evolution schema-evolution-ng search-api sqlalchemy Finally, under the archive/ prefix, the repository contains soc20XX/<project> tags referencing the tip of branches that were use ... ... fter Django 1.5 alpha 1 was tagged, the branch stable/1.5.x was created and all further work on preparing the code for the final 1.5 release was done there. These branches also provide bugfix and security support as described in サポートバージョン . F ... main repository branch. Thus, no new feature development work for the next release of Django could be committed until the final release happened. For example, shortly after the release of Django 1.3 the branch stable/1.3.x was created. Official suppo ... history generic-auth multiple-db-support per-object-permissions schema-evolution schema-evolution-ng search-api sqlalchemy Finally, under the archive/ prefix, the repository contains soc20XX/<project> tags referencing the tip of branches that were use ... ... versions of Django ¶ Testing pre-releases is a great way to contribute to Django. Early testers help catch bugs before the final release, ensuring a smoother upgrade experience for everyone. Prerequisites ¶ Before testing a pre-release, it is importan ... ase. Reporting issues ¶ If you discover a bug, please report it via the Django issue tracker so it can be fixed before the final release. When creating the ticket, be sure to set the Django version field to the exact pre-release version you are testin ... ... issue in the recently-released Django 1.0.1; the packaging scripts used for Django 1.0.1 omitted some directories from the final release package, including one directory required by django.contrib.gis and part of Django's unit-test suite. Django 1.0.2 ... 2026年10月08日