Before reporting a bug on the ticket tracker consider these points:
\nCheck that someone hasn't already filed the bug report by searching or\nrunning custom queries in the ticket tracker.
Don't use the ticket system to ask support questions. Use the Django Forum\nor the Django Discord server for that.
Don't reopen issues that have been marked "wontfix" without finding consensus\nto do so on the Django Forum.
Don't reopen issues that have been marked "needsnewfeatureprocess" without\nshepherding an issue through the new feature ideas GitHub project.
Don't use the ticket tracker for lengthy discussions, because they're\nlikely to get lost. If a particular ticket is controversial, please move the\ndiscussion to the Django Forum.
Tá tuairiscí fabht dea-scríofa * thar a bheith cabhrach. Mar sin féin, tá méid áirithe lasbhairde bainteach le hobair le haon chóras rianaithe fabht ionas go bhfuil meas ag do chabhair lenár rianaitheoir ticéad a choinneáil chomh úsáideach agus is féidir. Go háirithe:
\nDéan léigh an:doc: FAQ chun a fháil amach an bhféadfadh do cheist a bheith ina cheist aithe</faq/index> anta.
Do ask on Django Forum or the Django Discord server first if\nyou're not sure if what you're seeing is a bug.
Déan tuarascálacha fabht iomlána, in-atáirgthe, a scríobh. Caithfidh tú cur síos soiléir, gonta ar an bhfadhb a áireamh, agus sraith treoracha chun í a mhacasamhlú. Cuir an oiread faisnéise dífhabhtaithe agus is féidir leat: snippets cód, cásanna tástála, cúltaca eisceachta, scannáin, srl Is é cás tástála deas beag an bealach is fearr chun fabht a thuairisciú, mar tugann sé bealach cabhrach dúinn an fabht a dhearbhú go tapa.
Don't post to Django Forum only to announce that you have filed a\nbug report. All the tickets are mailed to another list, django-updates,\nwhich is tracked by developers and interested community members; we see them\nas they are filed.
To understand the lifecycle of your ticket once you have created it, refer to\nSreabhadh oibre triage.
\nIf your bug impacts anything visual in nature, there are a few additional\nguidelines to follow:
\nCuir scannáin san áireamh i do thicéad atá comhionann amhairc le cás tástála íosta. Taispeáin an tsaincheist, ní na saincheaptha craiceáilte a rinne tú ar do bhrabhsálaí.
Má tá sé deacair an cheist a thaispeáint ag baint úsáide as íomhá fhór, smaoinigh ar scáileán gearrthán* a ghabháil. Má cheadaíonn do bhogearraí é, ní ghabháil ach an limistéar ábhartha den scáileán.
Má tá paiste á dtairiscint agat a athraíonn cuma nó iompar Chomhéadain Django, ní mór duit** a cheangal roimh* agus* tar éis scáileán/scáileáin scáileáin. Tá sé deacair do thríóirí ticéid nach bhfuil siad seo acu a mheas go tapa.
Ní chuireann scáileáin scáileáin ort ó dhea-chleachtais tuairiscithe eile. Déan cinnte URLanna, snippets cód, agus treoracha céim ar chéim a áireamh maidir le conas an t-iompar atá le feiceáil sna scannáin a atáirgeadh.
Déan cinnte bratach UI/UX a shocrú ar an ticéad ionas gur féidir le páirtithe leasmhara do thicéad a fháil.
If the issue relates to accessibility, please link to the relevant\naccessibility standard if applicable.
Táimid i gcónaí ag iarraidh Django a dhéanamh níos fearr, agus is cuid lárnach de sin iad d'iarrataí gné. Seo roinnt leideanna maidir le conas iarratas a dhéanamh is éifeachtaí:
\nEvaluate whether the feature idea requires changes in Django's core. If your\nidea can be developed as an independent application or module — for\ninstance, you want to support another database engine — we'll probably\nsuggest that you develop it independently. Then, if your project gathers\nsufficient community support, we may consider it for inclusion in Django.
Propose the feature in the new feature ideas GitHub project (not in the\nticket tracker) by creating a new item in the Idea column. This is where\nthe community and the Steering Council evaluate new\nideas for the Django ecosystem. This step is especially important for large\nor complex proposals. We prefer to discuss any significant changes to\nDjango's core before any development begins. In some cases, a feature may be\nbetter suited as a third-party package, where it can evolve independently of\nDjango's release cycle.
Déan cur síos soiléir agus go hachomair cad é an ghné atá in easnamh agus conas ar mhaith leat é a fheiceáil i bhfeidhm. Cuir cód samplaí san áireamh (tá neamhfheidhmiúil ceart go leor) más féidir.
Mínigh cén fá* gur mhaith leat an ghné. Cuideoidh míniú cás íosta úsáide le daoine eile tuiscint a fháil ar an áit a luíonn sé isteach, agus má tá bealaí eile ann cheana chun an rud céanna a bhaint amach.
Ba cheart go soláthródh tuairiscí ar aischéimniú feidhmíochta, nó barrfheabhsú feidhmíochta molta, tagarmharcanna agus orduithe don triager ticéad a atáirgeadh.
\nFéach na:ref: django-asv-tagarmharcans le haghaidh tuilleadh sonraí faoi thagarmharcanna Django atá ann cheana.
\nWhenever possible, we aim for rough consensus. Emoji reactions are used on\nissues within the new feature ideas GitHub project to track community\nfeedback. The following meanings are assigned to each reaction:
\n👍: I support this feature and would use it
👎: I oppose this feature or believe it would cause issues for me or Django
😕: I have no strong opinion on this feature
🎉: This feature seems like a straightforward and beneficial addition
The Steering Council will regularly review the ideas\nin the project, moving those with community support through the following\nstages:
\nIdea
Approved - Idea refinement - Team creation
In progress
Working solution - Review - Feedback
Needs maintainer (Django only)
Done
Occasionally, discussions on feature ideas or the direction of Django may take\nplace on the Django Forum. These discussions may include informal votes, which\nfollow the voting style invented by Apache and used on Python itself, where\nvotes are given as +1, +0, -0, or -1.\nRoughly translated, these votes mean:
\n+1: “Is breá liom an smaoineamh agus táim tiomanta go láidir dó.”
+0: “Fuaimeanna ceart go leor dom.”
-0: “Níl áthas orm, ach ní sheasfaidh mé ar an mbealach.”
-1: “Ní aontaím go láidir agus bheadh mé an-míshásta an smaoineamh a fheiceáil ag titim ina réaltacht.”
Cé go bhfuil na vótaí seo neamhfhoirmiúil, glacfar i ndáiríre iad. Tar éis tréimhse vótála oiriúnach, má thagann comhdhearcadh soiléir chun cinn leanfaimid na vótaí.
\nTesting pre-releases is a great way to contribute to Django. Early testers\nhelp catch bugs before the final release, ensuring a smoother upgrade\nexperience for everyone.
\nBefore testing a pre-release, it is important that your project is running\nsmoothly on the latest stable release of Django. That way, any regressions can\nbe attributed to the pre-release. See the Conas Django a uasghrádú go leagan níos nuaí guide\nfor instructions on getting up to date.
\nTo ensure your project is ready, you should also:
\nRead the release notes: Review the Nótaí scaoilte for the\nupcoming version to learn about upgrade paths for deprecated features or\nabout minor backward-incompatible changes.
Resolve deprecation warnings: Run your tests with deprecation warnings\nenabled to become aware of required follow-up actions:
\n$ python -Wa manage.py test\nYou can install the latest pre-release using pip:
$ python -m pip install --pre Django\nOnce installed, run your project's test suite. Rather than just checking\nif tests pass, try the following:
\nCheck dependency support: Determine whether major dependencies support\nthe new version by checking Django version classifiers on PyPI.\nSince those projects also value early bug reports, don't let a lack\nof support prevent you from testing.
Monitor performance: You can run your tests with the test\n--durations flag to identify potential performance regressions.
Automate tests in CI: Consider running your Continuous Integration (CI)\npipeline with the pre-release version.
Test manually: While automated tests are great, manually testing your\napplication's main workflows is an important part of verifying compatibility\nwith a new release.
If you discover a bug, please report it via the Django issue tracker so it can be fixed before the final\nrelease. When creating the ticket, be sure to set the Django version field to\nthe exact pre-release version you are testing.
\nIf you suspect a regression, it's helpful to report the specific commit that\ncaused it. See Aischéimniú a dhíghilt for instructions.
\nYou can also discuss any issues or share feedback in the Pre-releases category\non the Django Forum.
\n