{"title":"Ticéid triail","version":"6.1","locale":"ga","docname":"internals/contributing/triaging-tickets","url":"/ga/6.1/internals/contributing/triaging-tickets/","canonical":"https://djangodocs.dev/ga/6.1/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 to add.…","html":"

Ticéid triailLink to this heading#

\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

Cosúil le gach gairdín, is féidir linn a bheith ag súil le foirfeacht, ach i ndáiríre níl aon rud den sórt sin ann. Fiú sa ghairdín is pristine tá seilidí agus feithidí fós ann. I ngairdín pobail tá daoine cabhracha ann freisin - leis an rún is fearr - a thorthú na fiailí agus a nimhionn na rósanna. Is obair an phobail ina iomláine é féin-bhainistiú, na fadhbanna a choinneáil ar a laghad, agus oideachas a chur ar fáil dóibh siúd a thagann isteach sa phobal ionas gur féidir leo a bheith ina mbaill luachmhara rannpháirteach.

\n

Ar an gcaoi chéanna, cé go bhfuil sé mar aidhm againn go mbeidh Trac ina léiriú foirfe ar staid dul chun cinn Django, admhaímid nach dtarlóidh sé seo. Trí ualach cothabhála Trac a dháileadh ar an bpobal, glacaimid leis go mbeidh botúin ann. Tá Trac “cruinn den chuid is mó”, agus tugaimid liúntais as go mbeidh sé mícheart uaireanta. Tá sé sin ceart go leor. Is foirfeachtóirí muid le spriocdhátaí.

\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

Is tionscadal pobail é Django, agus cabhraíonn gach ranníocaíocht. Ní féidir linn é seo a dhéanamh gan**tús**!

\n
\n

Sreabhadh oibre triageLink to this heading#

\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

Bealach amháin le cabhrú amach is ea ticéid a chruthaigh úsáideoirí eile trialó.

\n

<triage-stages>Tá an chuid is mó den sreabhadh oibre bunaithe ar choincheap an ticéad: ref: `céimeanna triage `. Déanann gach céim cur síos ar an áit a bhfuil ticéad ar leith ag am ar bith i rith a shaoil. In éineacht le dornán bratacha, insíonn an tréith seo dúinn go héasca cad agus cé a bhfuil gach ticéad ag fanacht air.

\n

Ós rud é gur fiú míle focal pictiúr, tosaímid ansin:

\n\"Sreabhadh\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\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

Céimeanna triageLink to this heading#

\n

Anseo thíos déanaimid cur síos níos mionsonraithe ar na céimeanna éagsúla a bhféadfadh ticéad dul tríd le linn a shaolré.

\n
\n

Gan athbhreithniúLink to this heading#

\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

GlacthaLink to this heading#

\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

Réidh le haghaidh SeiceálaLink to this heading#

\n

Rinne aon bhall den phobal athbhreithniú ar an ticéad seachas an duine a sholáthair an paiste agus fuair sé amach go gcomhlíonann sé na ceanglais go léir maidir le ranníocaíocht réidh le coiste. A: Tagairt: Caithfidh `cumais <mergers-team>c `athbhreithniú deiridh a thabhairt anois sula ndéantar é.

\n

Tá a lán iarratais tarraingthe ann. Féadfaidh sé tamall a thógáil go ndéanfar athbhreithniú ar do phaiste. Féach an:ref: `Cóid rannchuidiúcháin Coitianta <new-contributors-faq>`le haghaidh roinnt smaointe anseo.

\n
\n
\n

Lá éigin/B'fhéidirLink to this heading#

\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

Tréithe triage eileLink to this heading#

\n

Is féidir roinnt bratacha, atá le feiceáil mar bhosca seiceála i Trac, a shocrú ar thicéad:

\n
\n

Tá paiste aiste aigeLink to this heading#

\n

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

\n

Ní bheidh feidhm ag na trí réimse seo a leanas (Doiciméadú Riachtanas, Tástálacha Riachtanas, Feabhsú ar Phaistí) ach amháin má tá paiste curtha ar fáil.

\n
\n
\n

Ní mór doiciméadúLink to this heading#

\n

Úsáidtear an bratach seo le haghaidh ticéid le paistí a dteastaíonn cáipéisíocht ghab Is réamhriachtanas é doiciméadú iomlán na ngnéithe sula bhféadfaimis iad a sheiceáil isteach sa chód bhunachar.

\n
\n
\n

Tástálacha is gáLink to this heading#

\n

Cuireann sé seo an paiste de dhíth go bhfuil tástálacha aonaid gaolmhara de dh Arís, is cuid riachtanach é seo de ranníocaíocht bhailí.

\n
\n
\n

Ní mór feabhsú ar phaisteLink to this heading#

\n

Ciallaíonn an bratach seo cé go bhfuil réiteach ag an ticéad*, nach bhfuil sé réidh go leor le haghaidh seiceála. D'fhéadfadh sé seo a chiallú nach mbaineann an paiste go glan a thuilleadh, tá locht sa chur i bhfeidhm, nó nach gcomhlíonann an cód ár gcaighdeáin.

\n
\n
\n

Piocadh éascaLink to this heading#

\n

Ticéid a mbeadh athruithe beaga éasca ag teastáil uathu.

\n
\n
\n

CineálLink to this heading#

\n

Ba chóir ticéid a chatagóiriú de réir cineál idir:

\n\n
\n
\n

ComhpháirtLink to this heading#

\n

Ba chóir ticéid a aicmiú ina*comhpháirteanna* a léiríonn cén limistéar den chód bonn Django leis a mbaineann siad. Déanann sé seo ticéid eagraithe níos fearr agus níos éasca a aimsiú.

\n
\n
\n

DéineLink to this heading#

\n

Úsáidtear an tréith* solúbth* chun blocálaithe a aithint, is é sin, saincheisteanna ba chóir a shocrú sula scaoiltear an chéad leagan eile de Django. De ghnáth is fabhtanna iad na saincheisteanna sin a chuireann aischéimnithe ó leaganacha níos luaithe nó a d'fhéadfadh a bheith ina Is annamh a úsáidtear an tréith seo agus tá déine “Gnáth” ag formhór mór na dticéad.

\n
\n
\n

LeaganLink to this heading#

\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 to this heading#

\n

Úsáidtear an bhratach seo le haghaidh ticéid a bhaineann le ceisteanna Comhéadain Úsáideora agus Eispéiris Úsáideora. Mar shampla, bheadh ​​an bhratach seo oiriúnach do ghnéithe atá os comhair úsáideoirí i bhfoirmeacha nó sa chomhéadan riaracháin.

\n
\n
\n

CcLink to this heading#

\n

Is féidir leat d’ainm úsáideora nó do sheoladh ríomhphoist a chur leis an réimse seo le go gcuirfear ar an eolas tú nuair a dhéantar ranníocaíochtaí nua leis an ticéad.

\n
\n
\n

EochairfhocalLink to this heading#

\n

Leis an réimse seo is féidir leat ticéad a lipéadú le go leor eochairfhocail Is féidir leis seo a bheith úsáideach, mar shampla, chun roinnt ticéid a ghrúpáil ar an téama céanna. Is féidir le heochairfhocail a bheith scartha le camóg nó spás. Faigheann cuardach eochairfhocal an sreang eochairfhocal áit ar bith Mar shampla, cliceáil ar thicéad leis an eochairfhocal “foirm” beidh ticéid den chineál céanna clib le heochairfhocail ina bhfuil teaghráin mar “formset”, “modelformset”, agus “ManagementForm”.

\n
\n
\n
\n

Ticéid DúntaLink to this heading#

\n

Nuair a bheidh a shaolré úsáideach críochnaithe ag ticéad, tá sé in am é a dhúnadh. Is freagracht mhór é ticéad a dhúnadh, áfach. Caithfidh tú a bheith cinnte go bhfuil an cheist réiteach i ndáiríre, agus ní mór duit a choinneáil i gcuimhne nach mbeadh tuairisceoir an ticéad sásta a dticéad a bheith dúnta (mura bhfuil sé socraithe!). Mura bhfuil tú cinnte faoi ticéad a dhúnadh, fág trácht le do chuid smaointe ina ionad sin.

\n

Má dhúnann tú ticéad, ba cheart duit na rudaí seo a leanas a chinntiú i gcónaí:

\n\n

Is féidir ticéad a réiteach ar roinnt bealaí:

\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 to this heading#

\n

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

\n

Chun páirt a ghlacadh, tosú trí cuntas a chruthú ar Trac. Má tá cuntas agat ach má tá dearmad déanta agat ar do phasfhocal, is féidir leat é a athshocrú ag baint úsáide as an leathanach athshocraithe pasfhocal.

\n

Ansin, is féidir leat cabhrú amach trí:

\n\n\n

Mar sin féin, iarrann muid an méid seo a leanas ó gach ball ginearálta pobail atá ag obair sa bhunachar sonraí ticéad:

\n\n
\n
\n

Aischéimniú a dhíghiltLink to this heading#

\n

Is fabht é aischéimniú atá i láthair i roinnt leagan níos nuaí de Django ach ní i gceann níos sine. Píosa faisnéise thar a bheith cabhrach is ea an tiomantas a thug isteach an aischéimniú. Cuidíonn eolas a fháil ar an ngealltanas a bhí ina chúis leis an athrú ar iompar a aithint an raibh an t-athrú d'aon ghnó nó an raibh fo-iarsacht neamhthuigneach ann. Seo mar is féidir leat é seo a chinneadh.

\n

Tosaigh trí thástáil aischéimnithe a scríobh do shraith tástála Django don tsaincheist. Mar shampla, ligeanfaimid go bhfuilimid ag dífhabhtú aischéimnithe in imirce. Tar éis duit an tástáil a scríobh agus a dhearbhú go dteipeann air ar an bpríomhbhrainse is déanaí, cuir é i gcomhad ar leithligh ar féidir leat a reáchtáil go neamhspleách Mar shampla, ligeanfaimid go gcruthaíomar tests/migrations/test_regression.py, ar féidir é a reáchtáil le:

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

Ansin, déanaimid an pointe reatha sa stair a mharcáil mar “dona” ós rud é go dteipeann ar an tástáil:

\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

Anois, ní mór dúinn pointe a aimsiú i stair git sula dtugadh isteach an aischéimniú (ie pointe ina dtéann an tástáil). Úsáid rud éigin cosúil le git checkout HEAD~100 chun athbhreithniú níos luaithe a sheiceáil (100 gealltanais níos luaithe, sa chás seo). Seiceáil má theipeann ar an tástáil. Más ea, marcáil an pointe sin mar “olc” (``git bisect bad ``), ansin seiceáil athbhreithniú níos luaithe agus athsheiceáil. Nuair a aimsíonn tú athbhreithniú ina dtéann do thástáil, marcáil é mar “maith”:

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

Anois táimid réidh don chuid spraoi: git bisect run` a úsáid chun an chuid eile den phróiseas a uathoibriú:

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

Ba cheart go bhfeicfeá git bisect úsáid a bhaint as cuardach dénártha chun na hathbhreithnithe idir maith agus olc a sheiceáil amach go huathoibríoch go dtí go bhfaighidh sé an chéad ghealltanas "olc" nuair a theipeann ar an tástáil.

\n

Anois, tuairiscigh do thorthaí ar an ticéad Trac, agus cuir an tástáil aischéimnithe mar cheangaltán le do thoil. Nuair a scríobhann duine socrú don fhabht, beidh do thástáil acu cheana féin mar phointe tosaigh.

\n
\n
\n

Reviewing patchesLink to this heading#

\n

A great way to learn the Django codebase is to help review patches. It allows\nyou to focus on a fixed scope of Django with a particular perspective. Plus,\nDjango tends to receive more patches than it can review which causes the\nreview queue to build up. Contributors can help Django tremendously by\nreviewing patches.

\n

The review queue is defined by tickets in Trac that are in the "Accepted"\nstate with the flag "has patch" set and the flags "patch needs improvement",\n"needs tests" and "needs documentation" unset. There is also a set of\nPull Requests in GitHub with the "no ticket" label that can be reviewed.

\n
\n

Code review processLink to this heading#

\n

The general process to reviewing a patch for Django is as follows:

\n
    \n

  1. Pick a patch to review. This can be from the review queue or the\nPull Requests in GitHub with the "no ticket" label. If you're new, pick\na specific component to stick with. Django is a big codebase, so it's best\nto contribute consistently with a narrow focus and grow it slowly.

    2. \n

  2. Pull the branch. See the Iarrataí tarraingthe a, including the git\nalias to make checking out other pull requests easier.

    3. \n

  3. Check the tests. If the ticket is for a bug, there should be a regression\ntest. Confirm that the test fails if the change is reverted. Check that the\ntests are adequately covering the code and logic as well. See\nSeicliosta ranníocaíochta.

    4. \n

  4. Test in your own Django project. See Installing the development version\nfor how. Explore the user interface and user experience with the change.\nDoes it feel right? Can you break it? Another approach is to assume\neverything is wrong. Can you demonstrate to yourself that each piece is\ncorrect?

    5. \n

  5. Check the documentation. Is the documentation understandable? Does it\nprovide the information the reader needs at that moment? Does it read well?\nIs it consistent with the documentation before and after it? See\nTóg an doiciméadú go háiti.

    6. \n

  6. Are you happy with the patch? This is fairly subjective, but that's fine.\nYou should ask, does the approach make sense to you and is there another\nway to do it that's better? Also ask yourself, is the scope of the change\nappropriate? Are things named appropriately? Renaming things is slow and\nchallenging in Django, so we should try to get it right from the start.\nAre there backwards compatibility concerns? Lastly, are there any other\ngeneral concerns such as things that may worry you or that should be looked\ninto?

    7. \n

  7. Review your feedback. Before you submit your feedback, consider the\nfeedback you want to share. It takes courage to open a Pull Request, we\nshould be thoughtful and considerate of the leap the author has made. If\nthere are nitpicky or small suggestions, use GitHub's suggestion feature.\nIf the approach isn't what you expected, consider asking the author why\nbefore requesting several changes. Seek to understand their reasoning\nfirst.

    8. \n

  8. Submit feedback on GitHub and update flags, "patch needs improvement",\n"needs tests", and "needs documentation", as needed. This will move the\nticket to the "waiting for author" queue. If you have given a\nspecific type of code review, please indicate that on the Pull Request.

    9. \n
\n
\n
\n

Types of code reviewsLink to this heading#

\n

Not everyone will or should give the same type of code review. Having a diverse\nset of opinions and experiences helps Django be better. If you are providing a\nspecific review, please indicate that on the Pull Request in GitHub. Below\nare some of the types of code review you can perform:

\n\n
\n
","rootId":"triaging-tickets","toc":[{"title":"Sreabhadh oibre triage","anchor":"triage-workflow","children":[]},{"title":"Céimeanna triage","anchor":"triage-stages","children":[{"title":"Gan athbhreithniú","anchor":"unreviewed","children":[]},{"title":"Glactha","anchor":"accepted","children":[]},{"title":"Réidh le haghaidh Seiceála","anchor":"ready-for-checkin","children":[]},{"title":"Lá éigin/B'fhéidir","anchor":"someday-maybe","children":[]}]},{"title":"Tréithe triage eile","anchor":"other-triage-attributes","children":[{"title":"Tá paiste aiste aige","anchor":"has-patch","children":[]},{"title":"Ní mór doiciméadú","anchor":"needs-documentation","children":[]},{"title":"Tástálacha is gá","anchor":"needs-tests","children":[]},{"title":"Ní mór feabhsú ar phaiste","anchor":"patch-needs-improvement","children":[]},{"title":"Piocadh éasca","anchor":"easy-pickings","children":[]},{"title":"Cineál","anchor":"type","children":[]},{"title":"Comhpháirt","anchor":"component","children":[]},{"title":"Déine","anchor":"severity","children":[]},{"title":"Leagan","anchor":"version","children":[]},{"title":"UI/UX","anchor":"ui-ux","children":[]},{"title":"Cc","anchor":"cc","children":[]},{"title":"Eochairfhocal","anchor":"keywords","children":[]}]},{"title":"Ticéid Dúnta","anchor":"closing-tickets","children":[]},{"title":"How can I help with development?","anchor":"how-can-i-help-with-development","children":[]},{"title":"Aischéimniú a dhíghilt","anchor":"bisecting-a-regression","children":[]},{"title":"Reviewing patches","anchor":"reviewing-patches","children":[{"title":"Code review process","anchor":"code-review-process","children":[]},{"title":"Types of code reviews","anchor":"types-of-code-reviews","children":[]}]}],"breadcrumbs":[{"docname":"internals/index","title":"Inmheánacha Django","url":"/ga/6.1/internals/"},{"docname":"internals/contributing/index","title":"Ag cur le Django","url":"/ga/6.1/internals/contributing/"}],"prev":{"docname":"internals/contributing/bugs-and-features","title":"Tuairisciú fabhtanna agus gnéithe","url":"/ga/6.1/internals/contributing/bugs-and-features/"},"next":{"docname":"internals/mailing-lists","title":"Liostaí seoltaí agus Fóram","url":"/ga/6.1/internals/mailing-lists/"},"formats":{"html":"/ga/6.1/internals/contributing/triaging-tickets/","markdown":"/ga/6.1/internals/contributing/triaging-tickets.md","json":"/ga/6.1/internals/contributing/triaging-tickets.json"},"source":"https://github.com/django/django/blob/stable/6.1.x/docs/internals/contributing/triaging-tickets.txt","official":"https://docs.djangoproject.com/ga/6.1/internals/contributing/triaging-tickets/","inVersions":["6.1","6.0","5.2"],"inLocales":["en","sv","zh-hans","ga","fr","ja","id","it","pt-br","ko","es","el","pl"]}