这份文档解释了如何发布 Django。
\n请在进行更改时保持这些说明的最新状态！ 这里的重点是描述性的，而不是规范性的，所以请随意简化或进行其他更改，但 相应地更新这份文档！
\n有三种类型的发布可能需要进行：
\n安全性发布：揭示和修复漏洞。这通常涉及到两个或三个同时发布的版本，例如 3.2.x、4.0.x，根据时间的安排，可能还包括 4.1.x。
常规版本发布：可以是最终发布（例如 4.1）或错误修复更新（例如 4.1.1）。
预发布版本：例如 4.2 alpha、beta 或 rc。
涉及的步骤的简短版本是：
\n如果这是一个安全性发布，请在实际发布前一周预先通知安全性发布列表。
校对发布说明，查找组织和写作错误。起草一篇博客文章和电子邮件公告。
Update version numbers and create the release artifacts.
Create the new Release in the admin on djangoproject.com.
Set the proper date but ensure the flag is_active is disabled.
Upload the artifacts (tarball, wheel, and checksums).
验证包的签名，检查它们是否可以安装，并确保最小功能可用。
将新版本上传到 PyPI。
Enable the is_active flag for each release in the admin on\ndjangoproject.com.
发布博客文章并发送电子邮件公告。
Update version numbers post-release in stable branch(es).
Add stub release notes for the next patch release in main and backport.
有很多细节，请继续阅读。
\n\n在开始之前，你需要准备一些东西。如果这是你第一次发布，你需要与另一位发布者协调，确保所有事项都准备妥当，并写信给 Ops 邮件列表，请求所需的访问权限和许可。
\n一个安装了以下工具的 Unix 环境（按字母顺序排列）：
\nbash (version 4.0+)
git
GPG
make
man
哈希工具（通常在 Linux 上是 md5sum、sha1sum 和 sha256sum，在 macOS 上是 md5 和 shasum）
python
A GPG key pair. Securely store the private part, and protect it with a\npassphrase. The public part needs to be uploaded to your GitHub account.
\n\nA clean Python virtual environment (Python 3.10+, pip 26.1+) to build\nartifacts.
Access to Django's project on PyPI to\nupload binaries, ideally with extra permissions to yank a release if necessary. Ensure your PyPI account\nonly uses WebAuthn-based authentication factors, not TOTP (one-time codes).\nCreate an API token following the official documentation, and set up your $HOME/.pypirc file\nlike this:
~/.pypirc[distutils]\n index-servers =\n pypi\n django\n\n[pypi]\n username = __token__\n password = # User-scoped or project-scoped token, to set as the default.\n\n[django]\n repository = https://upload.pypi.org/legacy/\n username = __token__\n password = # A project token.\nAccess to Django's project on Transifex, with a Manager role. Generate\nan API Token in the user setting section and set up your\n$HOME/.transifexrc file like this:
~/.transifexrc[https://www.transifex.com]\n rest_hostname = https://rest.api.transifex.com\n token = # API token\n作为“站点维护者”访问 djangoproject.com 上的 Django 管理界面。
Access to create a post in the Django Forum - Announcements category and to send emails to\nthe django-announce\nmailing list.
访问 GitHub 中的 django-security 仓库。除其他事项外，这提供了对预通知分发列表的访问权限（安全发布准备任务所需）。
Access to the Django project on Read the Docs.
在开始发布过程之前，需要处理一些事项。这些工作大约在发布前一周开始；大部分工作可以在实际发布前的任何时间完成。
\nReserve one CVE ID per security\nissue as follows. (Or, if you lack CNA credentials, email\ncna@djangoproject.com with a request.)
Enable virtual environment with cvelib installed.
Export user information:
\n$ export CVE_USER=<user-email>@djangoproject.com CVE_ORG=DSF\nReserve:
\n$ cve --interactive reserve <quantity>\n使用 git format-patch 生成相关的（私有）补丁，一个用于 main 分支，一个用于每个正在修补的稳定分支。
Send out pre-notification exactly one week before the security release.\nThe template for that email and a list of the recipients are in the private\ndjango-security GitHub wiki. BCC the pre-notification recipients, and be\nsure to include the relevant CVE IDs. Attach all the relevant patches\n(targeting main and the stable branches), and sign the email text with\nthe key you'll use for the release, with a command like:
$ gpg --clearsign --digest-algo SHA256 prenotification-email.txt\n通知 django-announce 即将发布的安全版本，使用如下一般消息：
\nNotice of upcoming Django security releases (3.2.24, 4.2.10 and 5.0.2)\n\nDjango versions 5.0.2, 4.2.10, and 3.2.24 will be released on Tuesday,\nFebruary 6th, 2024 around 1500 UTC. They will fix one security defect\nwith severity "moderate".\n\nFor details of severity levels, see:\nhttps://docs.djangoproject.com/en/dev/internals/security/#how-django-discloses-security-issues\nPrepare issue metadata:\n* Severity\n* Short description\n* Reporter\n* Remediator\n* Reported at\n* Confirmed at (usually date CVE reserved)\n* CWE Problem Type\n* CAPEC Impact Type\n* CVSS (4.0) Score & Vector
As the release approaches, watch Trac to make sure no release blockers are\nleft for the upcoming release. Under exceptional circumstances, such as to\nmeet a pre-determined security release date, a release could still go ahead\nwith an open release blocker. The releaser is trusted with the decision to\nrelease with an open release blocker or to postpone the release date of a\nnon-security release if required.
与其他合并人员核对，确保他们没有为发布而提交的未提交更改。
校对发布说明，包括查看在线版本以 捕捉任何损坏的链接 或 reST 错误，并确保发布说明包含正确的日期。
再次确认发布说明中提到了任何已经标记为弃用的 API 的弃用时间表，并且提到了对 Python 版本支持的任何更改。
再次检查发布说明索引中是否有指向新发布版本说明的链接；这将在 docs/releases/index.txt 中。
If this is a feature release, ensure translations from Transifex\nhave been integrated.
\nIn addition to having a configured Transifex account, ensure that the tx\nCLI is available in your\nPATH. You can then fetch all translations since a given date by running:
$ python scripts/manage_translations.py fetch -v 1 --since=<some date>\nTo determine a good value for --since, check the date of the most recent\ncommit with wording similar to Updated translations from Transifex and\nuse a date a few days prior.
此命令需要一些时间运行。完成后，仔细检查输出以查找潜在的错误和/或警告。如果有，你需要逐个调试并解决它们。
\n最近获取的翻译需要一些手动调整。首先，PO-Revision-Date 值必须手动更新为晚于 POT-Creation-Date。你可以使用类似于以下的命令批量更新所有 .po 文件（与相关稳定分支进行比较）：
$ git diff --name-only stable/5.0.x | grep "\\.po" | xargs sed -ri "s/PO-Revision-Date: [0-9\\-]+ /PO-Revision-Date: $(date -I) /g"\nLastly, commit the changed/added files (both .po and .mo) and create\na new PR targeting the stable branch of the corresponding release (example\nPR updating translations for 4.2).
Once merged, forward port the changes into main (example commit).
$ cd docs\n$ make man\n$ man _build/man/django-admin.1 # do a quick sanity check\n$ cp _build/man/django-admin.1 man/django-admin.1\n然后提交已更改的手册页面。
\nIf this is the "dot zero" release of a new series, create a new branch from\nthe current stable branch in the django-docs-translations repository. For\nexample, when releasing Django 4.2:
\n$ git checkout -b stable/4.2.x origin/stable/4.1.x\n$ git push origin stable/4.2.x:stable/4.2.x\n为发布撰写公告博客文章。你可以随时输入它到管理员界面并将其标记为非活动状态。以下是一些示例：示例安全发布公告、示例常规发布公告、示例预发布公告。
In preparation for the alpha release, the directory\n/home/www/www/media/releases/A.B must be created on the djangoproject\nserver.
Before the feature freeze, a branch targeting main must be created to\nprepare for the next feature release. It should be reviewed and approved a few\ndays before the freeze, allowing it to be merged after the stable branch is\ncut. The following items should be addressed in this branch:
Update the VERSION tuple in django/__init__.py, incrementing to the\nnext expected release (example commit).
Create a stub release note for the next feature release. Use the stub from\nthe previous feature release or copy the contents from the current version\nand delete most of the contents leaving only the headings\n(example commit).
Remove .. versionadded:: and .. versionchanged:: annotations in the\ndocumentation from two releases ago, as well as any remaining older\nannotations. For example, in Django 5.1, notes for 4.2 will be removed\n(example commit).
Remove features that have reached the end of their deprecation cycle,\nincluding their docs and the .. deprecated:: annotation. Each removal\nshould be done in a separate commit for clarity. In the commit message, add\na Refs #XXXXX -- prefix linking to the original ticket where the\ndeprecation began if possible. Make sure this gets noted in the removed\nfeatures section in the release notes (example commit).
Advance the deprecation warnings (example commit).
Increase the default PBKDF2 iterations in\ndjango.contrib.auth.hashers.PBKDF2PasswordHasher by about 20%\n(pick a round number). Run the tests, and update the 3 failing\nhasher tests with the new values. Make sure this gets noted in the\nrelease notes (example commit).
Concrete examples for past feature release bootstrap branches: 5.2 bootstrap, 5.1 bootstrap, 5.0 bootstrap.
\nRemove empty sections from the release notes (example commit).
Build the release notes locally and read them. Make any necessary change\nto improve flow or fix grammar (example commit).
Create a new stable branch from main. Be sure to fetch and update\nupstream to latest. For example, when feature freezing Django 5.2:
$ git fetch upstream\n$ git checkout -b stable/5.2.x upstream/main\n$ git push upstream -u stable/5.2.x:stable/5.2.x\nAt the same time, update the django_next_version variable in\ndocs/conf.py on the stable release branch to point to the new\ndevelopment version. For example, when creating stable/5.2.x, set\ndjango_next_version to '6.0' on the new stable branch\n(example commit).
Create Release entries for the next version in the admin on\ndjangoproject.com. Add one for each milestone (alpha, beta, rc, and\nfinal), leaving is active unset to mark them as unreleased. Set target\ndates per the agreed schedule, and set the LTS flag if applicable. The\nX.Y roadmap page will be available at /download/X.Y/roadmap/.
For example, when creating stable/5.2.x, add Release entries for\n6.0a1, 6.0b1, 6.0rc1, and 6.0. The 6.0 roadmap can be\nthen reviewed at https://www.djangoproject.com/download/6.0/roadmap/.
Go to the Add document release page in the admin, create a new\nDocumentRelease object for the English language for the newly created\nRelease object. Do not mark this as default.
Add the new branch to Read the Docs. Since the automatically\ngenerated version names ("stable-A.B.x") differ from the version names used\nin Read the Docs ("A.B.x"), update the Read the Docs config for the version\nto point to the slug A.B.x and set it as active. See more details.
Create a PR on PyPI proposing the new Trove classifier.\nFor example Framework :: Django :: 5.2.
Update the current branch under active development and add pre-release\nbranch in the Django release process on Trac.
Update the docs/fixtures/doc_releases.json JSON fixture for\ndjangoproject.com, so people without access to the production DB can still\nrun an up-to-date copy of the docs site\n(example PR).\nThis will be merged after the final release.
好的，这是有趣的部分，我们实际上要发布一个版本！如果你要发布 多个版本，请为每个版本重复这些步骤。
\n检查 Jenkins 是否为你要发布的版本显示绿色。在它变绿之前，你可能不应该发布版本，并且你应该确保最新的绿色运行包括你要发布的更改。
\n清理此版本的发布说明。在 main 中进行这些更改，并向后移植到特定版本发布说明所在的所有分支。
Regenerate a fresh, dedicated virtual environment for the release tools\nusing a cooldown:
\n$ python -m pip install build twine --uploaded-prior-to=P7D\nA release always begins from a release branch, so you should make sure\nyou're on an up-to-date stable branch. For example:
\n$ git checkout stable/4.1.x\n$ git pull\n如果这是一个安全发布，请从 django-security 合并适当的补丁。根据需要重新基于这些补丁，使每个补丁都成为发布分支上的普通提交，而不是合并提交。为了确保这一点，使用 --ff-only 标志合并它们，例如：
$ git checkout stable/4.1.x\n$ git merge --ff-only security/4.1.x\n（这假设 security/4.1.x 是 django-security 存储库中包含下一个 4.1 系列发布所需的安全补丁的分支。）
如果 git 拒绝使用 --ff-only 合并，请切换到 security-patch 分支，并在你将要合并的分支上重新基于它（git checkout security/4.1.x; git rebase stable/4.1.x），然后切换回来并执行合并操作。确保每个安全修复的提交消息解释了这个提交是一个安全修复，并且会有一个公告随后发布（示例安全提交）。
在 django/__init__.py 中更新发布版本的版本号。有关 VERSION 的详细信息，请参阅下面的 设置 VERSION 元组的注意事项`_（:commit:`示例提交 <2719a7f8c161233f45d34b624a9df9392c86cc1b>）。
If this is a pre-release package also update the "Development Status"\ntrove classifier in pyproject.toml to reflect this. An rc\npre-release should not change the trove classifier (example\ncommit for alpha release,\nexample commit for beta release).
否则，确保分类器设置为 Development Status :: 5 - Production/Stable。
使用 git tag 标记发布。例如：
$ git tag --sign --message="Tag 4.1.1" 4.1.1\n你可以通过运行 git tag --verify <tag> 来检查你的工作。
确保你的代码库是绝对干净的，通过运行 git clean -dfx。
Run python -m build to generate the release packages. This will create\nthe release artifacts (tarball and wheel) in a dist/ directory.
生成发布包的哈希值：
\n$ cd dist\n$ md5sum *\n$ sha1sum *\n$ sha256sum *\n创建一个名为 Django-<<VERSION>>.checksum.txt 的 "checksums" 文件，其中包含哈希值和发布信息。使用以下模板，并插入正确的版本、日期、GPG 密钥 ID（从 gpg --list-keys --keyid-format LONG 获取）、发布管理器的 GitHub 用户名、发布 URL 和哈希值：
This file contains MD5, SHA1, and SHA256 checksums for the source-code\ntarball and wheel files of Django <<VERSION>>, released <<DATE>>.\n\nTo use this file, you will need a working install of PGP or other\ncompatible public-key encryption software. You will also need to have\nthe Django release manager's public key in your keyring. This key has\nthe ID ``XXXXXXXXXXXXXXXX`` and can be imported from GitHub, for example,\nif using the open-source GNU Privacy Guard implementation of PGP:\n\n curl https://github.com/<<RELEASE MANAGER GITHUB USERNAME>>.gpg | gpg --import -\n\nOnce the key is imported, verify this file:\n\n gpg --verify <<THIS FILENAME>>\n\nOnce you have verified this file, you can use normal MD5, SHA1, or SHA256\nchecksumming applications to generate the checksums of the Django\npackage and compare them to the checksums listed below.\n\nRelease packages\n================\n\nhttps://www.djangoproject.com/download/<<VERSION>>/tarball/\nhttps://www.djangoproject.com/download/<<VERSION>>/wheel/\n\nMD5 checksums\n=============\n\n<<MD5SUM>> <<RELEASE TAR.GZ FILENAME>>\n<<MD5SUM>> <<RELEASE WHL FILENAME>>\n\nSHA1 checksums\n==============\n\n<<SHA1SUM>> <<RELEASE TAR.GZ FILENAME>>\n<<SHA1SUM>> <<RELEASE WHL FILENAME>>\n\nSHA256 checksums\n================\n\n<<SHA256SUM>> <<RELEASE TAR.GZ FILENAME>>\n<<SHA256SUM>> <<RELEASE WHL FILENAME>>\n签名 "checksum" 文件（gpg --clearsign --digest-algo SHA256 Django-<version>.checksum.txt）。这将生成一个已签名的文档，Django-<version>.checksum.txt.asc，你可以使用 gpg --verify Django-<version>.checksum.txt.asc 来验证它。
现在，你准备好将发布版本发布出去了。为了做到这一点：
\nCreate a new Release entry in the djangoproject.com's admin. If this is a\nsecurity release, this should be done 15 minutes before the announced\nrelease time, no sooner:
Must match the version number as defined in the tarball\n(django-<version>.tar.gz). For example: "5.2", "4.1.1", or "4.2rc1".
Set to False until the release is fully published (last step).
\nEnable if the release is part of an LTS\nbranch.
\nSet the release date to today. This release will not be published until\nis_active is enabled.
Upload the tarball (django-<version>.tar.gz), wheel\n(django-<version>-py3-none-any.whl), and checksum\n(django-<version>.checksum.txt.asc) files created earlier.
Test that the release packages install correctly using pip. Here's one\nsimple method (this just tests that the binaries are available, that they\ninstall correctly, and that migrations and the development server start, but\nit'll catch silly mistakes):\nhttps://code.djangoproject.com/wiki/ReleaseTestNewVersion.
在 Jenkins 上运行 confirm-release 构建，以验证 checksum 文件（例如，对于 https://media.djangoproject.com/pgp/Django-4.2rc1.checksum.txt，使用 4.2rc1）。
Generate a new token for this release on PyPI, and store it in .pypirc\nas shown above.
Upload the release packages to PyPI:
\n$ twine upload --repository django dist/*\nOn PyPI, revoke the token you just created.
Update the newly created Release in the admin in djangoproject.com\nand enable the is_active flag.
推送你的工作和新标签：
\n$ git push\n$ git push --tags\n发布公告发布的博客文章。
对于新版本发布（例如 4.1、4.2），通过将 docs.djangoproject.com 数据库中适当的 DocumentRelease 对象上的 is_default 标志设置为 True 来更新文档的默认稳定版本（这将自动将其设置为 False，对于所有其他版本）；你可以使用站点的管理员界面来完成这个操作。
为每种语言创建新的 DocumentRelease 对象，这些语言在之前的发布中有条目。通过从 django-docs-translations 仓库 的当前稳定分支运行命令 manage_translations.py robots_txt 生成的结果，更新 djangoproject.com 的 robots.docs.txt 文件。例如，当发布 Django 4.2 时：
$ git checkout stable/4.2.x\n$ git pull\n$ python manage_translations.py robots_txt\nPost the release announcement to the django-announce mailing list and the\nDjango Forum. This should include a link to the announcement blog post.
If this is a security release, publish the CVE metadata. (The\nchecklist app generates JSON for this.):
\n$ cve publish <cve-number> --cve-json-file <path-to-file>\nIf this is a security release, send a separate email to\noss-security@lists.openwall.com. Provide "Django" plus the CVE IDs in\nthe subject line. The message body should include the vulnerability details,\nfor example, the announcement blog post text. Include a link to the\nannouncement blog post.
你差不多完成了！现在剩下要做的只有：
\nIf this is not a pre-release, update the VERSION tuple in\ndjango/__init__.py again, incrementing to whatever the next expected\nrelease will be. For example, after releasing 4.1.1, update VERSION to\nVERSION = (4, 1, 2, 'alpha', 0) (example commit).
If this was an alpha release:
\nAdd the feature release version in Trac's versions list.
Create a new security branch from the freshly cut stable branch. Be sure\nto fetch and update upstream to latest. For example, after the 5.2\nalpha release:
$ git fetch upstream\n$ git checkout -b security/5.2.x upstream/stable/5.2.x\n$ git push origin -u security/5.2.x:security/5.2.x\n如果这是一个最终发布：
\nUpdate the default_version setting in the code.djangoproject.com's\ntrac.ini file (example PR).
Update the current stable branch and remove the pre-release branch in the\nDjango release process on Trac.
更新 djangoproject.com 的下载页面（示例 PR）。
Process the older versions that will reach End-Of-Mainstream and/or\nEnd-Of-Life support when this final release is published:
\nEnsure that the EOL versions are mentioned in the blog post. See\nexample announcement.
Create a tag for the EOL stable branch and delete the stable branch.\nInspect and use the scripts/archive_eol_stable_branches.py helper.
如果这是一个安全发布，请更新 安全问题档案，提供解决问题的详细信息。
If this was a pre-release, the translation catalogs need to be updated:
\nMake a new branch from the recently released stable branch:
\n$ git checkout stable/A.B.x\n$ git checkout -b update-translations-catalog-A.B.x\nEnsure that the release's dedicated virtual environment is enabled and\nrun the following:
\n$ cd django\n$ django-admin makemessages -l en --domain=django\nprocessing locale en\n$ django-admin makemessages -l en --domain=djangojs\nprocessing locale en\nMake a pull request against the corresponding stable branch and merge\nonce approved.
Forward port the updated source translations to the main branch\n(example commit).
If this was an alpha pre-release, coordinate with the maintainer of\nasgiref to determine when to raise the minimum version before the\nfinal release. For the backport, add an upper bound on the next major\nversion (example commits:\nmain,\nbackport).
If this was an rc pre-release, call for translations for the upcoming\nrelease in the Django Forum - Internationalization category.
Django 的版本报告受控于 django/__init__.py 中的 VERSION 元组。这是一个包含五个元素的元组，其元素分别是：
主要版本。
次要版本。
微版本。
状态 -- 可以是 "alpha"、"beta"、"rc" 或 "final" 中的一个。
系列号，用于按顺序运行的 alpha/beta/RC 包（例如，"beta 1"、"beta 2" 等）。
对于最终发布，状态始终为 "final"，系列号始终为 0。状态为 "alpha" 的系列号为 0 将被报告为 "pre-alpha"。
\n一些示例：
\n(4, 1, 1, "final", 0) → "4.1.1"
(4, 2, 0, "alpha", 0) → "4.2 pre-alpha"
(4, 2, 0, "beta", 1) → "4.2 beta 1"