{"title":"Clasificando tickets","version":"4.0","locale":"es","docname":"internals/contributing/triaging-tickets","url":"/es/4.0/internals/contributing/triaging-tickets/","canonical":"https://djangodocs.dev/es/4.0/internals/contributing/triaging-tickets/","summary":"Django utiliza Trac para gestionar el trabajo realizado sobre la base de código. Trac es como un jardín cuidado por la comunidad contentivo de bugs que las personas…","html":"

Clasificando ticketsLink to this heading#

\n

Django utiliza Trac para gestionar el trabajo realizado sobre la base de código. Trac es como un jardín cuidado por la comunidad contentivo de bugs que las personas han encontrado y las funcionalidades que desearían ver añadidas. Como en cualquier jardín, a veces hay maleza que arrancar y a veces hay flores y verduras que necesitan ser recogidas. Necesitamos su ayuda para separar unas de las otras y al final todos nos beneficiamos.

\n

Como en todos los jardines, podemos aspirar a la perfección aunque en realidad no exista tal cosa. Incluso en el jardín más limpio todavía hay caracoles e insectos. En un jardín comunitario también hay personas útiles que, con las mejores intenciones, abonan la maleza y envenenan las rosas. Es tarea de la comunidad en su conjunto autogestionar, mantener los problemas al mínimo y educar a aquellos que entran a la comunidad, de modo que puedan convertirse en valiosos colaboradores.

\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

Confiamos en que la comunidad siga participando, mantenga los tickets lo más exactos posibles, y presente temas de discusión en nuestras listas de correo cuando haya confusión o desacuerdo.

\n

Django es un proyecto comunitario y cualquier contribución es de ayuda. ¡No podemos hacer esto sin usted!

\n
\n

Flujo de trabajo de clasificaciónLink to this heading#

\n

Desafortunadamente, no todos los informes de errores y solicitudes de funcionalidades en el rastreador de tickets proporcionan todos los :doc: detalles necesarios <bugs-and-features>. Varios tickets podrían tener parches, pero dichos parches podrían no cumplircon todos los requisitos de un :ref: buen parche <patch-style>`.

\n

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

\n

La mayor parte del flujo de trabajo se basa en el concepto de :ref: las etapas de clasificación de un ticket <triage-stages>. Cada etapa describe en que período de su ciclo de vida se encuentra un determinado ticket. Junto con un puñado de marcadores, este atributo fácilmente nos indica qué y por quién espera cada ticket.

\n

Ya que una imagen vale más que mil palabras, vamos a empezar por ahí:

\n\"Django's\n\n

Tenemos dos roles en este esquema:

\n\n

A modo de ejemplo, aquí vemos el ciclo de vida de un ticket promedio:

\n\n

Algunos tickets necesitan mucha menos retroalimentación que este, pero, por otro lado, algunos tickets necesitan muchísima más.

\n
\n
\n

Etapas de clasificaciónLink to this heading#

\n

A continuación, describimos con más detalles las diferentes etapas por las que tiene que pasar un ticket durante su ciclo de vida.

\n
\n

No revisadoLink to this heading#

\n

El ticket no ha sido revisado por alguien que se sintiera calificado para evaluar si el mismo contiene un tema válido, una funcionalidad viable o si se debe cerrar por cualquiera de los diversos motivos.

\n
\n
\n

AceptadoLink to this heading#

\n

¡La gran zona gris! El significado absoluto de «aceptado» es que el problema descrito en el ticket es válido y está en alguna etapa en la que se puede trabajar. Además de eso existen varias consideraciones:

\n\n
\n
\n

Listo Para RevisarLink to this heading#

\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 patch. A merger now needs to give the patch\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

Algún día/Tal vezLink to this heading#

\n

This stage isn’t shown on the diagram. It’s used sparingly to keep track of\nhigh-level ideas or long term feature requests.

\n

These tickets are uncommon and overall less useful since they don’t describe\nconcrete actionable issues. They are enhancement requests that we might\nconsider adding someday to the framework if an excellent patch is submitted.\nThey are not a high priority.

\n
\n
\n
\n

Otros atributos de clasificaciónLink to this heading#

\n

A number of flags, appearing as checkboxes in Trac, can be set on a ticket:

\n
\n

Tiene parcheLink to this heading#

\n

This means the ticket has an associated\npatch. These will be reviewed\nto see if the patch is «good».

\n

The following three fields (Needs documentation, Needs tests,\nPatch needs improvement) apply only if a patch has been supplied.

\n
\n
\n

Necesita documentaciónLink to this heading#

\n

This flag is used for tickets with patches that need associated\ndocumentation. Complete documentation of features is a prerequisite\nbefore we can check them into the codebase.

\n
\n
\n

Necesita pruebasLink to this heading#

\n

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

\n
\n
\n

El parche necesita mejorasLink to this heading#

\n

This flag means that although the ticket has a patch, 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

Presa fácilLink to this heading#

\n

Tickets que requerirían parches pequeños y fáciles.

\n
\n
\n

TipoLink to this heading#

\n

Los tickets deberían ser clasificados por tipos entre:

\n\n
\n
\n

ComponenteLink to this heading#

\n

Los tickets se deben clasificar en componentes que indican a que área de la base del código Django pertenecen. Esto hace que los tickets estén mejor organizados y sean más fáciles de encontrar.

\n
\n
\n

GravedadLink to this heading#

\n

The severity attribute is used to identify blockers, that is, issues which\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

VersiónLink to this heading#

\n

Es posible utilizar el atributo versión para indicar en qué versión se identificó el error reportado.

\n
\n
\n

UI/UXLink to this heading#

\n

This flag is used for tickets that relate to User Interface and User\nExperiences questions. For example, this flag would be appropriate for\nuser-facing features in forms or the admin interface.

\n
\n
\n

CcLink to this heading#

\n

You may add your username or email address to this field to be notified when\nnew contributions are made to the ticket.

\n
\n
\n

Palabras claveLink to this heading#

\n

With this field you may label a ticket with multiple keywords. This can be\nuseful, for example, to group several tickets of a 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

Cerrando ticketsLink to this heading#

\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

Si cierra un ticket, usted siempre debería asegurarse de lo siguiente:

\n\n

Un ticket se puede solucionar de varias maneras:

\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» and\nbring the issue to django-developers instead.

\n
\n
\n

How can I help with triaging?Link to this heading#

\n

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

\n

To get involved, start by creating an account on Trac. If you have an\naccount but have forgotten your password, you can reset it using the password\nreset page.

\n

Then, you can help out by:

\n\n\n

However, we do ask the following of all general community members working in\nthe ticket database:

\n\n
\n
\n

Bisecting a regressionLink to this heading#

\n

A regression is a bug that’s present in some newer version of Django but not in\nan older one. An extremely helpful piece of information is the commit that\nintroduced the regression. Knowing the commit that caused the change in\nbehavior helps identify if the change was intentional or if it was an\ninadvertent side-effect. Here’s how you can determine this.

\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 checkout an earlier revision (100 commits earlier,\nin this case). Check if the test fails. If so, mark that point as «bad»\n(git bisect bad), then checkout an earlier revision and recheck. Once you\nfind 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

You should see git bisect use a binary search to automatically checkout\nrevisions between the good and bad commits until it finds the first «bad»\ncommit where the test fails.

\n

Now, report your results on the Trac ticket, and please include the regression\ntest as an attachment. When someone writes a fix for the bug, they’ll already\nhave your test as a starting point.

\n
","rootId":"triaging-tickets","toc":[{"title":"Flujo de trabajo de clasificación","anchor":"triage-workflow","children":[]},{"title":"Etapas de clasificación","anchor":"triage-stages","children":[{"title":"No revisado","anchor":"unreviewed","children":[]},{"title":"Aceptado","anchor":"accepted","children":[]},{"title":"Listo Para Revisar","anchor":"ready-for-checkin","children":[]},{"title":"Algún día/Tal vez","anchor":"someday-maybe","children":[]}]},{"title":"Otros atributos de clasificación","anchor":"other-triage-attributes","children":[{"title":"Tiene parche","anchor":"has-patch","children":[]},{"title":"Necesita documentación","anchor":"needs-documentation","children":[]},{"title":"Necesita pruebas","anchor":"needs-tests","children":[]},{"title":"El parche necesita mejoras","anchor":"patch-needs-improvement","children":[]},{"title":"Presa fácil","anchor":"easy-pickings","children":[]},{"title":"Tipo","anchor":"type","children":[]},{"title":"Componente","anchor":"component","children":[]},{"title":"Gravedad","anchor":"severity","children":[]},{"title":"Versión","anchor":"version","children":[]},{"title":"UI/UX","anchor":"ui-ux","children":[]},{"title":"Cc","anchor":"cc","children":[]},{"title":"Palabras clave","anchor":"keywords","children":[]}]},{"title":"Cerrando tickets","anchor":"closing-tickets","children":[]},{"title":"How can I help with triaging?","anchor":"how-can-i-help-with-triaging","children":[]},{"title":"Bisecting a regression","anchor":"bisecting-a-regression","children":[]}],"breadcrumbs":[{"docname":"internals/index","title":"Django internals","url":"/es/4.0/internals/"},{"docname":"internals/contributing/index","title":"Contribuyendo con Django","url":"/es/4.0/internals/contributing/"}],"prev":{"docname":"internals/contributing/bugs-and-features","title":"Cómo informar de errores y solicitar funcionalidades","url":"/es/4.0/internals/contributing/bugs-and-features/"},"next":{"docname":"internals/contributing/writing-code/index","title":"Writing code","url":"/es/4.0/internals/contributing/writing-code/"},"formats":{"html":"/es/4.0/internals/contributing/triaging-tickets/","markdown":"/es/4.0/internals/contributing/triaging-tickets.md","json":"/es/4.0/internals/contributing/triaging-tickets.json"},"source":"https://github.com/django/django/blob/stable/4.0.x/docs/internals/contributing/triaging-tickets.txt","official":"https://docs.djangoproject.com/es/4.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","zh-hans","fr","ja","id","it","pt-br","ko","es","el","pl"]}