{"title":"Bagaimana Django Dibentuk?","version":"5.1","locale":"id","docname":"internals/howto-release-django","url":"/id/5.1/internals/howto-release-django/","canonical":"https://djangodocs.dev/id/5.1/internals/howto-release-django/","summary":"Dokumen ini menjelaskan bagaimana menerbitkan Django. Harap, jaga petunjuk-petunjuk ini terbaru jika anda membuat perubahan!","html":"

Bagaimana Django Dibentuk?Link to this heading#

\n

Dokumen ini menjelaskan bagaimana menerbitkan Django.

\n

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!

\n
\n

IkhtisarLink to this heading#

\n

Terdapat tiga jenis terbitan yang anda mungkin butuh untuk dibuat:

\n\n

Versi pendek dari langkah-langkah bersangkutan adalah:

\n
    \n

  1. Jika ini adalah terbitan keamanan, beritahu daftar penyebaran keamanan satu minggu sebelum terbitan sebenarnya.

    2. \n

  2. Proofread catatan terbitan, menacri kesalahan organisasi dan penulisan. Konsep sebuah penempatan blog dan pengumuman surel.

    3. \n

  3. Perbaharui angka versi dan buat paket terbitan.

    4. \n

  4. Unggah paket ke peladen djangoproject.com.

    5. \n

  5. Veridikasi tanda tangan paket, periksa jika mereka dapat dipasang, dan dan pastikan kegunaan minimal.

    6. \n

  6. Unggah versi terbaru ke PyPI.

    7. \n

  7. Nyatakan versi baru di admin pada djangoproject.com.

    8. \n

  8. Tempatkan masukan blog dan kirim pengumuman surel.

    9. \n

  9. Perbaharui angka versi pasca-terbitan.

    10. \n
\n

Ada banyak rincian, jadi silahkan lanjutkan membaca.

\n
\n
\n

PrasyaratLink to this heading#

\n

You'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.

\n\n
\n
\n

Tugas-tugas pra terbitanLink to this heading#

\n

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.

\n
\n

10 (atau lebih) hari sebelum terbitan keamananLink to this heading#

\n
    \n

  1. Request the CVE IDs for the security\nissue(s) being released. One CVE ID per issue, requested with\nVendor: djangoproject and Product: django.

    2. \n

  2. Generate the relevant (private) patch(es) using git format-patch, one\nfor the main branch and one for each stable branch being patched.

    3. \n
\n
\n
\n

Seminggu sebelum terbitan keamananLink to this heading#

\n
    \n

  1. 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:

    \n
    Shell
    $ gpg --clearsign --digest-algo SHA256 prenotification-email.txt\n
    \n
    2. \n

  2. Notify django-announce dari terbitan keamanan yang akan datang dengan pesan umum seperti:

    \n
    Text
    Notice 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\n
    \n
    3. \n
\n
\n
\n

Beberapa hari sebelum terbitanLink to this heading#

\n
    \n

  1. 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.

    2. \n

  2. Check with the other mergers to make sure they don't have any uncommitted\nchanges for the release.

    3. \n

  3. 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.

    4. \n

  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. \n

  5. Periksa kembali itu catatan terbitan index mempunyai sebuah tautan ke catatan untuk terbitan baru; ini akan ada di docs/releases/index.txt.

    6. \n

  6. 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.

    \n

    In 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:

    \n
    Shell
    $ python scripts/manage_translations.py fetch\n
    \n

    This 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.

    \n

    The 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):

    \n
    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"\n
    \n

    All 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.

    \n

    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).

    \n
    7. \n

  7. Update the django-admin manual page:

    \n
    Shell
    $ 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
    \n

    dan kemudian perbaiki perubahan halaman panduan.

    \n
    8. \n

  8. If this is the alpha release of a new series, create a new stable branch\nfrom main. For example, when releasing Django 4.2:

    \n
    Shell
    $ git checkout -b stable/4.2.x origin/main\n$ git push origin -u stable/4.2.x:stable/4.2.x\n
    \n

    At 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.

    \n
    9. \n

  9. 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
    Shell
    $ 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
    \n
    10. \n

  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, example regular release announcement, example pre-release announcement.

    11. \n
\n
\n
\n
\n

Sebenarnya menggulir terbitanLink to this heading#

\n

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.

\n
    \n

  1. Check 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.

    \n
    2. \n

  2. Cleanup 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.

    \n
      \n

    1. 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).

      2. \n

    2. For a patch release, remove the Expected prefix and update the\nrelease date for all releases, if necessary (example commit).

      3. \n
    \n
    3. \n

  3. 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
    Shell
    $ git checkout stable/4.1.x\n$ git pull\n
    \n
    4. \n

  4. If 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:

    \n
    Shell
    $ git checkout stable/4.1.x\n$ git merge --ff-only security/4.1.x\n
    \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.)

    \n

    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).

    \n
    5. \n

  5. 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).

    \n
      \n

    1. 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).

      2. \n

    2. Sebaliknya, pastikan penggolong disetel ke Development Status :: 5 - Production/Stable.

      3. \n
    \n
    6. \n

  6. Etiket terbitan menggunakan git tag. Sebagai contoh:

    \n
    Shell
    $ git tag --sign --message="Tag 4.1.1" 4.1.1\n
    \n

    Anda dapat memeriksa pekerjaan berjalan anda git tag --verify <tag>.

    \n
    7. \n

  7. Dorong pekerjaan anda dan tambah etiket baru:

    \n
    Shell
    $ git push\n$ git push --tags\n
    \n
    8. \n

  8. Pastikan anda mempunyai pohon sepenuhnya bersih dengan menjalankan git clean -dfx.

    9. \n

  9. Run python -m build to generate the release packages. This will create\nthe release packages in a dist/ directory.

    10. \n

  10. Bangkitkan hash dari paket terbitan:

    \n
    Shell
    $ cd dist\n$ md5sum *\n$ sha1sum *\n$ sha256sum *\n
    \n
    11. \n

  11. Create 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:

    \n
    Text
    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>>\n
    \n
    12. \n

  12. Tandatangi berkas checksum (gpg --clearsign --digest-algo SHA256 Django-<version>.checksum.txt). Ini membangkitkan dokumen ditandatangi, Django-<version>.checksum.txt.asc yang anda dapat kemudian memeriksa menggunakan gpg --verify Django-<version>.checksum.txt.asc.

    13. \n
\n
\n
\n

Membuat terbitan tesedia ke umumLink to this heading#

\n

Sekarang anda siap benar-benar menaruh terbitan diluar sana. Untuk melakukan ini:

\n
    \n

  1. Unggah berkas checksum:

    \n
    Shell
    $ scp Django-A.B.C.checksum.txt.asc djangoproject.com:/home/www/www/media/pgp/Django-A.B.C.checksum.txt\n
    \n

    (If this is a security release, what follows should be done 15 minutes\nbefore the announced release time, no sooner.)

    \n
    2. \n

  2. Unggah terbitan paket ke peladen djangoproject, mengganti A.B. dengan nomor versi sesuai, misalnya 4.1 untuk terbitan 4.1.x:

    \n
    Shell
    $ scp Django-* djangoproject.com:/home/www/www/media/releases/A.B\n
    \n

    If this is the alpha release of a new series, you will need to create\nfirst the directory A.B.

    \n
    3. \n

  3. 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):

    \n
    Shell
    $ 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\n
    \n
    4. \n

  4. Jalankan bangun confirm-release pada Jenkins untuk verifikasi berkas checksum (misalnya gunakan 4.2rc1 untuk https://media.djangoproject.com/pgp/Django-4.2rc1.checksum.txt).

    \n
    5. \n

  5. Upload the release packages to PyPI (for pre-releases, only upload the wheel\nfile):

    \n
    Shell
    $ twine upload --repository django dist/*\n
    \n
    6. \n

  6. Go 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.

    \n

    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.

    \n
    7. \n

  7. Buat blog menempatkan pengumuman terbitan langsung.

    8. \n

  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.

    \n

    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:

    \n
    Shell
    $ git checkout stable/4.2.x\n$ git pull\n$ python manage_translations.py robots_txt\n
    \n
    9. \n

  9. Post the release announcement to the django-announce mailing list and the\nDjango Forum. This should include a link to the announcement blog post.

    10. \n

  10. Jika ini adalah terbitan keamanan, kirim surel terpisah ke 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

    11. \n
\n
\n
\n

Pasca-terbitanLink to this heading#

\n

Anda hampir selesai! Semua yang tersisa untuk dilakukan sekarang adalah:

\n
    \n

  1. Update 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).

    2. \n

  2. Tambahkan terbitan dalam Trac's versions list jika dibutuhkan (dan buat sebagai awalan dengan merubah pengaturan default_version dalam code.djangoproject.com's trac.ini, jika terbitan akhirnya). Versi X.Y baru harus ditambahkan setelah terbitan alfa dan versi awalan harus diperbaharui setelah terbitan "dot zero".

    \n
    3. \n

  3. Jika ini adalah terbitan akhir:

    \n
      \n

    1. Update the current stable branch and remove the pre-release branch in the\nDjango release process on Trac.

      2. \n

    2. Perbaharui halaman unduh (example PR).

      3. \n
    \n
    4. \n

  4. Jika ini adalah terbitan keamanan, perbaharui Arsip dari masalah keamanan dengan rincian dari masalah-masalah yang dialamatkan.

    5. \n

  5. If this was a pre-release, the translation catalogs need to be updated:

    \n
      \n

    1. Make a new branch from the recently released stable branch:

      \n
      Shell
      git checkout stable/A.B.x\ngit checkout -b update-translations-catalog-A.B.x\n
      \n
      2. \n

    2. Ensure that the release's dedicated virtual environment is enabled and\nrun the following:

      \n
      Shell
      $ cd django\n$ django-admin makemessages -l en --domain=djangojs --domain=django\nprocessing locale en\n
      \n
      3. \n

    3. Review the diff before pushing and avoid committing changes to the\n.po files without any new translations (example commit).

      4. \n

    4. Make a pull request against the corresponding stable branch and merge\nonce approved.

      5. \n

    5. Forward port the updated source translations to the main branch\n(example commit).

      6. \n
    \n
    6. \n

  6. If this was an rc pre-release, call for translations for the upcoming\nrelease in the Django Forum - Internationalization category.

    7. \n
\n
\n
\n

Tugas cabang stabil baruLink to this heading#

\n

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.

\n
    \n

  1. Create 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).

    2. \n

  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. \n

  3. 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).

    4. \n

  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. \n

  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. \n

  6. 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.

    7. \n

  7. Request the new classifier on PyPI. Sebagai contoh Framework :: Django :: 3.1.

    8. \n

  8. Update the current branch under active development and add pre-release\nbranch in the Django release process on Trac.

    9. \n
\n
\n
\n

Catatan pada pengaturan tuple VERSIONLink to this heading#

\n

Pelaporan versi Django dikendalikan oleh tuple VERSION di django/__init__.py. Ini adalah lima-unsur tuple, yang unsurnya adalah:

\n
    \n

  1. Versi utama.

    2. \n

  2. Versi kecil.

    3. \n

  3. Versi mikro.

    4. \n

  4. Keadaan -- dapat menjadi satu dari "alpha", "beta", "rc" atau "final".

    5. \n

  5. Rangkaian angka, untuk paket alpha/beta/RC yang berjalan dalam urutan (mengizinkan, sebagai contoh, "beta 1", "beta 2", etc.).

    6. \n
\n

Untuk terbitan akhir, keadaan selalu "final" dan rangkaian angka selalu 0. Rangkaian angka dari 0 dengan keadaan "alpha" akan dilaporkan sebagai "pre-alpha".

\n

Beberapa contoh:

\n\n
","rootId":"how-is-django-formed","toc":[{"title":"Ikhtisar","anchor":"overview","children":[]},{"title":"Prasyarat","anchor":"prerequisites","children":[]},{"title":"Tugas-tugas pra terbitan","anchor":"pre-release-tasks","children":[{"title":"10 (atau lebih) hari sebelum terbitan keamanan","anchor":"or-more-days-before-a-security-release","children":[]},{"title":"Seminggu sebelum terbitan keamanan","anchor":"a-week-before-a-security-release","children":[]},{"title":"Beberapa hari sebelum terbitan","anchor":"a-few-days-before-any-release","children":[]}]},{"title":"Sebenarnya menggulir terbitan","anchor":"actually-rolling-the-release","children":[]},{"title":"Membuat terbitan tesedia ke umum","anchor":"making-the-release-s-available-to-the-public","children":[]},{"title":"Pasca-terbitan","anchor":"post-release","children":[]},{"title":"Tugas cabang stabil baru","anchor":"new-stable-branch-tasks","children":[]},{"title":"Catatan pada pengaturan tuple VERSION","anchor":"notes-on-setting-the-version-tuple","children":[]}],"breadcrumbs":[{"docname":"internals/index","title":"Dalam Django","url":"/id/5.1/internals/"}],"prev":{"docname":"internals/git","title":"Gudang sumber kode Django","url":"/id/5.1/internals/git/"},"next":null,"formats":{"html":"/id/5.1/internals/howto-release-django/","markdown":"/id/5.1/internals/howto-release-django.md","json":"/id/5.1/internals/howto-release-django.json"},"source":"https://github.com/django/django/blob/stable/5.1.x/docs/internals/howto-release-django.txt","official":"https://docs.djangoproject.com/id/5.1/internals/howto-release-django/","inVersions":["6.1","6.0","5.2","5.1","5.0","4.2","4.1","4.0","3.2","3.1","3.0","2.2","2.1","2.0","1.11","1.10","1.9"],"inLocales":["en","zh-hans","fr","ja","id","it","pt-br","ko","es","el","pl"]}