{"title":"Mengajukan tambalan","version":"1.9","locale":"id","docname":"internals/contributing/writing-code/submitting-patches","url":"/id/1.9/internals/contributing/writing-code/submitting-patches/","canonical":"https://djangodocs.dev/id/1.9/internals/contributing/writing-code/submitting-patches/","summary":"Kami semua selalu berterima kasih untuk tambalan-tambalan pada kode Django. Memang, laporan kesalahan dengan tambalan terhubung akan diperbaiki jauh lebih…","html":"

Mengajukan tambalanLink to this heading#

\n

Kami semua selalu berterima kasih untuk tambalan-tambalan pada kode Django. Memang, laporan kesalahan dengan tambalan terhubung akan diperbaiki jauh lebih cepat daripada mereka yang tanpa tambalan.

\n
\n

Perbaikan kesalahan ketik dan perubahan dokumentasi sepele.Link to this heading#

\n

Jika anda sedang memperbaiki masalah sepele, sebagai contoh merubah sebuah kata di dokumentasi, cara dipilih untuk menyediakan tambalan adalah menggunakan menarik permintaan Github tanpa tiket Trac.

\n

Lihat Bekerja dengan Git dan GitHub untuk tincian lebih bagaimana menggunakan penarian permintaan.

\n
\n
\n

Tiket "Meminta"Link to this heading#

\n

In an open-source project with hundreds of contributors around the world, it's\nimportant to manage communication efficiently so that work doesn't get\nduplicated and contributors can be as effective as possible.

\n

Hence, our policy is for contributors to "claim" tickets in order to let other\ndevelopers know that a particular bug or feature is being worked on.

\n

If you have identified a contribution you want to make and you're capable of\nfixing it (as measured by your coding ability, knowledge of Django internals\nand time availability), claim it by following these steps:

\n\n\n
\n

Ticket claimers' responsibilityLink to this heading#

\n

Once you've claimed a ticket, you have a responsibility to work on that ticket\nin a reasonably timely fashion. If you don't have time to work on it, either\nunclaim it or don't claim it in the first place!

\n

If there's no sign of progress on a particular claimed ticket for a week or\ntwo, another developer may ask you to relinquish the ticket claim so that it's\nno longer monopolized and somebody else can claim it.

\n

If you've claimed a ticket and it's taking a long time (days or weeks) to code,\nkeep everybody updated by posting comments on the ticket. If you don't provide\nregular updates, and you don't respond to a request for a progress report,\nyour claim on the ticket may be revoked.

\n

Seperti biasa, komunikasi lebih lebih baik dati pada komunikasi kurang!

\n
\n
\n

Tiket mana harus diminta?Link to this heading#

\n

Of course, going through the steps of claiming tickets is overkill in some\ncases.

\n

In the case of small changes, such as typos in the documentation or\nsmall bugs that will only take a few minutes to fix, you don't need to jump\nthrough the hoops of claiming tickets. Just submit your patch and be done with\nit.

\n

Of course, it is always acceptable, regardless whether someone has claimed it\nor not, to submit patches to a ticket if you happen to have a patch ready.

\n
\n
\n
\n

Gaya tambalanLink to this heading#

\n

Make sure that any contribution you do fulfills at least the following\nrequirements:

\n\n

When you think your work is ready to be reviewed, send a GitHub pull\nrequest. Please review the patch yourself using our\npatch review checklist first.

\n

If you can't send a pull request for some reason, you can also use patches in\nTrac. When using this style, follow these guidelines.

\n\n

Tanpa memperhatikan cara anda mengajukan pekerjaan anda, ikuti langkah-langkah ini.

\n\n
\n
\n

Tambalan bukan sepeleLink to this heading#

\n

Tambalan "bukan-sepele" adalah satu yang lebih dari sebuah perbaikan kesalahan sederhana. Itu adalah sebuah tambalan yang memperkenalkan fungsi Django dan membuat beberapa urutan keputusan rancangan.

\n

Jika anda menyediakan tambalan bukan-sepele, sertakan saksi yang jalan lain telah diobrolkan di django-developers.

\n

Jika anda tidak yakin apakah tambalan anda harus dipertimbangkan bukan-sepele, tanya saja.

\n
\n
\n

Mengusangkan fiturLink to this heading#

\n

Terdapat beberapa alasan bahwa kode di Django mungkin diusangkan:

\n\n

As the deprecation policy describes,\nthe first release of Django that deprecates a feature (A.B) should raise a\nRemovedInDjangoXXWarning (where XX is the Django version where the feature\nwill be removed) when the deprecated feature is invoked. Assuming we have good\ntest coverage, these warnings are converted to errors when running the\ntest suite with warnings enabled:\npython -Wall runtests.py. Thus, when adding a RemovedInDjangoXXWarning\nyou need to eliminate or silence any warnings generated when running the tests.

\n

The first step is to remove any use of the deprecated behavior by Django itself.\nNext you can silence warnings in tests that actually test the deprecated\nbehavior by using the ignore_warnings decorator, either at the test or class\nlevel:

\n
    \n

  1. Di percobaan khusus:

    \n
    Code
    from django.test import ignore_warnings\nfrom django.utils.deprecation import RemovedInDjangoXXWarning\n\n@ignore_warnings(category=RemovedInDjangoXXWarning)\ndef test_foo(self):\n    ...\n
    \n
    2. \n

  2. Untuk kasus percobaan keseluruhan:

    \n
    Code
    from django.test import ignore_warnings\nfrom django.utils.deprecation import RemovedInDjangoXXWarning\n\n@ignore_warnings(category=RemovedInDjangoXXWarning)\nclass MyDeprecatedTests(unittest.TestCase):\n    ...\n
    \n
    3. \n
\n\n

Anda dapat juga menambahkan sebuah percobaan untuk peringatan pengusangan. Anda harus meniadakan kebiasaan "peringatan sebagai kesalahan" di percobaan anda dengan melakukan:

\n
Code
import warnings\n\ndef test_foo_deprecation_warning(self):\n    with warnings.catch_warnings(record=True) as warns:\n        warnings.simplefilter('always')  # prevent warnings from appearing as errors\n        # invoke deprecated behavior\n\n    self.assertEqual(len(warns), 1)\n    msg = str(warns[0].message)\n    self.assertEqual(msg, 'Expected deprecation message')\n
\n

Akhirnya, ada sepasang pembaharuan ke dokumentasi Django untuk dibuat:

\n
    \n

  1. If the existing feature is documented, mark it deprecated in documentation\nusing the .. deprecated:: A.B annotation. Include a short description\nand a note about the upgrade path if applicable.

    2. \n

  2. Add a description of the deprecated behavior, and the upgrade path if\napplicable, to the current release notes (docs/releases/A.B.txt) under\nthe "Features deprecated in A.B" heading.

    3. \n

  3. Add an entry in the deprecation timeline (docs/internals/deprecation.txt)\nunder the appropriate version describing what code will be removed.

    4. \n
\n

Once you have completed these steps, you are finished with the deprecation.\nIn each feature release, all RemovedInDjangoXXWarnings matching\nthe new version are removed.

\n
\n
\n

Tambalan JavaScriptLink to this heading#

\n

Untuk informasi pada tambalan JavaScript, lihat dokumentasi Tambalan JavaScript.

\n
\n
\n

Daftar centang pratinjau tambalanLink to this heading#

\n

Use this checklist to review a pull request. If you are reviewing a pull\nrequest that is not your own and it passes all the criteria below, please set\nthe "Triage Stage" on the corresponding Trac ticket to "Ready for checkin".\nIf you've left comments for improvement on the pull request, please tick the\nappropriate flags on the Trac ticket based on the results of your review:\n"Patch needs improvement", "Needs documentation", and/or "Needs tests". As time\nand interest permits, core developers do final reviews of "Ready for checkin"\ntickets and will either commit the patch or bump it back to "Accepted" if\nfurther works need to be done. If you're looking to become a core developer,\ndoing thorough reviews of patches is a great way to earn trust.

\n

Looking for a patch to review? Check out the "Patches needing review" section\nof the Django Development Dashboard.\nLooking to get your patch reviewed? Ensure the Trac flags on the ticket are\nset so that the ticket appears in that queue.

\n
\n

DokumentasiLink to this heading#

\n\n
\n
\n

KesalahanLink to this heading#

\n\n
\n
\n

Fitur BaruLink to this heading#

\n\n
\n
\n

Mengusangkan fiturLink to this heading#

\n

Lihat panduan Mengusangkan fitur.

\n
\n
\n

Semua kode perubahanLink to this heading#

\n\n
\n
\n

Semua tiketLink to this heading#

\n\n
\n
","rootId":"submitting-patches","toc":[{"title":"Perbaikan kesalahan ketik dan perubahan dokumentasi sepele.","anchor":"typo-fixes-and-trivial-documentation-changes","children":[]},{"title":"Tiket \"Meminta\"","anchor":"claiming-tickets","children":[{"title":"Ticket claimers' responsibility","anchor":"ticket-claimers-responsibility","children":[]},{"title":"Tiket mana harus diminta?","anchor":"which-tickets-should-be-claimed","children":[]}]},{"title":"Gaya tambalan","anchor":"patch-style","children":[]},{"title":"Tambalan bukan sepele","anchor":"non-trivial-patches","children":[]},{"title":"Mengusangkan fitur","anchor":"deprecating-a-feature","children":[]},{"title":"Tambalan JavaScript","anchor":"javascript-patches","children":[]},{"title":"Daftar centang pratinjau tambalan","anchor":"patch-review-checklist","children":[{"title":"Dokumentasi","anchor":"documentation","children":[]},{"title":"Kesalahan","anchor":"bugs","children":[]},{"title":"Fitur Baru","anchor":"new-features","children":[]},{"title":"Mengusangkan fitur","anchor":"id4","children":[]},{"title":"Semua kode perubahan","anchor":"all-code-changes","children":[]},{"title":"Semua tiket","anchor":"all-tickets","children":[]}]}],"breadcrumbs":[{"docname":"internals/index","title":"Dalam Django","url":"/id/1.9/internals/"},{"docname":"internals/contributing/index","title":"Membantu untuk Django","url":"/id/1.9/internals/contributing/"},{"docname":"internals/contributing/writing-code/index","title":"Penulisan kode","url":"/id/1.9/internals/contributing/writing-code/"}],"prev":{"docname":"internals/contributing/writing-code/unit-tests","title":"Satuan percobaan","url":"/id/1.9/internals/contributing/writing-code/unit-tests/"},"next":{"docname":"internals/contributing/writing-code/working-with-git","title":"Bekerja dengan Git dan GitHub","url":"/id/1.9/internals/contributing/writing-code/working-with-git/"},"formats":{"html":"/id/1.9/internals/contributing/writing-code/submitting-patches/","markdown":"/id/1.9/internals/contributing/writing-code/submitting-patches.md","json":"/id/1.9/internals/contributing/writing-code/submitting-patches.json"},"source":"https://github.com/django/django/blob/stable/1.9.x/docs/internals/contributing/writing-code/submitting-patches.txt","official":"https://docs.djangoproject.com/id/1.9/internals/contributing/writing-code/submitting-patches/","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","fr","ja","id","pt-br","es"]}