... It contains the full source code for all Django releases, which you can browse online. The Git repository includes several branches : main contains the main in-development code which will become the next packaged release of Django. This is where most dev ... elopment activity is focused. stable/A.B.x are the branches where release preparation work happens. They are also used for bugfix and security releases which occur as necessary after ... ontributing to Django , which covers things like the preferred coding style and how to generate and submit a patch. Stable branches ¶ Django uses branches to prepare for releases of Django. Each major release series has its own stable branch. These branc ... ... It contains the full source code for all Django releases, which you can browse online. The Git repository includes several branches : main contains the main in-development code which will become the next packaged release of Django. This is where most dev ... elopment activity is focused. stable/A.B.x are the branches where release preparation work happens. They are also used for bugfix and security releases which occur as necessary after ... ontributing to Django , which covers things like the preferred coding style and how to generate and submit a patch. Stable branches ¶ Django uses branches to prepare for releases of Django. Each major release series has its own stable branch. These branc ... ... git checkout -b ticket_xxxxx upstream/main The -b flag creates a new branch for you locally. Don't hesitate to create new branches even for the smallest things - that's what they are there for. If instead you were working for a fix on the 1.4 branch, yo ... t base their work on such a branch, because their clone would become corrupt when you edit commits. There are also "public branches". These are branches other people are supposed to fork, so the history of these branches should never change. Good example ... s of public branches are the main and stable/A.B.x branches in the django/django repository. When you think your work is ready to be pulled int ... ... git checkout -b ticket_xxxxx upstream/main The -b flag creates a new branch for you locally. Don't hesitate to create new branches even for the smallest things - that's what they are there for. If instead you were working for a fix on the 1.4 branch, yo ... t base their work on such a branch, because their clone would become corrupt when you edit commits. There are also "public branches". These are branches other people are supposed to fork, so the history of these branches should never change. Good example ... s of public branches are the main and stable/A.B.x branches in the django/django repository. When you think your work is ready to be pulled int ... ... on recipients, and be sure to include the relevant CVE IDs. Attach all the relevant patches (targeting main and the stable branches), and sign the email text with the key you'll use for the release, with a command like: $ gpg --clearsign --digest-algo SH ... s. Make sure this gets noted in the release notes ( example commit ). Concrete examples for past feature release bootstrap branches: 5.2 bootstrap , 5.1 bootstrap , 5.0 bootstrap . Feature freeze tasks ¶ Remove empty sections from the release notes ( exa ... changes that you are releasing. Cleanup the release notes for this release. Make these changes in main and backport to all branches where the release notes for a particular version are located. For a feature release, remove the UNDER DEVELOPMENT header a ... ... on recipients, and be sure to include the relevant CVE IDs. Attach all the relevant patches (targeting main and the stable branches), and sign the email text with the key you'll use for the release, with a command like: $ gpg --clearsign --digest-algo SH ... s. Make sure this gets noted in the release notes ( example commit ). Concrete examples for past feature release bootstrap branches: 5.2 bootstrap , 5.1 bootstrap , 5.0 bootstrap . Feature freeze tasks ¶ Remove empty sections from the release notes ( exa ... changes that you are releasing. Cleanup the release notes for this release. Make these changes in main and backport to all branches where the release notes for a particular version are located. For a feature release, remove the UNDER DEVELOPMENT header a ... ... 4.1 4.0 3.1 3.0 2.1 2.0 1.10 1.9 1.8 1.7 1.6 1.5 1.4 1.3 Djangoソースコードレポジトリ 大局的な概要 The main branch Stable branches タグ How to release Django オーバービュー Prerequisites Pre-release tasks Feature freeze tasks Actually rolling the releas ... ... 4.1 4.0 3.1 3.0 2.1 2.0 1.10 1.9 1.8 1.7 1.6 1.5 1.4 1.3 Djangoソースコードレポジトリ 大局的な概要 The main branch Stable branches タグ How to release Django オーバービュー Prerequisites Pre-release tasks Feature freeze tasks Actually rolling the releas ... ... _99999 ...\> git push origin ticket_99999 プルリクエストは Django の GitHub ページ から作成できます。"Your recently pushed branches" の下にあなたのブランチが表示されているはずです。その下の "Compare & pull request" ボタンをクリックします。 このチュートリ ... ることができます。 すぐに始めたい場合（誰もあなたを責めません!）、 easy tickets without a branch や、 easy tickets that have branches which need improvement のリストを確認してみてください。テストを書くことに慣れている場合は、 easy tickets that need tests の ... ... _99999 ...\> git push origin ticket_99999 プルリクエストは Django の GitHub ページ から作成できます。"Your recently pushed branches" の下にあなたのブランチが表示されているはずです。その下の "Compare & pull request" ボタンをクリックします。 このチュートリ ... ることができます。 すぐに始めたい場合（誰もあなたを責めません!）、 easy tickets without a branch や、 easy tickets that have branches which need improvement のリストを確認してみてください。テストを書くことに慣れている場合は、 easy tickets that need tests の ... 2026年10月08日