{"title":"Mendahulukan tiket","version":"6.1","locale":"id","docname":"internals/contributing/triaging-tickets","url":"/id/6.1/internals/contributing/triaging-tickets/","canonical":"https://djangodocs.dev/id/6.1/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 to add.…","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

We have four roles in this diagram. Maintainers (also known as Fellows) usually\ntake part in all of them, but anyone in the Django community can participate in\nany role except merger. The merger role is granted by a\nvote of the Steering Council.

\n\n\n

For example, here's the typical lifecycle of a ticket:

\n\n

Some tickets move through these steps quickly, while others take more time and\ndiscussion. Each contribution helps Django improve.

\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 reasons. Unreviewed tickets appear in the "triage" queue.

\n

Unreviewed tickets may receive additional refinement before being accepted.\nUnless you are both the author of the ticket and intending to submit a patch,\nunreviewed tickets should not be claimed.

\n
\n
\n

DiterimaLink to this heading#

\n

The absolute meaning of "accepted" is that the issue described in the ticket is\nvalid and actionable. It is broken out into three queues:

\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

This means the ticket has an associated solution. These will be reviewed to\nensure they adhere to the 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

The version attribute indicates the earliest version in which the bug was\nreproduced. During triage, this field can be updated, but there is no need to\nmake further updates when that version goes out of support. The field should\nnot be reset to "dev" to show the issue still exists: instead, the tested\ncommit hash can be noted in a comment.

\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" or\n"needsnewfeatureprocess". For "wontfix" tickets, bring the issue to the\nDjango Forum instead. For "needsnewfeatureprocess" tickets, propose the\nfeature through the new features process.

\n
\n
\n

How can I help with development?Link to this heading#

\n

The development process is primarily driven by community members. Really,\nANYONE can help.

\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\nearlier, in this case). Check if the test fails. If so, mark that point as\n"bad" (git bisect bad), then check out an earlier revision and recheck.\nOnce you find 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
\n
\n

Reviewing patchesLink to this heading#

\n

A great way to learn the Django codebase is to help review patches. It allows\nyou to focus on a fixed scope of Django with a particular perspective. Plus,\nDjango tends to receive more patches than it can review which causes the\nreview queue to build up. Contributors can help Django tremendously by\nreviewing patches.

\n

The review queue is defined by tickets in Trac that are in the "Accepted"\nstate with the flag "has patch" set and the flags "patch needs improvement",\n"needs tests" and "needs documentation" unset. There is also a set of\nPull Requests in GitHub with the "no ticket" label that can be reviewed.

\n
\n

Code review processLink to this heading#

\n

The general process to reviewing a patch for Django is as follows:

\n
    \n

  1. Pick a patch to review. This can be from the review queue or the\nPull Requests in GitHub with the "no ticket" label. If you're new, pick\na specific component to stick with. Django is a big codebase, so it's best\nto contribute consistently with a narrow focus and grow it slowly.

    2. \n

  2. Pull the branch. See the Penanganan pull request, including the git\nalias to make checking out other pull requests easier.

    3. \n

  3. Check the tests. If the ticket is for a bug, there should be a regression\ntest. Confirm that the test fails if the change is reverted. Check that the\ntests are adequately covering the code and logic as well. See\nDaftar centang bantuan.

    4. \n

  4. Test in your own Django project. See Memasang versi pengembangan\nfor how. Explore the user interface and user experience with the change.\nDoes it feel right? Can you break it? Another approach is to assume\neverything is wrong. Can you demonstrate to yourself that each piece is\ncorrect?

    5. \n

  5. Check the documentation. Is the documentation understandable? Does it\nprovide the information the reader needs at that moment? Does it read well?\nIs it consistent with the documentation before and after it? See\nBangun dokumentasi lokal.

    6. \n

  6. Are you happy with the patch? This is fairly subjective, but that's fine.\nYou should ask, does the approach make sense to you and is there another\nway to do it that's better? Also ask yourself, is the scope of the change\nappropriate? Are things named appropriately? Renaming things is slow and\nchallenging in Django, so we should try to get it right from the start.\nAre there backwards compatibility concerns? Lastly, are there any other\ngeneral concerns such as things that may worry you or that should be looked\ninto?

    7. \n

  7. Review your feedback. Before you submit your feedback, consider the\nfeedback you want to share. It takes courage to open a Pull Request, we\nshould be thoughtful and considerate of the leap the author has made. If\nthere are nitpicky or small suggestions, use GitHub's suggestion feature.\nIf the approach isn't what you expected, consider asking the author why\nbefore requesting several changes. Seek to understand their reasoning\nfirst.

    8. \n

  8. Submit feedback on GitHub and update flags, "patch needs improvement",\n"needs tests", and "needs documentation", as needed. This will move the\nticket to the "waiting for author" queue. If you have given a\nspecific type of code review, please indicate that on the Pull Request.

    9. \n
\n
\n
\n

Types of code reviewsLink to this heading#

\n

Not everyone will or should give the same type of code review. Having a diverse\nset of opinions and experiences helps Django be better. If you are providing a\nspecific review, please indicate that on the Pull Request in GitHub. Below\nare some of the types of code review you can perform:

\n\n
\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":"How can I help with development?","anchor":"how-can-i-help-with-development","children":[]},{"title":"Membagi dua pemulihan","anchor":"bisecting-a-regression","children":[]},{"title":"Reviewing patches","anchor":"reviewing-patches","children":[{"title":"Code review process","anchor":"code-review-process","children":[]},{"title":"Types of code reviews","anchor":"types-of-code-reviews","children":[]}]}],"breadcrumbs":[{"docname":"internals/index","title":"Dalam Django","url":"/id/6.1/internals/"},{"docname":"internals/contributing/index","title":"Membantu untuk Django","url":"/id/6.1/internals/contributing/"}],"prev":{"docname":"internals/contributing/bugs-and-features","title":"Melaporkan kesalahan dan meminta fitur","url":"/id/6.1/internals/contributing/bugs-and-features/"},"next":{"docname":"internals/mailing-lists","title":"Daftar senarai surat dan Forum","url":"/id/6.1/internals/mailing-lists/"},"formats":{"html":"/id/6.1/internals/contributing/triaging-tickets/","markdown":"/id/6.1/internals/contributing/triaging-tickets.md","json":"/id/6.1/internals/contributing/triaging-tickets.json"},"source":"https://github.com/django/django/blob/stable/6.1.x/docs/internals/contributing/triaging-tickets.txt","official":"https://docs.djangoproject.com/id/6.1/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"]}