{"title":"Triagem de tickets","version":"6.0","locale":"pt-br","docname":"internals/contributing/triaging-tickets","url":"/pt-br/6.0/internals/contributing/triaging-tickets/","canonical":"https://djangodocs.dev/pt-br/6.0/internals/contributing/triaging-tickets/","summary":"Django uses Trac for managing the work on the code base. Trac is a community-tended garden of the bugs people have found and the features Django has decided…","html":"

Triagem de ticketsLink para este cabeçalho#

\n

Django uses Trac for managing the work on the code base. Trac is a\ncommunity-tended garden of the bugs people have found and the features Django\nhas decided to add. As in any garden, sometimes there are weeds to be pulled\nand sometimes there are flowers and vegetables that need picking. We need your\nhelp to sort out one from the other, and in the end, we all benefit together.

\n

Like all gardens, we can aspire to perfection, but in reality there’s no such\nthing. Even in the most pristine garden there are still snails and insects.\nIn a community garden there are also helpful people who – with the best of\nintentions – fertilize the weeds and poison the roses. It’s the job of the\ncommunity as a whole to self-manage, keep the problems to a minimum, and\neducate those coming into the community so that they can become valuable\ncontributing members.

\n

Similarly, while we aim for Trac to be a perfect representation of the state of\nDjango’s progress, we acknowledge that this will not happen. By distributing\nthe load of Trac maintenance to the community, we accept that there will be\nmistakes. Trac is “mostly accurate”, and we give allowances for the fact that\nsometimes it will be wrong. That’s okay. We’re perfectionists with deadlines.

\n

We rely on the community to keep participating, keep tickets as accurate as\npossible, and raise issues for discussion on the Django Forum when there is\nconfusion or disagreement.

\n

Django é um projeto comunitário, e cada contribuição ajuda. Nós não podemos fazer isso sem vocês!

\n
\n

Fluxo de triagemLink para este cabeçalho#

\n

Unfortunately, not all reports in the ticket tracker provide all the\nrequired details. A number of tickets have proposed\nsolutions, but those don’t necessarily meet all the requirements adhering\nto the guidelines for contributing.

\n

One way to help out is to triage tickets that have been created by other\nusers.

\n

A maior parte do fluxo de trabalho é baseada em torno do conceito de tickets estágios de triagem. Cada estágio descreve em que parte de seu clico de vida um ticket está em um dado momento. Além de várias tags, esse atributo nos diz claramente o que e quem o ticket está aguardando.

\n

Já que uma imagem vale mais que mil palavras, vamos começar aqui:

\n\"Django's\n

We have four roles in this diagram. Maintainers (also known as Fellows) usually\ntake part in all of them, but anyone in the Django community can participate in\nany role except merger. The merger role is granted by a\nvote of the Steering Council.

\n\n

Our Trac system is intentionally open to the public, and anyone can help by\nworking on tickets. Django is a community project, and we encourage\ntriage and collaboration by the community. This could be you!

\n

For example, here’s the typical lifecycle of a ticket:

\n\n

Some tickets move through these steps quickly, while others take more time and\ndiscussion. Each contribution helps Django improve.

\n
\n
\n

Estágios de triagemLink para este cabeçalho#

\n

Abaixo são descritos em mais detalhes os vários estágios que um ticket pode possuir durante o seu tempo de vida.

\n
\n

Não revisadoLink para este cabeçalho#

\n

The ticket has not been reviewed by anyone who felt qualified to make a\njudgment about whether the ticket contained a valid issue or ought to be closed\nfor any reasons. Unreviewed tickets appear in the “triage” queue.

\n

Unreviewed tickets may receive additional refinement before being accepted.\nUnless you are both the author of the ticket and intending to submit a patch,\nunreviewed tickets should not be claimed.

\n
\n
\n

AceitoLink para este cabeçalho#

\n

The absolute meaning of “accepted” is that the issue described in the ticket is\nvalid and actionable. It is broken out into three queues:

\n\n
\n
\n

Pronto para CheckinLink para este cabeçalho#

\n

The ticket was reviewed by any member of the community other than the person\nwho supplied the patch and found to meet all the requirements for a\ncommit-ready contribution. A merger now needs to give\na final review prior to being committed.

\n

There are a lot of pull requests. It can take a while for your patch to get\nreviewed. See the contributing code FAQ for some\nideas here.

\n
\n
\n

Algum Dia/TalvezLink para este cabeçalho#

\n

This stage isn’t shown on the diagram. It’s used sparingly to keep track of\nlong-term changes.

\n

These tickets are uncommon and overall less useful since they don’t describe\nconcrete actionable issues.

\n
\n
\n
\n

Outros atributos de triagemLink para este cabeçalho#

\n

Um número de tags, aparecendo como checkboxes no Trac, podem ser ativdadas no ticket:

\n
\n

Possui patchLink para este cabeçalho#

\n

This means the ticket has an associated solution. These will be reviewed to\nensure they adhere to the documented guidelines.

\n

Os três campos seguintes (Precisa de documentação, Precisa de testes, Patch precisa de melhorias) se aplicam apenas se o patch foi submetido.

\n
\n
\n

Precisa de documentaçãoLink para este cabeçalho#

\n

Essa tag é usada para tickets com patches sem documentação associada. Documentação completa de funcionalidades é um pré-requisito antes de nós adicionarmos elas no código base.

\n
\n
\n

Precisa de testesLink para este cabeçalho#

\n

This flags the patch as needing associated unit tests. Again, this\nis a required part of a valid contribution.

\n
\n
\n

Patch precisa de melhoriasLink para este cabeçalho#

\n

This flag means that although the ticket has a solution, it’s not quite\nready for checkin. This could mean the patch no longer applies\ncleanly, there is a flaw in the implementation, or that the code\ndoesn’t meet our standards.

\n
\n
\n

Escolhas FáceisLink para este cabeçalho#

\n

Tickets that would require small, easy, changes.

\n
\n
\n

TipoLink para este cabeçalho#

\n

Os tickets devem ser categorizados por tipo entre:

\n\n
\n
\n

ComponenteLink para este cabeçalho#

\n

Tickets devem ser classificados dentro de componentes indicando qual área do código base do Django eles pertencem. Isso faz com que os tickets fiquem melhor organizados e mais fáceis de encontrar.

\n
\n
\n

SeveridadeLink para este cabeçalho#

\n

The severity attribute is used to identify blockers, that is, issues that\nshould get fixed before releasing the next version of Django. Typically those\nissues are bugs causing regressions from earlier versions or potentially\ncausing severe data losses. This attribute is quite rarely used and the vast\nmajority of tickets have a severity of “Normal”.

\n
\n
\n

VersãoLink para este cabeçalho#

\n

The version attribute indicates the earliest version in which the bug was\nreproduced. During triage, this field can be updated, but there is no need to\nmake further updates when that version goes out of support. The field should\nnot be reset to “dev” to show the issue still exists: instead, the tested\ncommit hash can be noted in a comment.

\n
\n
\n

UI/UXLink para este cabeçalho#

\n

Esta tag é utilizada para tickets que estão relacionados a questões de interface de usuário e de experiência de usuário. Por exemplo, essa tag seria apropriada para funcionalidades que os usuários podem ver nos formulários ou na interface do admin.

\n
\n
\n

CcLink para este cabeçalho#

\n

Você pode adicionar o seu nome de usuário ou endereço de email neste campo para ser notificado quando novas contribuições forem feitas ao ticket.

\n
\n
\n

Palavras-chaveLink para este cabeçalho#

\n

With this field you may label a ticket with multiple keywords. This can be\nuseful, for example, to group several tickets on the same theme. Keywords can\neither be comma or space separated. Keyword search finds the keyword string\nanywhere in the keywords. For example, clicking on a ticket with the keyword\n“form” will yield similar tickets tagged with keywords containing strings such\nas “formset”, “modelformset”, and “ManagementForm”.

\n
\n
\n
\n

Fechando TicketsLink para este cabeçalho#

\n

When a ticket has completed its useful lifecycle, it’s time for it to be\nclosed. Closing a ticket is a big responsibility, though. You have to be sure\nthat the issue is really resolved, and you need to keep in mind that the\nreporter of the ticket may not be happy to have their ticket closed (unless\nit’s fixed!). If you’re not certain about closing a ticket, leave a comment\nwith your thoughts instead.

\n

Se você realmente for fechar um ticket, você sempre deve ter certeza de que:

\n\n

Um ticket pode ser resolvido de diversas maneiras:

\n\n

If you believe that the ticket was closed in error – because you’re\nstill having the issue, or it’s popped up somewhere else, or the triagers have\nmade a mistake – please reopen the ticket and provide further information.\nAgain, please do not reopen tickets that have been marked as “wontfix” or\n“needsnewfeatureprocess”. For “wontfix” tickets, bring the issue to the\nDjango Forum instead. For “needsnewfeatureprocess” tickets, propose the\nfeature through the new features process.

\n
\n
\n

How can I help with development?Link para este cabeçalho#

\n

The development process is primarily driven by community members. Really,\nANYONE can help.

\n

Para contribuir, comece criando uma conta no Trac. Se você tem uma conta mas esqueceu a sua senha, você pode resetá-la usando a página de recuperação de senha.

\n

A partir disso, você poderá ajudar com:

\n\n\n

Porém, nós pedimos o seguinte de todos os membros da comunidade trabalhando no banco de dados de tickets:

\n\n
\n
\n

Bisseccionando uma regressãoLink para este cabeçalho#

\n

Uma regressão é um bug que está presente em alguma versão nova do Django mas não em versões mais antigas. Uma informação extremamente valiosa é o commit que introduziu a regressão. Saber qual foi o commit que causou a mudança de comportamento ajuda a identificar se a mudança foi intencional ou se ela foi um efeito colateral inesperado. Aqui vamos mostrar como você pode determinar isso.

\n

Begin by writing a regression test for Django’s test suite for the issue. For\nexample, we’ll pretend we’re debugging a regression in migrations. After you’ve\nwritten the test and confirmed that it fails on the latest main branch, put it\nin a separate file that you can run standalone. For our example, we’ll pretend\nwe created tests/migrations/test_regression.py, which can be run with:

\n
Shell
$ ./runtests.py migrations.test_regression\n
\n

Next, we mark the current point in history as being “bad” since the test fails:

\n
Shell
$ git bisect bad\nYou need to start by "git bisect start"\nDo you want me to do it for you [Y/n]? y\n
\n

Now, we need to find a point in git history before the regression was\nintroduced (i.e. a point where the test passes). Use something like\ngit checkout HEAD~100 to check out an earlier revision (100 commits\nearlier, in this case). Check if the test fails. If so, mark that point as\n“bad” (git bisect bad), then check out an earlier revision and recheck.\nOnce you find a revision where your test passes, mark it as “good”:

\n
Shell
$ git bisect good\nBisecting: X revisions left to test after this (roughly Y steps)\n...\n
\n

Now we’re ready for the fun part: using git bisect run to automate the rest\nof the process:

\n
Shell
$ git bisect run tests/runtests.py migrations.test_regression\n
\n

Você deverá ver o git bisect usando uma busca binária para automaticamente fazer checkout de revisões entre os commits bons e os commits ruins até que ele encontre o primeiro commit “ruim” onde o teste falha.

\n

Agora, mostre os seus resultados no ticket do Trac, e por favor inclua o teste de regressão como um anexo. Quando alguém escreve uma correção para o bug, eles já terão o seu teste como uma referência de por onde começar.

\n
","rootId":"triaging-tickets","toc":[{"title":"Fluxo de triagem","anchor":"triage-workflow","children":[]},{"title":"Estágios de triagem","anchor":"triage-stages","children":[{"title":"Não revisado","anchor":"unreviewed","children":[]},{"title":"Aceito","anchor":"accepted","children":[]},{"title":"Pronto para Checkin","anchor":"ready-for-checkin","children":[]},{"title":"Algum Dia/Talvez","anchor":"someday-maybe","children":[]}]},{"title":"Outros atributos de triagem","anchor":"other-triage-attributes","children":[{"title":"Possui patch","anchor":"has-patch","children":[]},{"title":"Precisa de documentação","anchor":"needs-documentation","children":[]},{"title":"Precisa de testes","anchor":"needs-tests","children":[]},{"title":"Patch precisa de melhorias","anchor":"patch-needs-improvement","children":[]},{"title":"Escolhas Fáceis","anchor":"easy-pickings","children":[]},{"title":"Tipo","anchor":"type","children":[]},{"title":"Componente","anchor":"component","children":[]},{"title":"Severidade","anchor":"severity","children":[]},{"title":"Versão","anchor":"version","children":[]},{"title":"UI/UX","anchor":"ui-ux","children":[]},{"title":"Cc","anchor":"cc","children":[]},{"title":"Palavras-chave","anchor":"keywords","children":[]}]},{"title":"Fechando Tickets","anchor":"closing-tickets","children":[]},{"title":"How can I help with development?","anchor":"how-can-i-help-with-development","children":[]},{"title":"Bisseccionando uma regressão","anchor":"bisecting-a-regression","children":[]}],"breadcrumbs":[{"docname":"internals/index","title":"Funcionamento interno do Projeto Django","url":"/pt-br/6.0/internals/"},{"docname":"internals/contributing/index","title":"Contribuindo com o Django","url":"/pt-br/6.0/internals/contributing/"}],"prev":{"docname":"internals/contributing/bugs-and-features","title":"Relatando bugs e solicitando funcionalidades","url":"/pt-br/6.0/internals/contributing/bugs-and-features/"},"next":{"docname":"internals/mailing-lists","title":"Mailing lists and Forum","url":"/pt-br/6.0/internals/mailing-lists/"},"formats":{"html":"/pt-br/6.0/internals/contributing/triaging-tickets/","markdown":"/pt-br/6.0/internals/contributing/triaging-tickets.md","json":"/pt-br/6.0/internals/contributing/triaging-tickets.json"},"source":"https://github.com/django/django/blob/stable/6.0.x/docs/internals/contributing/triaging-tickets.txt","official":"https://docs.djangoproject.com/pt-br/6.0/internals/contributing/triaging-tickets/","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"]}