Este documento explica cómo se publica Django.
\nPlease, keep these instructions up-to-date if you make changes! The point\nhere is to be descriptive, not prescriptive, so feel free to streamline or\notherwise make changes, but update this document accordingly!
\nThere are three types of releases that you might need to make:
\nSecurity releases: disclosing and fixing a vulnerability. This’ll\ngenerally involve two or three simultaneous releases – e.g.\n3.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\nbugfix update (e.g. 4.1.1).
Pre-releases: e.g. 4.2 alpha, beta, or rc.
The short version of the steps involved is:
\nIf this is a security release, pre-notify the security distribution list\none week before the actual release.
Proofread the release notes, looking for organization and writing errors.\nDraft a blog post and email announcement.
Update version numbers and create the release package(s).
Upload the package(s) to the djangoproject.com server.
Verify package(s) signatures, check if they can be installed, and ensure\nminimal functionality.
Upload the new version(s) to PyPI.
Declare the new version in the admin on djangoproject.com.
Post the blog entry and send out the email announcements.
Update version numbers post-release.
There are a lot of details, so please read on.
\nYou’ll need a few things before getting started. If this is your first release,\nyou’ll need to coordinate with another releaser to get all these things lined\nup, and write to the Ops mailing list requesting the required access and\npermissions.
\nA Unix environment with these tools installed (in alphabetical order):
\nbash
git
GPG
make
man
hashing tools (typically md5sum, sha1sum, and sha256sum on\nLinux, or md5 and shasum on macOS)
python
ssh
A GPG key pair. Ensure that the private part of this key is securely stored.\nThe public part needs to be uploaded to your GitHub account, and also to the\nJenkins server running the «confirm release» job.
\n\nA clean Python virtual environment per Django version being released, with\nthese required Python packages installed:
\n$ python -m pip install build twine\nAccess to Django’s project on PyPI to\nupload binaries, ideally with extra permissions to yank a release if necessary. Create a project-scoped token\nfollowing the official documentation\nand set up your $HOME/.pypirc file like 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\nAccess to the djangoproject.com server to upload files (using scp).
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\nthe following mailing lists:
\nAccess to the django-security repo in GitHub. Among other things, this\nprovides access to the pre-notification distribution list (needed for\nsecurity release preparation tasks).
A few items need to be taken care of before even beginning the release process.\nThis stuff starts about a week before the release; most of it can be done\nany time leading up to the actual release.
\nRequest the CVE IDs for the security\nissue(s) being released. One CVE ID per issue, requested with\nVendor: djangoproject and Product: django.
Generate the relevant (private) patch(es) using git format-patch, one\nfor the main branch and one for each stable branch being patched.
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\nNotify django-announce of the upcoming\nsecurity release with a general message such as:
\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\nAs 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.
Check with the other mergers to make sure they don’t have any uncommitted\nchanges for the release.
Proofread the release notes, including looking at the online version to\ncatch any broken links or reST errors, and\nmake sure the release notes contain the correct date.
Double-check that the release notes mention deprecation timelines\nfor any APIs noted as deprecated, and that they mention any changes\nin Python version support.
Double-check that the release notes index has a link to the notes\nfor the new release; this will be in docs/releases/index.txt.
If this is a feature release, ensure translations from Transifex\nhave been integrated. This is typically done by a separate translation’s\nmanager rather than the releaser, but here are the steps. This process is a\nbit lengthy so be sure to set aside 4-10 hours to do this, and ideally plan\nfor this task one or two days ahead of the release day.
\nIn addition to having a configured Transifex account, the\ntx CLI should be available in\nyour PATH. Then, you can fetch all the translations by running:
$ python scripts/manage_translations.py fetch\nThis command takes some time to run. When done, carefully inspect the output\nfor potential errors and/or warnings. If there are some, you will need to\ndebug and resolve them on a case by case basis.
\nThe recently fetched translations need some manual adjusting. First of all,\nthe PO-Revision-Date values must be manually bumped to be later than\nPOT-Creation-Date. You can use a command similar to this to bulk update\nall the .po files (compare the diff against the relevant stable branch):
$ 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"\nAll the new .po files should be manually and carefully inspected to\navoid committing a change in a file without any new translations. Also,\nthere shouldn’t be any changes in the «plural forms»: if there are any\n(usually Spanish and French report changes for this) those will need\nreverting.
Lastly, 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).
Update the django-admin manual page:
\n$ 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\nand then commit the changed man page.
\nIf this is the alpha release of a new series, create a new stable branch\nfrom main. For example, when releasing Django 4.2:
\n$ git checkout -b stable/4.2.x origin/main\n$ git push origin -u stable/4.2.x:stable/4.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/4.2.x, set\ndjango_next_version to '5.0' on the new branch.
If 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\nWrite the announcement blog post for the release. You can enter it into the\nadmin at any time and mark it as inactive. Here are a few examples: example\nsecurity release announcement, example regular release announcement,\nexample pre-release announcement.
OK, this is the fun part, where we actually push out a release! If you’re\nissuing multiple releases, repeat these steps for each release.
\nCheck Jenkins is green for the version(s) you’re putting out. You\nprobably shouldn’t issue a release until it’s green, and you should make\nsure that the latest green run includes the changes that you are releasing.
\nCleanup the release notes for this release. Make these changes in main\nand backport to all branches where the release notes for a particular\nversion are located.
For a feature release, remove the UNDER DEVELOPMENT header at the top\nof the release notes, remove the Expected prefix and update the\nrelease date, if necessary (example commit).
For a patch release, remove the Expected prefix and update the\nrelease date for all releases, if necessary (example commit).
A release always begins from a release branch, so you should make sure\nyou’re on an up-to-date stable branch. Also, you should have available a\nclean and dedicated virtual environment per version being released. For\nexample:
\n$ git checkout stable/4.1.x\n$ git pull\nIf this is a security release, merge the appropriate patches from\ndjango-security. Rebase these patches as necessary to make each one a\nplain commit on the release branch rather than a merge commit. To ensure\nthis, merge them with the --ff-only flag; for example:
$ git checkout stable/4.1.x\n$ git merge --ff-only security/4.1.x\n(This assumes security/4.1.x is a branch in the django-security repo\ncontaining the necessary security patches for the next release in the 4.1\nseries.)
If git refuses to merge with --ff-only, switch to the security-patch\nbranch and rebase it on the branch you are about to merge it into (git\ncheckout security/4.1.x; git rebase stable/4.1.x) and then switch back and\ndo the merge. Make sure the commit message for each security fix explains\nthat the commit is a security fix and that an announcement will follow\n(example security commit).
Update the version number in django/__init__.py for the release.\nPlease see notes on setting the VERSION tuple below for details\non VERSION (example commit).
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).
Otherwise, make sure the classifier is set to\nDevelopment Status :: 5 - Production/Stable.
Tag the release using git tag. For example:
$ git tag --sign --message="Tag 4.1.1" 4.1.1\nYou can check your work running git tag --verify <tag>.
Push your work and the new tag:
\n$ git push\n$ git push --tags\nMake sure you have an absolutely clean tree by running git clean -dfx.
Run python -m build to generate the release packages. This will create\nthe release packages in a dist/ directory.
Generate the hashes of the release packages:
\n$ cd dist\n$ md5sum *\n$ sha1sum *\n$ sha256sum *\nCreate a «checksums» file, Django-<<VERSION>>.checksum.txt containing\nthe hashes and release information. Start with this template and insert the\ncorrect version, date, GPG key ID (from\ngpg --list-keys --keyid-format LONG), release manager’s GitHub username,\nrelease URL, and checksums:
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 the MIT\nkeyserver, for example, if using the open-source GNU Privacy Guard\nimplementation of PGP:\n\n gpg --keyserver pgp.mit.edu --recv-key XXXXXXXXXXXXXXXX\n\nor via the GitHub API:\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/m/releases/<<MAJOR VERSION>>/<<RELEASE TAR.GZ FILENAME>>\nhttps://www.djangoproject.com/m/releases/<<MAJOR VERSION>>/<<RELEASE WHL FILENAME>>\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>>\nSign the checksum file (gpg --clearsign --digest-algo SHA256\nDjango-<version>.checksum.txt). This generates a signed document,\nDjango-<version>.checksum.txt.asc which you can then verify using gpg\n--verify Django-<version>.checksum.txt.asc.
Now you’re ready to actually put the release out there. To do this:
\nUpload the checksum file(s):
\n$ scp Django-A.B.C.checksum.txt.asc djangoproject.com:/home/www/www/media/pgp/Django-A.B.C.checksum.txt\n(If this is a security release, what follows should be done 15 minutes\nbefore the announced release time, no sooner.)
\nUpload the release package(s) to the djangoproject server, replacing\nA.B. with the appropriate version number, e.g. 4.1 for a 4.1.x release:
\n$ scp Django-* djangoproject.com:/home/www/www/media/releases/A.B\nIf this is the alpha release of a new series, you will need to create\nfirst the directory A.B.
\nTest 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):
$ RELEASE_VERSION='4.1.1'\n$ MAJOR_VERSION=`echo $RELEASE_VERSION| cut -c 1-3`\n\n$ python -m venv django-pip-tarball\n$ . django-pip-tarball/bin/activate\n$ python -m pip install https://www.djangoproject.com/m/releases/$MAJOR_VERSION/Django-$RELEASE_VERSION.tar.gz\n$ django-admin startproject test_tarball\n$ cd test_tarball\n$ ./manage.py --help # Ensure executable bits\n$ python manage.py migrate\n$ python manage.py runserver\n<CTRL+C>\n$ deactivate\n$ cd .. && rm -rf test_tarball && rm -rf django-pip-tarball\n\n$ python -m venv django-pip-wheel\n$ . django-pip-wheel/bin/activate\n$ python -m pip install https://www.djangoproject.com/m/releases/$MAJOR_VERSION/Django-$RELEASE_VERSION-py3-none-any.whl\n$ django-admin startproject test_wheel\n$ cd test_wheel\n$ ./manage.py --help # Ensure executable bits\n$ python manage.py migrate\n$ python manage.py runserver\n<CTRL+C>\n$ deactivate\n$ cd .. && rm -rf test_wheel && rm -rf django-pip-wheel\nRun the confirm-release build on Jenkins to verify the checksum file(s)\n(e.g. use 4.2rc1 for\nhttps://media.djangoproject.com/pgp/Django-4.2rc1.checksum.txt).
Upload the release packages to PyPI (for pre-releases, only upload the wheel\nfile):
\n$ twine upload --repository django dist/*\nGo to the Add release page in the admin, enter the new release number\nexactly as it appears in the name of the tarball\n(Django-<version>.tar.gz). So for example enter «4.1.1» or «4.2rc1»,\netc. If the release is part of an LTS branch, mark it so.
If this is the alpha release of a new series, also create a Release object\nfor the final release, ensuring that the Release date field is blank,\nthus marking it as unreleased. For example, when creating the Release\nobject for 4.2a1, also create 4.2 with the Release date field blank.
Make the blog post announcing the release live.
For a new version release (e.g. 4.1, 4.2), update the default stable version\nof the docs by flipping the is_default flag to True on the\nappropriate DocumentRelease object in the docs.djangoproject.com\ndatabase (this will automatically flip it to False for all\nothers); you can do this using the site’s admin.
Create new DocumentRelease objects for each language that has an entry\nfor the previous release. Update djangoproject.com’s robots.docs.txt\nfile by copying the result generated from running the command\nmanage_translations.py robots_txt in the current stable branch from the\ndjango-docs-translations repository. For example, when releasing Django\n4.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, send a separate email to\noss-security@lists.openwall.com. Provide a descriptive subject, for example,\n«Django» plus the issue title from the release notes (including CVE ID). The\nmessage body should include the vulnerability details, for example, the\nannouncement blog post text. Include a link to the announcement blog post.
You’re almost done! All that’s left to do now is:
\nUpdate the VERSION tuple in django/__init__.py again,\nincrementing to whatever the next expected release will be. For\nexample, after releasing 4.1.1, update VERSION to\nVERSION = (4, 1, 2, 'alpha', 0).
Add the release in Trac’s versions list if necessary (and make it the\ndefault by changing the default_version setting in the\ncode.djangoproject.com’s trac.ini, if it’s a final release). The new X.Y\nversion should be added after the alpha release and the default version\nshould be updated after «dot zero» release.
If this was a final release:
\nUpdate the current stable branch and remove the pre-release branch in the\nDjango release process on Trac.
Update djangoproject.com’s download page (example PR).
If this was a security release, update Archive of security issues with\ndetails of the issues addressed.
If this was a pre-release, the translation catalogs need to be updated:
\nMake a new branch from the recently released stable branch:
\ngit checkout stable/A.B.x\ngit 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=djangojs --domain=django\nprocessing locale en\nReview the diff before pushing and avoid committing changes to the\n.po files without any new translations (example commit).
Make 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 rc pre-release, call for translations for the upcoming\nrelease in the Django Forum - Internationalization category.
There are several items to do in the time following the creation of a new\nstable branch (often following an alpha release). Some of these tasks don’t\nneed to be done by the releaser.
\nCreate a new DocumentRelease object in the docs.djangoproject.com\ndatabase for the new version’s docs, and update the\ndocs/fixtures/doc_releases.json JSON fixture, so people without access\nto the production DB can still run an up-to-date copy of the docs site\n(example PR).
Create a stub release note for the new feature version. Use the stub from\nthe previous feature release version or copy the contents from the previous\nfeature version and delete most of the contents leaving only the headings.
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 (see the 4.1 release notes for an example).
Remove features that have reached the end of their deprecation cycle. Each\nremoval should be done in a separate commit for clarity. In the commit\nmessage, add a «refs #XXXX» to the original ticket where the deprecation\nbegan if possible.
Remove .. versionadded::, .. versionchanged::, and\n.. deprecated:: annotations in the documentation from two releases ago.\nFor example, in Django 4.2, notes for 4.0 will be removed.
Add the new branch to Read the Docs. Since the automatically\ngenerated version names («stable-A.B.x») differ from the version names\nused in Read the Docs («A.B.x»), create a ticket requesting\nthe new version.
Request the new classifier on PyPI. For example\nFramework :: Django :: 3.1.
Update the current branch under active development and add pre-release\nbranch in the Django release process on Trac.
Django’s version reporting is controlled by the VERSION tuple in\ndjango/__init__.py. This is a five-element tuple, whose elements\nare:
Major version.
Minor version.
Micro version.
Status – can be one of «alpha», «beta», «rc» or «final».
Series number, for alpha/beta/RC packages which run in sequence\n(allowing, for example, «beta 1», «beta 2», etc.).
For a final release, the status is always «final» and the series\nnumber is always 0. A series number of 0 with an «alpha» status will\nbe reported as «pre-alpha».
\nSome examples:
\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»