{"title":"Mendahulukan tiket","version":"5.2","locale":"id","docname":"internals/contributing/triaging-tickets","url":"/id/5.2/internals/contributing/triaging-tickets/","canonical":"https://djangodocs.dev/id/5.2/internals/contributing/triaging-tickets/","summary":"Django uses Trac for managing the work on the code base. Trac is a community-tended garden of the bugs people have found and the features Django has decided…","html":"

Mendahulukan tiketLink to this heading#

\n

Django uses Trac for managing the work on the code base. Trac is a\ncommunity-tended garden of the bugs people have found and the features Django\nhas decided to add. As in any garden, sometimes there are weeds to be pulled\nand sometimes there are flowers and vegetables that need picking. We need your\nhelp to sort out one from the other, and in the end, we all benefit together.

\n

Like all gardens, we can aspire to perfection, but in reality there's no such\nthing. Even in the most pristine garden there are still snails and insects.\nIn a community garden there are also helpful people who -- with the best of\nintentions -- fertilize the weeds and poison the roses. It's the job of the\ncommunity as a whole to self-manage, keep the problems to a minimum, and\neducate those coming into the community so that they can become valuable\ncontributing members.

\n

Demikan pula, selagi kita menyasar untuk Trac menjadi perwakilan sempurna dari keadaan kemajuan Django, kami mengakui bahwa ini tidak akan terjadi. Dengan menyebarkan muatan perawatan Trac ke komunitas, kami menerima bahwa ada kesalahan. Trac "kebanyakan paling akurat", dan kami memberikan kelonggaran untuk fakta bahwa terkadang itu akan salah. Tidak mengapa. Kami ingin sempurna dengan tenggat waktu.

\n

We rely on the community to keep participating, keep tickets as accurate as\npossible, and raise issues for discussion on the Django Forum when there is\nconfusion or disagreement.

\n

Django adalah proyek komunitas, dan setiap bantuan membantu. Kami tidak dapat melakukan ini tanpa anda!

\n
\n

Alur kerja TriageLink to this heading#

\n

Unfortunately, not all reports in the ticket tracker provide all the\nrequired details. A number of tickets have proposed\nsolutions, but those don't necessarily meet all the requirements adhering\nto the guidelines for contributing.

\n

Satu cara untuk membantu adalah memberikan tiket yang telah dibuat oleh pengguna lain.

\n

Kebanyakan alurkerja berdasarkan seputar konsep dari triage stages tiket. Setiap tahapan menggambarkan dimana didalam siklus hidupnya tiket yang diberikan adalah kapan saja. Bersama dengan bendera-bendera yang sangat membantu, atribut ini dengan mudah memberitahu kami bahwa apa dan siapa setiap tiket sedang menunggu.

\n

Sejak gambar berharga seribu kata, mari kita mulai disana:

\n\"Alur\n\n

Kami telah mendapat dua peran pada diagram ini:

\n\n

Sebagai contoh, disini kita melihat daur hidup dari sebuah tiket rata-rata:

\n\n

Beberapa tiket membutuhkan sedikit umpan balik daripada ini, tapi kembali lagi beberapa tiket membutuhkan lebih banyak.

\n
\n
\n

Tahapan-tahapan TriageLink to this heading#

\n

Dibawah ini kami menggambarkan dalam lebih rinci beragam tingkatan dimana sebuah tiket mungkin mengalir selama siklus hidupnya.

\n
\n

Belum ditinjauLink to this heading#

\n

The ticket has not been reviewed by anyone who felt qualified to make a\njudgment about whether the ticket contained a valid issue or ought to be closed\nfor any of the various reasons.

\n
\n
\n

DiterimaLink to this heading#

\n

Kawasan abu-abu besar! Arti mutlak dari "diterima" adalah bahwa masalah digambarkan dalam tiket adalah sah dan dalam beberapa tingkatan sedang dikerjakan. Diluar itu ada beberapa pertimbangan:

\n\n
\n
\n

Siap Untuk MendaftarLink to this heading#

\n

The ticket was reviewed by any member of the community other than the person\nwho supplied the patch and found to meet all the requirements for a\ncommit-ready contribution. A merger now needs to give\na final review prior to being committed.

\n

There are a lot of pull requests. It can take a while for your patch to get\nreviewed. See the contributing code FAQ for some\nideas here.

\n
\n
\n

Suatu hari/MungkinLink to this heading#

\n

This stage isn't shown on the diagram. It's used sparingly to keep track of\nlong-term changes.

\n

Tiket ini tidak umum dan secara keseluruhan kurang berguna sejak mereka tidak menggambarkan masalah nyata yang dapat ditindaklanjuti.

\n
\n
\n
\n

Atribut triage lainnyaLink to this heading#

\n

Sejumlah bendera, muncul sebagai kotak centang di Trac, dapat di setel di tiket:

\n
\n

Memiliki TambalanLink to this heading#

\n

Ini berarti tiket tersebut memiliki solusi terkait. Solusi ini akan ditinjau untuk memastikan kesesuaiannya dengan documented guidelines.

\n

Tiga bidang berikut (Butuh dokumentasi, Butuh percobaan, Tambalan butuh perbaikan) berlaku jika sebuah tambalan telah dipasok.

\n
\n
\n

Butuh dokumentasiLink to this heading#

\n

Bendera ini digunakan untuk tiket dengan tambalan yang butuh dokumentasi terkait. Dokumentasi lengkap dari fitur adalah prasyarat sebelum kami dapat memerika mereka ke dalam basiskode.

\n
\n
\n

Butuh pengujianLink to this heading#

\n

This flags the patch as needing associated unit tests. Again, this\nis a required part of a valid contribution.

\n
\n
\n

Tambalan butuh perbaikanLink to this heading#

\n

This flag means that although the ticket has a solution, it's not quite\nready for checkin. This could mean the patch no longer applies\ncleanly, there is a flaw in the implementation, or that the code\ndoesn't meet our standards.

\n
\n
\n

Pengambilan mudahLink to this heading#

\n

Tiket yang akan membutuhkan kecil, mudah, perubahan.

\n
\n
\n

TipeLink to this heading#

\n

Tiket harus dikelompokkan berdasarkan jenis diantara:

\n\n
\n
\n

KomponenLink to this heading#

\n

Tiket harus dikelompokkan kedalam komponen menandakan milik kawasan mana dari basiskode Django. Ini membuat tiket lebih baik tersusun dan lebih mudah ditemukan.

\n
\n
\n

KesederhanaanLink to this heading#

\n

The severity attribute is used to identify blockers, that is, issues that\nshould get fixed before releasing the next version of Django. Typically those\nissues are bugs causing regressions from earlier versions or potentially\ncausing severe data losses. This attribute is quite rarely used and the vast\nmajority of tickets have a severity of "Normal".

\n
\n
\n

VersiLink to this heading#

\n

Itu dimungkinkan menggunakan atribut versi untuk menandakan versi mana kesalahan dilaporkan telah dicirikan.

\n
\n
\n

UI/UXLink to this heading#

\n

Bendera ini digunakan untuk tiket yang terkait ke Antarmuka Pengguna dan pertanyaan Pengalaman pengguna. Sebagai contoh, bendera ini akan sesuai untuk pengguna-menghadapi fitur dalam formulir atau antarmuka admin.

\n
\n
\n

CcLink to this heading#

\n

Anda mungkin menambahkan nama pengguna atau alamt surel ke bidang ini untuk diberitahu ketika bantuan baru dibuat ke tiket.

\n
\n
\n

Kata kunciLink to this heading#

\n

With this field you may label a ticket with multiple keywords. This can be\nuseful, for example, to group several tickets on the same theme. Keywords can\neither be comma or space separated. Keyword search finds the keyword string\nanywhere in the keywords. For example, clicking on a ticket with the keyword\n"form" will yield similar tickets tagged with keywords containing strings such\nas "formset", "modelformset", and "ManagementForm".

\n
\n
\n
\n

Menutup TiketLink to this heading#

\n

When a ticket has completed its useful lifecycle, it's time for it to be\nclosed. Closing a ticket is a big responsibility, though. You have to be sure\nthat the issue is really resolved, and you need to keep in mind that the\nreporter of the ticket may not be happy to have their ticket closed (unless\nit's fixed!). If you're not certain about closing a ticket, leave a comment\nwith your thoughts instead.

\n

Jika anda menutup sebuah tiket, anda harus selalu memastikan berikut:

\n\n

Sebuah tiket dapat diselesaikan dalam sejumlah jalan:

\n\n

If you believe that the ticket was closed in error -- because you're\nstill having the issue, or it's popped up somewhere else, or the triagers have\nmade a mistake -- please reopen the ticket and provide further information.\nAgain, please do not reopen tickets that have been marked as "wontfix" and\nbring the issue to the Django Forum instead.

\n
\n
\n

Bagaimana saya dapat membantu dengan penyortiran?Link to this heading#

\n

Pengolahan penyortiran adalah utamanya dikendalikan oleh anggota komunitas. Benar, SIAPAPUN dapat membantu.

\n

Untuk ikut serta, mulai dengan membuat sebuah akun pada Trac. Jika anda mempunyai sebuah akun tetapi lupa sandi anda, anda dapat menyetel kembali menggunakan password reset page.

\n

lalu, anda dapat membantu dengan:

\n\n\n

Bagaimanapun, kami meminta berikut semua anggota komunitas umum yang bekerja di basisdata tiket:

\n\n
\n
\n

Membagi dua pemulihanLink to this heading#

\n

Pemulihan adalah sebuah kesalahan yang hadir dalam beberapa versi terbaru dari Django tetapi tidak di versi lama. Sepotong informasi sangat membantu adalah perbaikan yang memperkenalkan pemulihan. Sepengetahuan penyerahan yang menyebabkan perubahan dalam kebiasaan membantu mencirikan jika perubahan disengaja atau jika itu efek samping tidak sengaja. Disini bagaimana anda dapat menentukan ini.

\n

Begin by writing a regression test for Django's test suite for the issue. For\nexample, we'll pretend we're debugging a regression in migrations. After you've\nwritten the test and confirmed that it fails on the latest main branch, put it\nin a separate file that you can run standalone. For our example, we'll pretend\nwe created tests/migrations/test_regression.py, which can be run with:

\n
Shell
$ ./runtests.py migrations.test_regression\n
\n

Selanjutnya, kami menandari titik saat ini di riwayat menjadi "bad" sejak kegagalan pengujian:

\n
Shell
$ git bisect bad\nYou need to start by "git bisect start"\nDo you want me to do it for you [Y/n]? y\n
\n

Now, we need to find a point in git history before the regression was\nintroduced (i.e. a point where the test passes). Use something like\ngit checkout HEAD~100 to check out an earlier revision (100 commits earlier,\nin this case). Check if the test fails. If so, mark that point as "bad"\n(git bisect bad), then check out an earlier revision and recheck. Once you\nfind a revision where your test passes, mark it as "good":

\n
Shell
$ git bisect good\nBisecting: X revisions left to test after this (roughly Y steps)\n...\n
\n

Sekarang kami siap untuk bagian yang menyenangkan menggunakan git bisect run untuk mengotomatiskan sisa proses:

\n
Shell
$ git bisect run tests/runtests.py migrations.test_regression\n
\n

Anda seharusnya melihat git bisect menggunakan pencarian biner untuk otomatis periksa perbaikan diantara perbaikan baik dan buruk sampai dia menemukan perbaikan "buruk" dimana percobaan gagal.

\n

Sekarang, laporkan hasil anda di tiket Trac, dan silahkan sertakan percobaan pemulihan sebagai sebuah lampiran. Ketika seseorang menulis perbaikan untuk kesalahan, mereka sudah akan memiliki percobaan anda sebagai sebuah titik permulaan.

\n
","rootId":"triaging-tickets","toc":[{"title":"Alur kerja Triage","anchor":"triage-workflow","children":[]},{"title":"Tahapan-tahapan Triage","anchor":"triage-stages","children":[{"title":"Belum ditinjau","anchor":"unreviewed","children":[]},{"title":"Diterima","anchor":"accepted","children":[]},{"title":"Siap Untuk Mendaftar","anchor":"ready-for-checkin","children":[]},{"title":"Suatu hari/Mungkin","anchor":"someday-maybe","children":[]}]},{"title":"Atribut triage lainnya","anchor":"other-triage-attributes","children":[{"title":"Memiliki Tambalan","anchor":"has-patch","children":[]},{"title":"Butuh dokumentasi","anchor":"needs-documentation","children":[]},{"title":"Butuh pengujian","anchor":"needs-tests","children":[]},{"title":"Tambalan butuh perbaikan","anchor":"patch-needs-improvement","children":[]},{"title":"Pengambilan mudah","anchor":"easy-pickings","children":[]},{"title":"Tipe","anchor":"type","children":[]},{"title":"Komponen","anchor":"component","children":[]},{"title":"Kesederhanaan","anchor":"severity","children":[]},{"title":"Versi","anchor":"version","children":[]},{"title":"UI/UX","anchor":"ui-ux","children":[]},{"title":"Cc","anchor":"cc","children":[]},{"title":"Kata kunci","anchor":"keywords","children":[]}]},{"title":"Menutup Tiket","anchor":"closing-tickets","children":[]},{"title":"Bagaimana saya dapat membantu dengan penyortiran?","anchor":"how-can-i-help-with-triaging","children":[]},{"title":"Membagi dua pemulihan","anchor":"bisecting-a-regression","children":[]}],"breadcrumbs":[{"docname":"internals/index","title":"Dalam Django","url":"/id/5.2/internals/"},{"docname":"internals/contributing/index","title":"Membantu untuk Django","url":"/id/5.2/internals/contributing/"}],"prev":{"docname":"internals/contributing/bugs-and-features","title":"Melaporkan kesalahan dan meminta fitur","url":"/id/5.2/internals/contributing/bugs-and-features/"},"next":{"docname":"internals/mailing-lists","title":"Daftar senarai surat dan Forum","url":"/id/5.2/internals/mailing-lists/"},"formats":{"html":"/id/5.2/internals/contributing/triaging-tickets/","markdown":"/id/5.2/internals/contributing/triaging-tickets.md","json":"/id/5.2/internals/contributing/triaging-tickets.json"},"source":"https://github.com/django/django/blob/stable/5.2.x/docs/internals/contributing/triaging-tickets.txt","official":"https://docs.djangoproject.com/id/5.2/internals/contributing/triaging-tickets/","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","sv","zh-hans","ga","fr","ja","id","it","pt-br","ko","es","el","pl"]}