per page, with , order by , clip by
Results of 1 - 10 of about 46 for ticket (0.003 sec.)
Sprint quickstart guide — Django 6.1 ドキュメント 11411
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Sprint quickstart guide ¶ This document explains how to prepare to contribute to Django. It is intended for use during sprints, or by people who are ... changes. Build the documentation: /  $ cd docs && make html && cd .. ...\> cd docs && make.bat html && cd .. Finding a ticket to work on ¶ Finding a workable ticket is a challenging task. It's important to read this section before attempting to do ... so. Assessing tickets ¶ When looking over tickets, it's a good idea to keep your search to accepted tickets created in the last five years . Ol ... der tickets are old for a reason: they are usually still open because they are hard, contentious, or both. You're welcome to try one, ...
https://man.mtool.work/django/6.1/internals/contributing/sprint-quickstart.html
Sprint quickstart guide — Django 6.1 ドキュメント 11411
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Sprint quickstart guide ¶ This document explains how to prepare to contribute to Django. It is intended for use during sprints, or by people who are ... changes. Build the documentation: /  $ cd docs && make html && cd .. ...\> cd docs && make.bat html && cd .. Finding a ticket to work on ¶ Finding a workable ticket is a challenging task. It's important to read this section before attempting to do ... so. Assessing tickets ¶ When looking over tickets, it's a good idea to keep your search to accepted tickets created in the last five years . Ol ... der tickets are old for a reason: they are usually still open because they are hard, contentious, or both. You're welcome to try one, ...
https://man.mtool.work/django/6.1/internals/contributing/sprint-quickstart.html
チケットをトリアージする — Django 6.1 ドキュメント 11274
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 ... ほぼ正確」です。間違ってなんぼ、我々は期限を守ってからの完璧主義です。 We rely on the community to keep participating, keep tickets as accurate as possible, and raise issues for discussion on the Django Forum when there is confusion or disagreement. Dja ... 役立ちます。 あなた なしではこれを実現することはできません! トリアージのワークフロー ¶ Unfortunately, not all reports in the ticket tracker provide all the required details . A number of tickets have proposed solutions, but those don't necessarily meet a ... ll the requirements adhering to the guidelines for contributing . One way to help out is to triage tickets that have been created by other users. Most of the workflow is based around the concept of a ticket's triage stages . Eac ...
https://man.mtool.work/django/6.1/internals/contributing/triaging-tickets.html
チケットをトリアージする — Django 6.1 ドキュメント 11274
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 ... ほぼ正確」です。間違ってなんぼ、我々は期限を守ってからの完璧主義です。 We rely on the community to keep participating, keep tickets as accurate as possible, and raise issues for discussion on the Django Forum when there is confusion or disagreement. Dja ... 役立ちます。 あなた なしではこれを実現することはできません! トリアージのワークフロー ¶ Unfortunately, not all reports in the ticket tracker provide all the required details . A number of tickets have proposed solutions, but those don't necessarily meet a ... ll the requirements adhering to the guidelines for contributing . One way to help out is to triage tickets that have been created by other users. Most of the workflow is based around the concept of a ticket's triage stages . Eac ...
https://man.mtool.work/django/6.1/internals/contributing/triaging-tickets.html
Submitting contributions — Django 6.1 ドキュメント 10953
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 ... changing a word in the documentation, the preferred way to provide the patch is using GitHub pull requests without a Trac ticket. See Working with Git and GitHub for more details on how to use pull requests. "Claiming" tickets ¶ In an open-source proj ... doesn't get duplicated and contributors can be as effective as possible. Hence, our policy is for contributors to "claim" tickets in order to let other developers know that a particular bug or feature is being worked on. If you have identified a contr ... ls and time availability), claim it by following these steps: Log in using your GitHub account or create an account in our ticket system. If you have an account but have forgotten your password, you can reset it using the password reset page . If a tic ...
https://man.mtool.work/django/6.1/internals/contributing/writing-code/submitting...
Submitting contributions — Django 6.1 ドキュメント 10953
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 ... changing a word in the documentation, the preferred way to provide the patch is using GitHub pull requests without a Trac ticket. See Working with Git and GitHub for more details on how to use pull requests. "Claiming" tickets ¶ In an open-source proj ... doesn't get duplicated and contributors can be as effective as possible. Hence, our policy is for contributors to "claim" tickets in order to let other developers know that a particular bug or feature is being worked on. If you have identified a contr ... ls and time availability), claim it by following these steps: Log in using your GitHub account or create an account in our ticket system. If you have an account but have forgotten your password, you can reset it using the password reset page . If a tic ...
https://man.mtool.work/django/6.1/internals/contributing/writing-code/submitting...
Working with Git and GitHub — Django 6.1 ドキュメント 9565
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Working with Git and GitHub ¶ This section explains how the community can contribute code to Django via pull requests. If you're interested in how m ... プルリクエストの取り扱い . Below, we are going to show how to create a GitHub pull request containing the changes for Trac ticket #xxxxx. By creating a fully-ready pull request, you will make the reviewer's job easier, meaning that your work is more li ... can add other remotes similarly, for example: git remote add akaariai https://github.com/akaariai/django.git Working on a ticket ¶ When working on a ticket, create a new branch for the work, and base that work on upstream/main : git checkout -b ticket ... s - that's what they are there for. If instead you were working for a fix on the 1.4 branch, you would do: git checkout -b ticket_xxxxx_1_4 upstream/stable/1.4.x Assume the work is carried on the ticket_xxxxx branch. Make some changes and commit them: ...
https://man.mtool.work/django/6.1/internals/contributing/writing-code/working-wi...
Working with Git and GitHub — Django 6.1 ドキュメント 9565
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Working with Git and GitHub ¶ This section explains how the community can contribute code to Django via pull requests. If you're interested in how m ... プルリクエストの取り扱い . Below, we are going to show how to create a GitHub pull request containing the changes for Trac ticket #xxxxx. By creating a fully-ready pull request, you will make the reviewer's job easier, meaning that your work is more li ... can add other remotes similarly, for example: git remote add akaariai https://github.com/akaariai/django.git Working on a ticket ¶ When working on a ticket, create a new branch for the work, and base that work on upstream/main : git checkout -b ticket ... s - that's what they are there for. If instead you were working for a fix on the 1.4 branch, you would do: git checkout -b ticket_xxxxx_1_4 upstream/stable/1.4.x Assume the work is carried on the ticket_xxxxx branch. Make some changes and commit them: ...
https://man.mtool.work/django/6.1/internals/contributing/writing-code/working-wi...
バグレポートと機能のリクエスト — Django 6.1 ドキュメント 8207
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 ... hives are not public. For further details, please see our security policies . バグレポート ¶ Before reporting a bug on the ticket tracker consider these points: Check that someone hasn't already filed the bug report by searching or running custom queri ... es in the ticket tracker. Don't use the ticket system to ask support questions. Use the Django Forum or the Django Discord server for that. ... n marked "needsnewfeatureprocess" without shepherding an issue through the new feature ideas GitHub project. Don't use the ticket tracker for lengthy discussions, because they're likely to get lost. If a particular ticket is controversial, please move ...
https://man.mtool.work/django/6.1/internals/contributing/bugs-and-features.html
バグレポートと機能のリクエスト — Django 6.1 ドキュメント 8177
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 ... hives are not public. For further details, please see our security policies . バグレポート ¶ Before reporting a bug on the ticket tracker consider these points: Check that someone hasn't already filed the bug report by searching or running custom queri ... es in the ticket tracker. Don't use the ticket system to ask support questions. Use the Django Forum or the Django Discord server for that. ... n marked "needsnewfeatureprocess" without shepherding an issue through the new feature ideas GitHub project. Don't use the ticket tracker for lengthy discussions, because they're likely to get lost. If a particular ticket is controversial, please move ...
https://man.mtool.work/django/6.1/internals/contributing/bugs-and-features.html
PREV 1 2 3 4 5 NEXT