Tuairisciú fabhtanna agus gnéitheLink to this heading#

Fhabhtanna a thuLink to this heading#

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 queries 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.

• Don't reopen issues that have been marked "wontfix" without finding consensus to do so on the Django Forum.

• Don't reopen issues that have been 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 the discussion 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:

• Dé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 you'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 bug report. All the tickets are mailed to another list, django-updates, which is tracked by developers and interested community members; we see them as they are filed.

To understand the lifecycle of your ticket once you have created it, refer to Sreabhadh oibre triage.

Gnéithe a iarraidhLink to this heading#

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í:

• Evaluate whether the feature idea requires changes in Django's core. If your idea can be developed as an independent application or module — for instance, you want to support another database engine — we'll probably suggest that you develop it independently. Then, if your project gathers sufficient community support, we may consider it for inclusion in Django.

• Propose the feature in the new feature ideas GitHub project (not in the ticket tracker) by creating a new item in the Idea column. This is where the community and the Steering Council evaluate new ideas for the Django ecosystem. This step is especially important for large or complex proposals. We prefer to discuss any significant changes to Django's core before any development begins. In some cases, a feature may be better suited as a third-party package, where it can evolve independently of Django'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.

Féach freisin: :ref: `documenting-new-features `.

Optamú feidhmíochta a iarraidhLink to this heading#

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.

Féach na:ref: django-asv-tagarmharcans le haghaidh tuilleadh sonraí faoi thagarmharcanna Django atá ann cheana.

Conas a dhéanaimid cinntíLink to this heading#

Whenever possible, we aim for rough consensus. Emoji reactions are used on issues within the new feature ideas GitHub project to track community feedback. The following meanings are assigned to each reaction:

• 👍: 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 in the project, moving those with community support through the following stages:

• Idea

• 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 place on the Django Forum. These discussions may include informal votes, which follow the voting style invented by Apache and used on Python itself, where votes are given as +1, +0, -0, or -1. Roughly translated, these votes mean:

• +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í.

How to test pre-release versions of DjangoLink to this heading#

Testing pre-releases is a great way to contribute to Django. Early testers help catch bugs before the final release, ensuring a smoother upgrade experience for everyone.

$ python -m pip install --pre Django