--- title: "Bagaimana Django Dibentuk?" version: 5.1 locale: id source: https://docs.djangoproject.com/id/5.1/internals/howto-release-django/ canonical: https://djangodocs.dev/id/5.1/internals/howto-release-django/ --- # Bagaimana Django Dibentuk? Dokumen ini menjelaskan bagaimana menerbitkan Django. **Harap, jaga petunjuk-petunjuk ini terbaru jika anda membuat perubahan!** Titiknya disini adalah menjadi lebih menggambarkan, bukan memberi petunjuk, jadi silahkan untuk mempersingkat atau jika tidak buat perubahan, tetapi **perbaharui dokumen ini sesuai dengan itu!** ## Ikhtisar Terdapat tiga jenis terbitan yang anda mungkin butuh untuk dibuat: - Terbitan keamanan: mengungkap dan memperbaiki kerentanan. Ini umumnya melibatkan dua atau lebih terbitan beruntun -- misalnya 3.2.x, 4.0.x, dan, tergatung dari waktu, mungkin 4.1.x. - Terbitan versi umum: salah satu terbitan akhir (misalnya 4.1) atau pembaharuan perbaikan kesalahan (misalnya 4.1.1). - Pra-terbitan: misalnya 4.2 alpha, beta, atau rc. Versi pendek dari langkah-langkah bersangkutan adalah: 1. Jika ini adalah terbitan keamanan, beritahu daftar penyebaran keamanan satu minggu sebelum terbitan sebenarnya. 2. Proofread catatan terbitan, menacri kesalahan organisasi dan penulisan. Konsep sebuah penempatan blog dan pengumuman surel. 3. Perbaharui angka versi dan buat paket terbitan. 4. Unggah paket ke peladen `djangoproject.com`. 5. Veridikasi tanda tangan paket, periksa jika mereka dapat dipasang, dan dan pastikan kegunaan minimal. 6. Unggah versi terbaru ke PyPI. 7. Nyatakan versi baru di admin pada `djangoproject.com`. 8. Tempatkan masukan blog dan kirim pengumuman surel. 9. Perbaharui angka versi pasca-terbitan. Ada banyak rincian, jadi silahkan lanjutkan membaca. ## Prasyarat You'll need a few things before getting started. If this is your first release, you'll need to coordinate with another releaser to get all these things lined up, and write to the Ops mailing list requesting the required access and permissions. - Lingkungan Unix dengan alat alat ini terpasang (dalam urutan abjad): - bash - git - GPG - membuat - pria - alat hashing (typically `md5sum`, `sha1sum`, dan `sha256sum` pada Linux, atau `md5` dan `shasum` pada macOS) - python - ssh - A GPG key pair. Ensure that the private part of this key is securely stored. The public part needs to be uploaded to your GitHub account, and also to the Jenkins server running the "confirm release" job. > **Lebih dari satu kunci GPG** > > If the key you want to use is not your default signing key, you'll need to > add `-u you@example.com` to every GPG signing command shown below, where > `you@example.com` is the email address associated with the key you want > to use. - A clean Python virtual environment per Django version being released, with these required Python packages installed: ```shell $ python -m pip install build twine ``` - Akses ke [Django's project on PyPI](https://pypi.org/project/Django/) untuk mengunggah biner, idealnya dengan perizinan tambahan pada [yank a release](https://pypi.org/help/#yanked) jika dibutuhkan. Buat token cakupan-proyek mengikuti berkas [official documentation](https://pypi.org/help/#apitoken) dan buat `$HOME/.pypirc` seperti ini: *`~/.pypirc`* ```ini [distutils] index-servers = pypi django [pypi] username = __token__ password = # User-scoped or project-scoped token, to set as the default. [django] repository = https://upload.pypi.org/legacy/ username = __token__ password = # A project token. ``` - Access to [Django's project on Transifex](https://app.transifex.com/django/django/), with a Manager role. Generate an API Token in the [user setting section](https://app.transifex.com/user/settings/api/) and set up your `$HOME/.transifexrc` file like this: *`~/.transifexrc`* ```ini [https://www.transifex.com] rest_hostname = https://rest.api.transifex.com token = # API token ``` - Access 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](https://forum.djangoproject.com/c/announcements/7) and to send emails to the following mailing lists: - [django-announce](https://groups.google.com/g/django-announce/) - Access to the `django-security` repo in GitHub. Among other things, this provides access to the pre-notification distribution list (needed for security release preparation tasks). ## Tugas-tugas pra terbitan A few items need to be taken care of before even beginning the release process. This stuff starts about a week before the release; most of it can be done any time leading up to the actual release. ### 10 (atau lebih) hari sebelum terbitan keamanan 1. Request the [CVE IDs](https://cveform.mitre.org/) for the security issue(s) being released. One CVE ID per issue, requested with `Vendor: djangoproject` and `Product: django`. 2. Generate the relevant (private) patch(es) using `git format-patch`, one for the `main` branch and one for each stable branch being patched. ### Seminggu sebelum terbitan keamanan 1. Send out pre-notification exactly **one week** before the security release. The template for that email and a list of the recipients are in the private `django-security` GitHub wiki. BCC the pre-notification 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: ```shell $ gpg --clearsign --digest-algo SHA256 prenotification-email.txt ``` 2. [Notify django-announce](/id/5.1/internals/security/#security-disclosure) dari terbitan keamanan yang akan datang dengan pesan umum seperti: ```text Notice of upcoming Django security releases (3.2.24, 4.2.10 and 5.0.2) Django versions 5.0.2, 4.2.10, and 3.2.24 will be released on Tuesday, February 6th, 2024 around 1500 UTC. They will fix one security defect with severity "moderate". For details of severity levels, see: https://docs.djangoproject.com/en/dev/internals/security/#how-django-discloses-security-issues ``` ### Beberapa hari sebelum terbitan 1. As the release approaches, watch Trac to make sure no release blockers are left for the upcoming release. Under exceptional circumstances, such as to meet a pre-determined security release date, a release could still go ahead with an open release blocker. The releaser is trusted with the decision to release with an open release blocker or to postpone the release date of a non-security release if required. 2. Check with the other mergers to make sure they don't have any uncommitted changes for the release. 3. Proofread the release notes, including looking at the online version to [catch any broken links](/id/5.1/internals/contributing/writing-documentation/#documentation-link-check) or reST errors, and make sure the release notes contain the correct date. 4. Periksa kembali itu catatan terbitan menyebutkan linimasa pengusangan untuk setiap API dicatat sebagai diusangkan, dan mereka menyebut bahwa tiap perubahan di Python versi dukungan. 5. Periksa kembali itu catatan terbitan index mempunyai sebuah tautan ke catatan untuk terbitan baru; ini akan ada di `docs/releases/index.txt`. 6. If this is a [feature release](/id/5.1/internals/release-process/#term-Feature-release), ensure translations from Transifex have been integrated. This is typically done by a separate translation's manager rather than the releaser, but here are the steps. This process is a bit lengthy so be sure to set aside 4-10 hours to do this, and ideally plan for this task one or two days ahead of the release day. In addition to having a configured Transifex account, the [tx CLI](https://developers.transifex.com/docs/cli) should be available in your `PATH`. Then, you can fetch all the translations by running: ```shell $ python scripts/manage_translations.py fetch ``` This command takes some time to run. When done, carefully inspect the output for potential errors and/or warnings. If there are some, you will need to debug and resolve them on a case by case basis. The recently fetched translations need some manual adjusting. First of all, the `PO-Revision-Date` values must be manually bumped to be later than `POT-Creation-Date`. You can use a command similar to this to bulk update all the `.po` files (compare the diff against the relevant stable branch): ```shell $ 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" ``` All the new `.po` files should be manually and carefully inspected to avoid committing a change in a file without any new translations. Also, there shouldn't be any changes in the "plural forms": if there are any (usually Spanish and French report changes for this) those will need reverting. Lastly, commit the changed/added files (both `.po` and `.mo`) and create a new PR targeting the stable branch of the corresponding release (example [PR updating translations for 4.2](https://github.com/django/django/pull/16715)). 7. [Update the django-admin manual page](/id/5.1/internals/contributing/writing-documentation/#django-admin-manpage): ```shell $ cd docs $ make man $ man _build/man/django-admin.1 # do a quick sanity check $ cp _build/man/django-admin.1 man/django-admin.1 ``` dan kemudian perbaiki perubahan halaman panduan. 8. If this is the alpha release of a new series, create a new stable branch from main. For example, when releasing Django 4.2: ```shell $ git checkout -b stable/4.2.x origin/main $ git push origin -u stable/4.2.x:stable/4.2.x ``` At the same time, update the `django_next_version` variable in `docs/conf.py` on the stable release branch to point to the new development version. For example, when creating `stable/4.2.x`, set `django_next_version` to `'5.0'` on the new branch. 9. If this is the "dot zero" release of a new series, create a new branch from the current stable branch in the [django-docs-translations](https://github.com/django/django-docs-translations) repository. For example, when releasing Django 4.2: ```shell $ git checkout -b stable/4.2.x origin/stable/4.1.x $ git push origin stable/4.2.x:stable/4.2.x ``` 10. Tulis penempatan blog pengumuman untuk terbitan. Anda dapat memasukkannya kedalam admin kapan pun dan menandainya sebagai tidak aktif. Ini adalah beberapa contoh: [example security release announcement](https://www.djangoproject.com/weblog/2013/feb/19/security/), [example regular release announcement](https://www.djangoproject.com/weblog/2012/mar/23/14/), [example pre-release announcement](https://www.djangoproject.com/weblog/2012/nov/27/15-beta-1/). ## Sebenarnya menggulir terbitan OK, this is the fun part, where we actually push out a release! If you're issuing **multiple releases**, repeat these steps for each release. 1. Check [Jenkins](https://djangoci.com) is green for the version(s) you're putting out. You probably shouldn't issue a release until it's green, and you should make sure that the latest green run includes the changes that you are releasing. 2. 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. 1. For a feature release, remove the `UNDER DEVELOPMENT` header at the top of the release notes, remove the `Expected` prefix and update the release date, if necessary ([example commit](https://github.com/django/django/commit/1994a2643881a9e3f9fa8d3e0794c1a9933a1831)). 2. For a patch release, remove the `Expected` prefix and update the release date for all releases, if necessary ([example commit](https://github.com/django/django/commit/34a503162fe222033a1cd3249bccad014fcd1d20)). 3. A release always begins from a release branch, so you should make sure you're on an up-to-date stable branch. Also, you should have available a clean and dedicated virtual environment per version being released. For example: ```shell $ git checkout stable/4.1.x $ git pull ``` 4. If this is a security release, merge the appropriate patches from `django-security`. Rebase these patches as necessary to make each one a plain commit on the release branch rather than a merge commit. To ensure this, merge them with the `--ff-only` flag; for example: ```shell $ git checkout stable/4.1.x $ git merge --ff-only security/4.1.x ``` (This assumes `security/4.1.x` is a branch in the `django-security` repo containing the necessary security patches for the next release in the 4.1 series.) If git refuses to merge with `--ff-only`, switch to the security-patch branch and rebase it on the branch you are about to merge it into (`git checkout security/4.1.x; git rebase stable/4.1.x`) and then switch back and do the merge. Make sure the commit message for each security fix explains that the commit is a security fix and that an announcement will follow ([example security commit](https://github.com/django/django/commit/bf39978a53f117ca02e9a0c78b76664a41a54745)). 5. Update the version number in `django/__init__.py` for the release. Please see [notes on setting the VERSION tuple](#notes-on-setting-the-version-tuple) below for details on `VERSION` ([example commit](https://github.com/django/django/commit/2719a7f8c161233f45d34b624a9df9392c86cc1b)). 1. If this is a pre-release package also update the "Development Status" trove classifier in `pyproject.toml` to reflect this. An `rc` pre-release should not change the trove classifier ([example commit for alpha release](https://github.com/django/django/commit/eeeacc52a967234e920c001b7908c4acdfd7a848), [example commit for beta release](https://github.com/django/django/commit/25fec8940b24107e21314ab6616e18ce8dec1c1c)). 2. Sebaliknya, pastikan penggolong disetel ke `Development Status :: 5 - Production/Stable`. 6. Etiket terbitan menggunakan `git tag`. Sebagai contoh: ```shell $ git tag --sign --message="Tag 4.1.1" 4.1.1 ``` Anda dapat memeriksa pekerjaan berjalan anda `git tag --verify `. 7. Dorong pekerjaan anda dan tambah etiket baru: ```shell $ git push $ git push --tags ``` 8. Pastikan anda mempunyai pohon sepenuhnya bersih dengan menjalankan `git clean -dfx`. 9. Run `python -m build` to generate the release packages. This will create the release packages in a `dist/` directory. 10. Bangkitkan hash dari paket terbitan: ```shell $ cd dist $ md5sum * $ sha1sum * $ sha256sum * ``` 11. Create a "checksums" file, `Django-<>.checksum.txt` containing the hashes and release information. Start with this template and insert the correct version, date, GPG key ID (from `gpg --list-keys --keyid-format LONG`), release manager's GitHub username, release URL, and checksums: ```text This file contains MD5, SHA1, and SHA256 checksums for the source-code tarball and wheel files of Django <>, released <>. To use this file, you will need a working install of PGP or other compatible public-key encryption software. You will also need to have the Django release manager's public key in your keyring. This key has the ID ``XXXXXXXXXXXXXXXX`` and can be imported from the MIT keyserver, for example, if using the open-source GNU Privacy Guard implementation of PGP: gpg --keyserver pgp.mit.edu --recv-key XXXXXXXXXXXXXXXX or via the GitHub API: curl https://github.com/<>.gpg | gpg --import - Once the key is imported, verify this file: gpg --verify <> Once you have verified this file, you can use normal MD5, SHA1, or SHA256 checksumming applications to generate the checksums of the Django package and compare them to the checksums listed below. Release packages ================ https://www.djangoproject.com/m/releases/<>/<> https://www.djangoproject.com/m/releases/<>/<> MD5 checksums ============= <> <> <> <> SHA1 checksums ============== <> <> <> <> SHA256 checksums ================ <> <> <> <> ``` 12. Tandatangi berkas checksum (`gpg --clearsign --digest-algo SHA256 Django-.checksum.txt`). Ini membangkitkan dokumen ditandatangi, `Django-.checksum.txt.asc` yang anda dapat kemudian memeriksa menggunakan `gpg --verify Django-.checksum.txt.asc`. ## Membuat terbitan tesedia ke umum Sekarang anda siap benar-benar menaruh terbitan diluar sana. Untuk melakukan ini: 1. Unggah berkas checksum: ```shell $ scp Django-A.B.C.checksum.txt.asc djangoproject.com:/home/www/www/media/pgp/Django-A.B.C.checksum.txt ``` (If this is a security release, what follows should be done 15 minutes before the announced release time, no sooner.) 2. Unggah terbitan paket ke peladen djangoproject, mengganti A.B. dengan nomor versi sesuai, misalnya 4.1 untuk terbitan 4.1.x: ```shell $ scp Django-* djangoproject.com:/home/www/www/media/releases/A.B ``` If this is the alpha release of a new series, you will need to create **first** the directory A.B. 3. Test that the release packages install correctly using `pip`. Here's one simple method (this just tests that the binaries are available, that they install correctly, and that migrations and the development server start, but it'll catch silly mistakes): ```shell $ RELEASE_VERSION='4.1.1' $ MAJOR_VERSION=`echo $RELEASE_VERSION| cut -c 1-3` $ python -m venv django-pip-tarball $ . django-pip-tarball/bin/activate $ python -m pip install https://www.djangoproject.com/m/releases/$MAJOR_VERSION/Django-$RELEASE_VERSION.tar.gz $ django-admin startproject test_tarball $ cd test_tarball $ ./manage.py --help # Ensure executable bits $ python manage.py migrate $ python manage.py runserver $ deactivate $ cd .. && rm -rf test_tarball && rm -rf django-pip-tarball $ python -m venv django-pip-wheel $ . django-pip-wheel/bin/activate $ python -m pip install https://www.djangoproject.com/m/releases/$MAJOR_VERSION/Django-$RELEASE_VERSION-py3-none-any.whl $ django-admin startproject test_wheel $ cd test_wheel $ ./manage.py --help # Ensure executable bits $ python manage.py migrate $ python manage.py runserver $ deactivate $ cd .. && rm -rf test_wheel && rm -rf django-pip-wheel ``` 4. Jalankan bangun [confirm-release](https://djangoci.com/job/confirm-release/) pada Jenkins untuk verifikasi berkas checksum (misalnya gunakan `4.2rc1` untuk ). 5. Upload the release packages to PyPI (for pre-releases, only upload the wheel file): ```shell $ twine upload --repository django dist/* ``` 6. Go to the [Add release page in the admin](https://www.djangoproject.com/admin/releases/release/add/), enter the new release number exactly as it appears in the name of the tarball (`Django-.tar.gz`). So for example enter "4.1.1" or "4.2rc1", etc. 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 for the *final* release, ensuring that the *Release date* field is blank, thus marking it as *unreleased*. For example, when creating the Release object for `4.2a1`, also create `4.2` with the Release date field blank. 7. Buat blog menempatkan pengumuman terbitan langsung. 8. Untuk terbitan versi baru (misalnya 4.1, 4.2), perbaharui versi stabil awal dari dokumen dengan membalikkan bendera `is_default` menjadi `True` pada obyek `DocumentRelease` yang sesuai di basisdata `docs.djangoproject.com` (ini akan otomatis menggantinya menjadi `False` untuk semua lainnya); anda dapat melakukan ini menggunakan admin situs. Create new `DocumentRelease` objects for each language that has an entry for the previous release. Update djangoproject.com's [robots.docs.txt](https://github.com/django/djangoproject.com/blob/main/djangoproject/static/robots.docs.txt) file by copying the result generated from running the command `manage_translations.py robots_txt` in the current stable branch from the [django-docs-translations repository](https://github.com/django/django-docs-translations). For example, when releasing Django 4.2: ```shell $ git checkout stable/4.2.x $ git pull $ python manage_translations.py robots_txt ``` 9. Post the release announcement to the [django-announce](/id/5.1/internals/mailing-lists/#django-announce-mailing-list) mailing list and the Django Forum. This should include a link to the announcement blog post. 10. Jika ini adalah terbitan keamanan, kirim surel terpisah ke [oss-security@lists.openwall.com](mailto:oss-security@lists.openwall.com). Sediakan gambaran subjek, sebagai contoh, "Django" ditambah masalah dari catatan terbitan (termasuk ID CVE). Badan pesan harus menyertakan rincian kerentanan, sebagai contoh, pengumuman teks penempatan blog. Sertakan sebauh tautan pada penempatan blog pengumuman ## Pasca-terbitan Anda hampir selesai! Semua yang tersisa untuk dilakukan sekarang adalah: 1. Update the `VERSION` tuple in `django/__init__.py` again, incrementing to whatever the next expected release will be. For example, after releasing 4.1.1, update `VERSION` to `VERSION = (4, 1, 2, 'alpha', 0)`. 2. Tambahkan terbitan dalam [Trac's versions list](https://code.djangoproject.com/admin/ticket/versions) jika dibutuhkan (dan buat sebagai awalan dengan merubah pengaturan `default_version` dalam code.djangoproject.com's [trac.ini](https://github.com/django/code.djangoproject.com/blob/main/trac-env/conf/trac.ini), jika terbitan akhirnya). Versi X.Y baru harus ditambahkan setelah terbitan alfa dan versi awalan harus diperbaharui setelah terbitan "dot zero". 3. Jika ini adalah terbitan akhir: 1. Update the current stable branch and remove the pre-release branch in the [Django release process](https://code.djangoproject.com/#Djangoreleaseprocess) on Trac. 2. Perbaharui halaman unduh ([example PR](https://github.com/django/djangoproject.com/pull/1444)). 4. Jika ini adalah terbitan keamanan, perbaharui [Arsip dari masalah keamanan](/id/5.1/releases/security/) dengan rincian dari masalah-masalah yang dialamatkan. 5. If this was a pre-release, the translation catalogs need to be updated: 1. Make a new branch from the recently released stable branch: ```shell git checkout stable/A.B.x git checkout -b update-translations-catalog-A.B.x ``` 2. Ensure that the release's dedicated virtual environment is enabled and run the following: ```shell $ cd django $ django-admin makemessages -l en --domain=djangojs --domain=django processing locale en ``` 3. Review the diff before pushing and avoid committing changes to the `.po` files without any new translations ([example commit](https://github.com/django/django/commit/d2b1ec551567c208abfdd21b27ff6d08ae1a6371)). 4. Make a pull request against the corresponding stable branch and merge once approved. 5. Forward port the updated source translations to the `main` branch ([example commit](https://github.com/django/django/commit/aed303aff57ac990894b6354af001b0e8ea55f71)). 6. If this was an `rc` pre-release, call for translations for the upcoming release in the [Django Forum - Internationalization category](https://forum.djangoproject.com/c/internals/i18n/14). ## Tugas cabang stabil baru Ada beberapa barang untuk dilakukan di waktu mengikuti pembuatan cabang stabil baru (sering mengikuti terbitan alpha). Beberapa dari pekerjaan ini tidak butuh diselesaikan oleh penerbit. 1. Create a new `DocumentRelease` object in the `docs.djangoproject.com` database for the new version's docs, and update the `docs/fixtures/doc_releases.json` JSON fixture, so people without access to the production DB can still run an up-to-date copy of the docs site ([example PR](https://github.com/django/djangoproject.com/pull/1446)). 2. Buat sebuah catatan terbitan rintisan untuk versi fitur baru. Gunakan rintisan dari terbitan fitur sebelumnya atau salin isi dari versi fitur sebelumnya dan hapus kebanyakan isi meninggalkan hanya kepala. 3. Increase the default PBKDF2 iterations in `django.contrib.auth.hashers.PBKDF2PasswordHasher` by about 20% (pick a round number). Run the tests, and update the 3 failing hasher tests with the new values. Make sure this gets noted in the release notes (see the 4.1 release notes for an example). 4. Pindahkan fitur yang telah mencapai akhir dari siklus pengusangannya. Setiap perpindahan harus selesai di perbaikan terpisah untuk kejelasan. Dalam pesan perbaikan, tambah "refs #XXXX" pada tiket asli dimana pengusangan dimulai jika memungkinkan. 5. Hapus catatan tambahan `.. versionadded::`, `.. versionchanged::`, dan `.. deprecated::` di dokumentasi dari terbitan dua tahun lalu. Sebagai contoh, di Django 4.2, catatan untuk 4.0 akan dihapus. 6. Add the new branch to [Read the Docs](https://readthedocs.org/projects/django/). Since the automatically generated version names ("stable-A.B.x") differ from the version names used in Read the Docs ("A.B.x"), [create a ticket](https://github.com/readthedocs/readthedocs.org/issues/5537) requesting the new version. 7. [Request the new classifier on PyPI](https://github.com/pypa/trove-classifiers/issues/29). Sebagai contoh `Framework :: Django :: 3.1`. 8. Update the current branch under active development and add pre-release branch in the [Django release process](https://code.djangoproject.com/#Djangoreleaseprocess) on Trac. ## Catatan pada pengaturan tuple VERSION Pelaporan versi Django dikendalikan oleh tuple `VERSION` di `django/__init__.py`. Ini adalah lima-unsur tuple, yang unsurnya adalah: 1. Versi utama. 2. Versi kecil. 3. Versi mikro. 4. Keadaan -- dapat menjadi satu dari "alpha", "beta", "rc" atau "final". 5. Rangkaian angka, untuk paket alpha/beta/RC yang berjalan dalam urutan (mengizinkan, sebagai contoh, "beta 1", "beta 2", etc.). Untuk terbitan akhir, keadaan selalu "final" dan rangkaian angka selalu 0. Rangkaian angka dari 0 dengan keadaan "alpha" akan dilaporkan sebagai "pre-alpha". Beberapa contoh: - `(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"