... の品質が期待通りのものであることを確認しましょう。準備ができたら次のようにします: / $ # Pull in the latest changes from main. $ git checkout main $ git pull upstream main $ # Rebase the pull request on main. $ git checkout pr/#### $ git rebase mai ... n $ git checkout main $ # Merge the work as "fast-forward" to main to avoid a merge commit. $ # (in practice, you can omit "--ff-only" since you ... did things correctly, check that only the $ # changes you expect will be pushed to upstream. $ git push --dry-run upstream main $ # Push! $ git push upstream main $ # Delete the pull request branch. $ git branch -d pr/xxxx ...\> REM Pull in the lates ... ... の品質が期待通りのものであることを確認しましょう。準備ができたら次のようにします: / $ # Pull in the latest changes from main. $ git checkout main $ git pull upstream main $ # Rebase the pull request on main. $ git checkout pr/#### $ git rebase mai ... n $ git checkout main $ # Merge the work as "fast-forward" to main to avoid a merge commit. $ # (in practice, you can omit "--ff-only" since you ... did things correctly, check that only the $ # changes you expect will be pushed to upstream. $ git push --dry-run upstream main $ # Push! $ git push upstream main $ # Delete the pull request branch. $ git branch -d pr/xxxx ...\> REM Pull in the lates ... ... 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 developmen ... rchived work . The source code for the Djangoproject.com website can be found at github.com/django/djangoproject.com . The main branch ¶ If you'd like to try out the in-development code for the next release of Django, or if you'd like to contribute t ... o Django by fixing bugs or developing new features, you'll want to get the code from the main branch. 注釈 Prior to March 2021, the main branch was called master . Note that this will get all of Django: in addition t ... ... 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 developmen ... rchived work . The source code for the Djangoproject.com website can be found at github.com/django/djangoproject.com . The main branch ¶ If you'd like to try out the in-development code for the next release of Django, or if you'd like to contribute t ... o Django by fixing bugs or developing new features, you'll want to get the code from the main branch. 注釈 Prior to March 2021, the main branch was called master . Note that this will get all of Django: in addition t ... ... jango.git Working on a ticket ¶ When working on a ticket, create a new branch for the work, and base that work on upstream/main : git checkout -b ticket_xxxxx upstream/main The -b flag creates a new branch for you locally. Don't hesitate to create ne ... eople are supposed to fork, so the history of these branches should never change. Good examples 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 into Django, you ... stream ( django/django ) has changed, you should rebase your work. To do this, use: git fetch upstream git rebase upstream/main The work is automatically rebased using the branch you forked on, in the example case using upstream/main . The rebase com ... ... ouncements. Update version numbers post-release in stable branch(es). Add stub release notes for the next patch release in main and backport. There are a lot of details, so please read on. Use the checklists app To generate a checklist compiling the ... t_hostname = https://rest.api.transifex.com token = # API token Access to the Django admin on djangoproject.com as a "Site maintainer". Access to create a post in the Django Forum - Announcements category and to send emails to the django-announce mai ... rve: $ cve --interactive reserve <quantity> Generate the relevant (private) patch(es) using git format-patch , one for the main branch and one for each stable branch being patched. A week before a security release ¶ Send out pre-notification exactly ... ... ouncements. Update version numbers post-release in stable branch(es). Add stub release notes for the next patch release in main and backport. There are a lot of details, so please read on. Use the checklists app To generate a checklist compiling the ... t_hostname = https://rest.api.transifex.com token = # API token Access to the Django admin on djangoproject.com as a "Site maintainer". Access to create a post in the Django Forum - Announcements category and to send emails to the django-announce mai ... rve: $ cve --interactive reserve <quantity> Generate the relevant (private) patch(es) using git format-patch , one for the main branch and one for each stable branch being patched. A week before a security release ¶ Send out pre-notification exactly ... ... jango.git Working on a ticket ¶ When working on a ticket, create a new branch for the work, and base that work on upstream/main : git checkout -b ticket_xxxxx upstream/main The -b flag creates a new branch for you locally. Don't hesitate to create ne ... eople are supposed to fork, so the history of these branches should never change. Good examples 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 into Django, you ... stream ( django/django ) has changed, you should rebase your work. To do this, use: git fetch upstream git rebase upstream/main The work is automatically rebased using the branch you forked on, in the example case using upstream/main . The rebase com ... ... の サポートバージョンのセクション にある、各バージョンに対する現在のサポート状況のリストを見てください。 現在の開発ブランチ main は、大規模なリファクタリングを必要とする新機能とバグ修正を受け取ります。 メインブランチに適用されたパッチは、重大な問題を修 ... 5.1.x ブランチに適用され、5.1.1、5.1.2 などとしてリリースされます。 データ損失の問題に対するセキュリティ修正とバグ修正は、 main と stable/5.1.x 、 stable/5.0.x 、そして stable/4.2.x (LTS) のブランチに適用されます。これらは 5.1.1 、 5.0.5 、 4.2.8 など ... をリリースします。 ドキュメントの修正は、main に適用され、容易にバックポート可能であれば、最新の安定ブランチ 5.1.x にも適用されます。 リリースプロセス ¶ Django は期間に ... ... の サポートバージョンのセクション にある、各バージョンに対する現在のサポート状況のリストを見てください。 現在の開発ブランチ main は、大規模なリファクタリングを必要とする新機能とバグ修正を受け取ります。 メインブランチに適用されたパッチは、重大な問題を修 ... 5.1.x ブランチに適用され、5.1.1、5.1.2 などとしてリリースされます。 データ損失の問題に対するセキュリティ修正とバグ修正は、 main と stable/5.1.x 、 stable/5.0.x 、そして stable/4.2.x (LTS) のブランチに適用されます。これらは 5.1.1 、 5.0.5 、 4.2.8 など ... をリリースします。 ドキュメントの修正は、main に適用され、容易にバックポート可能であれば、最新の安定ブランチ 5.1.x にも適用されます。 リリースプロセス ¶ Django は期間に ... 2026年10月08日