我们总是感谢Django代码的补丁。确实，具有相关补丁的错误报告将比没有补丁的错误报告 更 快地得到修复。
\nIf you are fixing a really trivial issue, for example changing a word in the\ndocumentation, the preferred way to provide the patch is using GitHub pull\nrequests without a Trac ticket.
\n有关如何使用拉取请求的更多详细信息，请参见:doc:working-with-git
\n在一个全球有数百个贡献者的开源项目中，有效地管理沟通以避免重复工作并尽可能提高贡献者的效率是非常重要的。
\n因此，我们的政策是供贡献者“发布”工单，以便让其他开发人员知道正在处理特定的错误或功能。
\n如果您确定了要做出的贡献并且有能力解决（通过编程能力，Django内核知识水平和时间可用性来衡量），请按照以下步骤进行发表：
\nLogin using your GitHub account or create an account in our ticket\nsystem. If you have an account but have forgotten your password, you can\nreset it using the password reset page.
如果尚无此问题的工单，请在我们的 ticket tracker 工单追踪系统中创建一个。
If a ticket for this issue already exists, make sure nobody else has\nclaimed it. To do this, look at the "Owned by" section of the ticket.\nIf it's assigned to "nobody," then it's available to be claimed.\nOtherwise, somebody else may be working on this ticket. Either find another\nbug/feature to work on, or contact the developer working on the ticket to\noffer your help. If a ticket has been assigned for weeks or months without\nany activity, it's probably safe to reassign it to yourself.
Log into your account, if you haven't already, by clicking "GitHub Login"\nor "DjangoProject Login" in the upper left of the ticket page.
Claim the ticket by clicking the "assign to myself" radio button under\n"Action" near the bottom of the page, then click "Submit changes."
发布工单后，您有责任以合理及时的方式处理该工单。 如果您没有时间来处理它，请先取消发布或不发布它！
\n如果一两周内没有任何关于特定已发布工单的进展迹象，则另一位开发人员可能会要求您放弃该发布了的工单，以使其不再被垄断，而其他人也可以发布。
\n如果您已发布工单，并且要花很长时间（几天或几周）编写代码，请通过在工单上发布评论来使每个人都保持最新状态。如果您不提供定期更新，并且不响应进度报告的请求，则您对工单的要求可能会被撤消。
\n与往常一样，多交流好过少交流！
\nGoing through the steps of claiming tickets is overkill in some cases.
\nIn the case of small changes, such as typos in the documentation or small bugs\nthat will only take a few minutes to fix, you don't need to jump through the\nhoops of claiming tickets. Submit your patch directly and you're done!
\nIt is always acceptable, regardless whether someone has claimed it or not, to\nsubmit patches to a ticket if you happen to have a patch ready.
\n确保您所做的任何贡献至少满足以下要求：
\n解决问题或添加功能所需的代码是补丁的重要组成部分，但不是唯一的部分。 一个好的补丁程序还应该包括一个 regression test 1 回归测试以验证已修复的行为并防止问题再次出现。 另外，如果某些工单与您编写的代码相关，请在测试中的一些注释中提及工单编号，以便在提交补丁程序并关闭工单后可以轻松地追溯相关的讨论。
如果与修补程序关联的代码添加了新功能或修改了现有功能的行为，则该修补程序还应包含文档。
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.
\nIf you can't send a pull request for some reason, you can also use patches in\nTrac. When using this style, follow these guidelines.
\nSubmit patches in the format returned by the git diff command.
使用“附加文件”按钮将补丁附加到 ticket tracker 工单跟踪系统中的工单上。 除非是单行补丁，否则请 不要 将补丁放入工单描述或注释中。
用扩展名 .diff 命名补丁文件； 这将使工单跟踪系统应用正确的语法突出显示，这非常有帮助。
无论您以何种方式提交工作成果，请按照以下步骤操作。
\nMake sure your code fulfills the requirements in our patch review\nchecklist.
Check the "Has patch" box on the ticket and make sure the "Needs\ndocumentation", "Needs tests", and "Patch needs improvement" boxes aren't\nchecked. This makes the ticket appear in the "Patches needing review" queue\non the Development dashboard.
A "non-trivial" patch is one that is more than a small bug fix. It's a patch\nthat introduces Django functionality and makes some sort of design decision.
\nIf you provide a non-trivial patch, include evidence that alternatives have\nbeen discussed on django-developers.
\nIf you're not sure whether your patch should be considered non-trivial, ask on\nthe ticket for opinions.
\nThere are a couple of reasons that code in Django might be deprecated:
\nIf a feature has been improved or modified in a backwards-incompatible way,\nthe old feature or behavior will be deprecated.
Sometimes Django will include a backport of a Python library that's not\nincluded in a version of Python that Django currently supports. When Django\nno longer needs to support the older version of Python that doesn't include\nthe library, the library will be deprecated in Django.
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 -Wa runtests.py. Thus, when adding a RemovedInDjangoXXWarning\nyou need to eliminate or silence any warnings generated when running the tests.
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:
In a particular test:
\nfrom django.test import ignore_warnings\nfrom django.utils.deprecation import RemovedInDjangoXXWarning\n\n@ignore_warnings(category=RemovedInDjangoXXWarning)\ndef test_foo(self):\n ...\nFor an entire test case:
\nfrom django.test import ignore_warnings\nfrom django.utils.deprecation import RemovedInDjangoXXWarning\n\n@ignore_warnings(category=RemovedInDjangoXXWarning)\nclass MyDeprecatedTests(unittest.TestCase):\n ...\nYou can also add a test for the deprecation warning:
\nfrom django.utils.deprecation import RemovedInDjangoXXWarning\n\ndef test_foo_deprecation_warning(self):\n msg = 'Expected deprecation message'\n with self.assertWarnsMessage(RemovedInDjangoXXWarning, msg):\n # invoke deprecated behavior\nFinally, there are a couple of updates to Django's documentation to make:
\nIf 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.
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.
Add an entry in the deprecation timeline (docs/internals/deprecation.txt)\nunder the appropriate version describing what code will be removed.
Once you have completed these steps, you are finished with the deprecation.\nIn each feature release, all\nRemovedInDjangoXXWarnings matching the new version are removed.
For information on JavaScript patches, see the JavaScript patches\ndocumentation.
\nUse 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, mergers do final reviews of "Ready for checkin" tickets\nand will either commit the patch or bump it back to "Accepted" if further works\nneed to be done. If you're looking to become a merger, doing thorough reviews\nof patches is a great way to earn trust.
\nLooking 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.
\nDoes the documentation build without any errors (make html, or\nmake.bat html on Windows, from the docs directory)?
Does the documentation follow the writing style guidelines in\n编写文档?
Are there any spelling errors?
Is there a proper regression test (the test should fail before the fix\nis applied)?
If it's a bug that qualifies for a backport\nto the stable version of Django, is there a release note in\ndocs/releases/A.B.C.txt? Bug fixes that will be applied only to the main\nbranch don't need a release note.
Are there tests to "exercise" all of the new code?
Is there a release note in docs/releases/A.B.txt?
Is there documentation for the feature and is it annotated\nappropriately with\n.. versionadded:: A.B or .. versionchanged:: A.B?
See the Deprecating a feature guide.
\nDoes the coding style conform to our\nguidelines? Are there any black, flake8, or isort errors? You\ncan install the pre-commit hooks to\nautomatically catch these errors.
If the change is backwards incompatible in any way, is there a note\nin the release notes (docs/releases/A.B.txt)?
Is Django's test suite passing?
Is the pull request a single squashed commit with a message that follows our\ncommit message format?
Are you the patch author and a new contributor? Please add yourself to the\nAUTHORS file and submit a Contributor License Agreement.