per page, with , order by , clip by
Results of 1 - 10 of about 14 for feedback (0.007 sec.)
新しいコントリビューターへのアドバイス — Django 6.1 ドキュメント 12411
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » 新しいコントリビューターへのアドバイス ¶ 新しいコントリビューターで、何をするべきかわかりませんか? 助けたいと思っているのにどこから手を付ければいいの ... sts and make sure they pass. Where possible and relevant, try them out on a database other than SQLite. Leave comments and feedback! Keep old patches up-to-date ¶ Oftentimes the codebase will change between a patch being submitted and the time it gets re ... に確認してもらうことや、実装する前に提案された機能についてコンセンサスが得られていることを確認することです。 Be bold! Leave feedback! ¶ 「このチケットは正しい」とか、「このパッチには作業が必要だ」とか、自分の意見を世界に発信するのは、時には怖いことかもしれ ... ributing-getting-started channel in the Django Discord server to see if someone else can confirm your suspicions. Wait for feedback, and respond to feedback that you receive ¶ 1つか2つのチケットに集中し、最初から最後まで見届け、それを繰り返します。たくさ ...
https://man.mtool.work/django/6.1/internals/contributing/new-contributors.html
新しいコントリビューターへのアドバイス — Django 6.1 ドキュメント 12411
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » 新しいコントリビューターへのアドバイス ¶ 新しいコントリビューターで、何をするべきかわかりませんか? 助けたいと思っているのにどこから手を付ければいいの ... sts and make sure they pass. Where possible and relevant, try them out on a database other than SQLite. Leave comments and feedback! Keep old patches up-to-date ¶ Oftentimes the codebase will change between a patch being submitted and the time it gets re ... に確認してもらうことや、実装する前に提案された機能についてコンセンサスが得られていることを確認することです。 Be bold! Leave feedback! ¶ 「このチケットは正しい」とか、「このパッチには作業が必要だ」とか、自分の意見を世界に発信するのは、時には怖いことかもしれ ... ributing-getting-started channel in the Django Discord server to see if someone else can confirm your suspicions. Wait for feedback, and respond to feedback that you receive ¶ 1つか2つのチケットに集中し、最初から最後まで見届け、それを繰り返します。たくさ ...
https://man.mtool.work/django/6.1/internals/contributing/new-contributors.html
チケットをトリアージする — Django 6.1 ドキュメント 9347
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » チケットをトリアージする ¶ Django uses Trac for managing the work on the code base. Trac is a community-tended garden of the bugs people have found ... and trying it out, verifying that it contains tests and docs, running the test suite with the included patch, and leaving feedback on the ticket. Waiting On Author (Accepted + Has Patch + Needs fixes) This means the ticket has been reviewed, and has bee ... Lastly, are there any other general concerns such as things that may worry you or that should be looked into? Review your feedback. Before you submit your feedback, consider the feedback you want to share. It takes courage to open a Pull Request, we sho ... pected, consider asking the author why before requesting several changes. Seek to understand their reasoning first. Submit feedback on GitHub and update flags, "patch needs improvement", "needs tests", and "needs documentation", as needed. This will move ...
https://man.mtool.work/django/6.1/internals/contributing/triaging-tickets.html
Submitting contributions — Django 6.1 ドキュメント 9347
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Submitting contributions ¶ We're always grateful for contributions to Django's code. Indeed, bug reports with associated contributions will get fixe ... ot comply with these rules, clearly call it out in the contribution and explain why. Contributions which require community feedback ¶ A wider community discussion is required when a patch introduces new Django functionality and makes some sort of design ... if the approach involves a deprecation or introduces breaking changes. The following are different approaches for gaining feedback from the community. The new feature ideas tracker ¶ If you have an idea for a new feature, please create a new proposal (o ... ollow our deprecation policy . Hence, it can take months or years for Django to iterate on an API design. If you need user feedback on a public interface, it is better to create a third-party package first. You can iterate on the public API much faster, ...
https://man.mtool.work/django/6.1/internals/contributing/writing-code/submitting...
チケットをトリアージする — Django 6.1 ドキュメント 9347
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » チケットをトリアージする ¶ Django uses Trac for managing the work on the code base. Trac is a community-tended garden of the bugs people have found ... and trying it out, verifying that it contains tests and docs, running the test suite with the included patch, and leaving feedback on the ticket. Waiting On Author (Accepted + Has Patch + Needs fixes) This means the ticket has been reviewed, and has bee ... Lastly, are there any other general concerns such as things that may worry you or that should be looked into? Review your feedback. Before you submit your feedback, consider the feedback you want to share. It takes courage to open a Pull Request, we sho ... pected, consider asking the author why before requesting several changes. Seek to understand their reasoning first. Submit feedback on GitHub and update flags, "patch needs improvement", "needs tests", and "needs documentation", as needed. This will move ...
https://man.mtool.work/django/6.1/internals/contributing/triaging-tickets.html
Submitting contributions — Django 6.1 ドキュメント 9347
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Submitting contributions ¶ We're always grateful for contributions to Django's code. Indeed, bug reports with associated contributions will get fixe ... ot comply with these rules, clearly call it out in the contribution and explain why. Contributions which require community feedback ¶ A wider community discussion is required when a patch introduces new Django functionality and makes some sort of design ... if the approach involves a deprecation or introduces breaking changes. The following are different approaches for gaining feedback from the community. The new feature ideas tracker ¶ If you have an idea for a new feature, please create a new proposal (o ... ollow our deprecation policy . Hence, it can take months or years for Django to iterate on an API design. If you need user feedback on a public interface, it is better to create a third-party package first. You can iterate on the public API much faster, ...
https://man.mtool.work/django/6.1/internals/contributing/writing-code/submitting...
バグレポートと機能のリクエスト — Django 6.1 ドキュメント 8507
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » バグレポートと機能のリクエスト ¶ 重要 Please report security issues only to security@djangoproject.com . This is a private list only open to long-ti ... aim for rough consensus. Emoji reactions are used on issues within the new feature ideas GitHub project to track community feedback. The following meanings are assigned to each reaction: ?: I support this feature and would use it ?: I oppose this feature ... pport through the following stages: アイデア Approved - Idea refinement - Team creation 進行中 Working solution - Review - Feedback Needs maintainer (Django only) 完了 Occasionally, discussions on feature ideas or the direction of Django may take place o ... the specific commit that caused it. See リグレッションの bisect for instructions. You can also discuss any issues or share feedback in the Pre-releases category on the Django Forum . 目次 バグレポートと機能のリクエスト バグレポート Reporting user interfa ...
https://man.mtool.work/django/6.1/internals/contributing/bugs-and-features.html
バグレポートと機能のリクエスト — Django 6.1 ドキュメント 8507
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » バグレポートと機能のリクエスト ¶ 重要 Please report security issues only to security@djangoproject.com . This is a private list only open to long-ti ... aim for rough consensus. Emoji reactions are used on issues within the new feature ideas GitHub project to track community feedback. The following meanings are assigned to each reaction: ?: I support this feature and would use it ?: I oppose this feature ... pport through the following stages: アイデア Approved - Idea refinement - Team creation 進行中 Working solution - Review - Feedback Needs maintainer (Django only) 完了 Occasionally, discussions on feature ideas or the direction of Django may take place o ... the specific commit that caused it. See リグレッションの bisect for instructions. You can also discuss any issues or share feedback in the Pre-releases category on the Django Forum . 目次 バグレポートと機能のリクエスト バグレポート Reporting user interfa ...
https://man.mtool.work/django/6.1/internals/contributing/bugs-and-features.html
Django 0.95 リリースノート — Django 6.1 ドキュメント 7387
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Django 0.95 リリースノート ¶ Django 0.95 へようこそ! このリリースでは、2006年1月にリリースされた 0.91 から Django の開発が大幅に進んでいます。このリ ... me regularity, and any particular problem may already have been answered. Finally, for those who prefer the more immediate feedback offered by IRC, there's a #django channel on irc.libera.chat that is regularly populated by Django users and developers fr ...
https://man.mtool.work/django/6.1/releases/0.95.html
Django 0.95 リリースノート — Django 6.1 ドキュメント 7387
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Django 0.95 リリースノート ¶ Django 0.95 へようこそ! このリリースでは、2006年1月にリリースされた 0.91 から Django の開発が大幅に進んでいます。このリ ... me regularity, and any particular problem may already have been answered. Finally, for those who prefer the more immediate feedback offered by IRC, there's a #django channel on irc.libera.chat that is regularly populated by Django users and developers fr ...
https://man.mtool.work/django/6.1/releases/0.95.html
PREV 1 2 NEXT