{"title":"Bagaimana Django Dibentuk?","version":"4.2","locale":"id","docname":"internals/howto-release-django","url":"/id/4.2/internals/howto-release-django/","canonical":"https://djangodocs.dev/id/4.2/internals/howto-release-django/","summary":"Dokumen ini menjelaskan bagaimana menerbitkan Django. Harap, jaga petunjuk-petunjuk ini terbaru jika anda membuat perubahan! Titiknya disini adalah menjadi lebih…","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. Unggah versi terbaru ke PyPI.

    6. \n

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

    7. \n

  7. Tempatkan masukan blog dan kirim pengumuman surel.

    8. \n

  8. Perbaharui angka versi pasca-terbitan.

    9. \n
\n

Ada banyak rincian, jadi silahkan lanjutkan membaca.

\n
\n
\n

PrasyaratLink to this heading#

\n

Anda akan butuh beberapa hal sebelum memulai:

\n\n

Jika ini adalah terbitan pertama anda, anda akan butuh berhubungan dengan penerbit lain untuk mendapatkan semua hal ini berbaris.

\n
\n
\n

Tugas-tugas pra terbitanLink to this heading#

\n

Beberapa barang harus dijaga sebelum bahkan memulai pengolahan terbitan. Barang ini mulai sekitar seminggu sebelum terbitan; kebanyakan dari itu dapat dilakukan kapan saja membawa ke terbitan sebenarnya:

\n
    \n

  1. Ini adalah terbitan keamanan, mengirimkan pra-pemberitahuan satu minggu sebelum terbitan. Cetakan untuk surel itu dan daftar dari penerima adalah dalam wiki GitHub django-security pribadi. Penerima BCC pra-pemberitahuan. Menandai surel dengan kunci anda akan gunakan untuk terbitan dan menyertakan CVE IDs (diminta dengan Vendor: djangoproject, Product: django) dan tambalan untuk setiap masalah yang sedang diperbaiki. Juga, notify django-announce of the upcoming security release.

    2. \n

  2. Ketika terbitan mendekat. lihat Trac untuk memastikan tidak ada pemblok terbitan tertinggal untuk terbitan akan datang.

    3. \n

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

    4. \n

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

    5. \n

  5. Periksa kembali itu catatan terbitan menyebutkan linimasa pengusangan untuk setiap API dicatat sebagai diusangkan, dan mereka menyebut bahwa tiap perubahan di Python versi dukungan.

    6. \n

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

    7. \n

  7. If this is a feature release, ensure translations from Transifex have been\nintegrated. This is typically done by a separate translation's manager\nrather than the releaser, but here are the steps. Provided you have an\naccount on Transifex:

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

    and then commit the changed/added files (both .po and .mo).\nSometimes there are validation errors which need to be debugged, so avoid\ndoing this task immediately before a release is needed.

    \n
    8. \n

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

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

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

Bersiap untuk terbitanLink to this heading#

\n

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.

\n
\n
\n

Sebenarnya menggulir terbitanLink to this heading#

\n

OKE, ini adalah bagian menyenangkan, dimana kami sebenarnya mendorong terbitan!

\n
    \n

  1. Periksa Jenkins adalah hijau untuk versi anda hasilkan. Anda mungkin tidak harus mengeluarkan terbitan sampai itu hijau.

    \n
    2. \n

  2. A release always begins from a release branch, so you should make sure\nyou're on a stable branch and up-to-date. For example:

    \n
    Shell
    $ git checkout stable/4.1.x\n$ git pull\n
    \n
    3. \n

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

  4. For a feature release, remove the UNDER DEVELOPMENT header at the\ntop of the release notes and add the release date on the next line. For a\npatch release, remove the Expected prefix and update the release date,\nif necessary. Make this change on all branches where the release notes for a\nparticular version are located.

    5. \n

  5. Perbaharui angka versi di django/__init__.py untuk terbitan. Silahkan lihat notes on setting the VERSION tuple dibawah ini untuk rincian pada VERSION.

    \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. Otherwise, make sure the classifier is set to\nDevelopment Status :: 5 - Production/Stable.

      3. \n
    \n
    6. \n

  6. Tag the release using git tag. For example:

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

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

    \n
    7. \n

  7. Dorong pekerjaan anda, termasuk etiket: git push --tags.

    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. Generate the hashes of the release packages:

    \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

Jika anda sedang menerbitkan banyak terbitan, ulangi langkah ini untuk setiap terbitan.

\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. Upload 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
    Shell
    $ scp Django-* djangoproject.com:/home/www/www/media/releases/A.B\n
    \n

    Jika ini adalah terbitan alfa dari deretan baru, anda akan butuh membuat direktori A.B.

    \n
    2. \n

  2. Upload the checksum file(s):

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

  3. Test that the release packages install correctly using pip. Here's one\nmethod:

    \n
    Shell
    $ RELEASE_VERSION='4.1.1'\n$ MAJOR_VERSION=`echo $RELEASE_VERSION| cut -c 1-3`\n\n$ python -m venv django-pip\n$ . django-pip/bin/activate\n$ python -m pip install https://www.djangoproject.com/m/releases/$MAJOR_VERSION/Django-$RELEASE_VERSION.tar.gz\n$ deactivate\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$ deactivate\n
    \n

    Ini hanya percobaan dimana tarball tersedia (yaitu pengalihan hidup) dan dimana mereka memasang dengan benar, tetapi dia akan menangkap kesalahan-kesalahan bodoh.

    \n
    4. \n

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

    \n
    5. \n

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

    \n
    Shell
    $ twine upload -s 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. 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.

    \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 entries from manage_translations.py robots_txt from the\ncurrent stable branch in the django-docs-translations repository. For\nexample, when releasing Django 4.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, django-developers,\ndjango-users mailing lists, and the Django Forum. This should include a\nlink 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

  11. Add a link to the blog post in the topic of the #django IRC channel:\n/msg chanserv TOPIC #django new topic goes here.

    12. \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. If it's a final release, update the current stable branch and remove the\npre-release branch in the Django release process on Trac.

    4. \n

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

    5. \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. Buat sebuah obyek DocumentRelease baru di basisdata docs.djangoproject.com untuk dokumen versi baru, dan perbaharui docs/fixtures/doc_releases.json perlengkapan lengkap JSON, jadi orang tanpa akses ke BD produksi dapat masih menjalankan salinan terbaru dari situs dokumentasi.

    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. Remove .. versionadded::, .. versionadded::, and .. deprecated::\nannotations in the documentation from two releases ago. For example, in\nDjango 4.2, notes for 4.0 will be removed.

    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":"Bersiap untuk terbitan","anchor":"preparing-for-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/4.2/internals/"}],"prev":{"docname":"internals/git","title":"Gudang sumber kode Django","url":"/id/4.2/internals/git/"},"next":null,"formats":{"html":"/id/4.2/internals/howto-release-django/","markdown":"/id/4.2/internals/howto-release-django.md","json":"/id/4.2/internals/howto-release-django.json"},"source":"https://github.com/django/django/blob/stable/4.2.x/docs/internals/howto-release-django.txt","official":"https://docs.djangoproject.com/id/4.2/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"]}