{"title":"バグレポートと機能のリクエスト","version":"6.0","locale":"ja","docname":"internals/contributing/bugs-and-features","url":"/ja/6.0/internals/contributing/bugs-and-features/","canonical":"https://djangodocs.dev/ja/6.0/internals/contributing/bugs-and-features/","summary":"重要 Please report security issues only to security@djangoproject.com . This is a private list only open to long-time, highly trusted Django developers, and its…","html":"

バグレポートと機能のリクエストLink to this heading#

\n\n
\n

バグレポートLink to this heading#

\n

Before reporting a bug on the ticket tracker consider these points:

\n\n

よく書かれたバグレポートは信じられないくらい有益です。しなしながら、バグチケットシステムの作業には手間がかかるため、チケットトラッカーを可能な限り便利に保つようにご協力をお願いします。特に、

\n\n

To understand the lifecycle of your ticket once you have created it, refer to\nトリアージのワークフロー.

\n
\n

Reporting user interface bugsLink to this heading#

\n

If your bug impacts anything visual in nature, there are a few additional\nguidelines to follow:

\n\n
\n
\n
\n

機能のリクエストLink to this heading#

\n

我々は常にDjangoをより良くしようと努めており、ユーザーからの機能のリクエストは重要なパーツになります。リクエストを最も効果的に行うためのヒントをいくつか示します。

\n\n

新機能のドキュメントを書く. も参照してください。

\n
\n
\n

Requesting performance optimizationsLink to this heading#

\n

Reports of a performance regression, or suggested performance optimizations,\nshould provide benchmarks and commands for the ticket triager to reproduce.

\n

See the django-asv benchmarks for more details of Django's existing\nbenchmarks.

\n
\n
\n

どのように決定が下されるかLink to this heading#

\n

Whenever possible, we aim for rough consensus. Emoji reactions are used on\nissues within the new feature ideas GitHub project to track community\nfeedback. The following meanings are assigned to each reaction:

\n\n

The Steering Council will regularly review the ideas\nin the project, moving those with community support through the following\nstages:

\n\n

Occasionally, discussions on feature ideas or the direction of Django may take\nplace on the Django Forum. These discussions may include informal votes, which\nfollow the voting style invented by Apache and used on Python itself, where\nvotes are given as +1, +0, -0, or -1.\nRoughly translated, these votes mean:

\n\n

これらの投票は非公式なものですが、非常に真摯に受け止められます。適切な投票期間の後、明らかなコンセンサスが得られれば、投票に従います。

\n
\n
\n

How to test pre-release versions of DjangoLink to this heading#

\n

Testing pre-releases is a great way to contribute to Django. Early testers\nhelp catch bugs before the final release, ensuring a smoother upgrade\nexperience for everyone.

\n
\n

PrerequisitesLink to this heading#

\n

Before testing a pre-release, it is important that your project is running\nsmoothly on the latest stable release of Django. That way, any regressions can\nbe attributed to the pre-release. See the Django の新しいバージョンへの更新 guide\nfor instructions on getting up to date.

\n

To ensure your project is ready, you should also:

\n\n
\n
\n

Testing your projectLink to this heading#

\n

You can install the latest pre-release using pip:

\n
Shell
$ python -m pip install --pre Django\n
\n

Once installed, run your project's test suite. Rather than just checking\nif tests pass, try the following:

\n\n
\n
\n

Reporting issuesLink to this heading#

\n

If you discover a bug, please report it via the Django issue tracker so it can be fixed before the final\nrelease. When creating the ticket, be sure to set the Django version field to\nthe exact pre-release version you are testing.

\n

If you suspect a regression, it's helpful to report the specific commit that\ncaused it. See リグレッションの bisect for instructions.

\n

You can also discuss any issues or share feedback in the Pre-releases category\non the Django Forum.

\n
\n
","rootId":"reporting-bugs-and-requesting-features","toc":[{"title":"バグレポート","anchor":"reporting-bugs","children":[{"title":"Reporting user interface bugs","anchor":"reporting-user-interface-bugs","children":[]}]},{"title":"機能のリクエスト","anchor":"requesting-features","children":[]},{"title":"Requesting performance optimizations","anchor":"requesting-performance-optimizations","children":[]},{"title":"どのように決定が下されるか","anchor":"how-we-make-decisions","children":[]},{"title":"How to test pre-release versions of Django","anchor":"how-to-test-pre-release-versions-of-django","children":[{"title":"Prerequisites","anchor":"prerequisites","children":[]},{"title":"Testing your project","anchor":"testing-your-project","children":[]},{"title":"Reporting issues","anchor":"reporting-issues","children":[]}]}],"breadcrumbs":[{"docname":"internals/index","title":"Django internals","url":"/ja/6.0/internals/"},{"docname":"internals/contributing/index","title":"Django へのコントリビュート","url":"/ja/6.0/internals/contributing/"}],"prev":{"docname":"internals/contributing/localizing","title":"Django のローカライズ","url":"/ja/6.0/internals/contributing/localizing/"},"next":{"docname":"internals/contributing/triaging-tickets","title":"チケットをトリアージする","url":"/ja/6.0/internals/contributing/triaging-tickets/"},"formats":{"html":"/ja/6.0/internals/contributing/bugs-and-features/","markdown":"/ja/6.0/internals/contributing/bugs-and-features.md","json":"/ja/6.0/internals/contributing/bugs-and-features.json"},"source":"https://github.com/django/django/blob/stable/6.0.x/docs/internals/contributing/bugs-and-features.txt","official":"https://docs.djangoproject.com/ja/6.0/internals/contributing/bugs-and-features/","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"]}