{"title":"How to release Django","version":"5.2","locale":"ga","docname":"internals/howto-release-django","url":"/ga/5.2/internals/howto-release-django/","canonical":"https://djangodocs.dev/ga/5.2/internals/howto-release-django/","summary":"Míníonn an doiciméad seo conas Django a scaoiltear. ** Coinnigh na treoracha seo cothrom le dáta má dhéanann tú athruithe! ** Is é an pointe anseo a bheith…","html":"

How to release DjangoLink to this heading#

\n

Míníonn an doiciméad seo conas Django a scaoiltear.

\n

** Coinnigh na treoracha seo cothrom le dáta má dhéanann tú athruithe! ** Is é an pointe anseo a bheith tuairisciúil, gan oiriúnaitheach, mar sin bíodh leisce ort athruithe a shruthlíniú nó a dhéanamh ar shlí eile, ach**nuashonrú an doiciméad seo dá réir sin! **

\n
\n

ForbhreathnúLink to this heading#

\n

Tá trí chineál eisiúintí ann a d'fhéadfadh go mbeadh ort a dhéanamh:

\n\n

Is é an leagan gairid de na céimeanna atá i gceist ná:

\n
    \n

  1. Más scaoileadh slándála é seo, déan an liosta dáilte slándála réamh-fógra seachtain roimh an eisiúint iarbhír.

    2. \n

  2. Cruthléigh na nótaí scaoilte, ag lorg earráidí eagraíochta agus scríbhneoireachta. Blagphost agus fógra ríomhphoist a dhréachtú.

    3. \n

  3. Update version numbers and create the release artifacts.

    4. \n

  4. Create the new Release in the admin on djangoproject.com.

    \n
      \n

    1. Set the proper date but ensure the flag is_active is disabled.

      2. \n

    2. Upload the artifacts (tarball, wheel, and checksums).

      3. \n
    \n
    5. \n

  5. Fíoraigh sínithe pacáiste/na pacáistí, seiceáil an féidir iad a shuiteáil, agus cinntigh íosta feidhmiúlacht.

    6. \n

  6. Uaslódáil an leagan/na leaganacha nua chuig PyPi.

    7. \n

  7. Enable the is_active flag for each release in the admin on\ndjangoproject.com.

    8. \n

  8. Postáil iontráil an bhlag agus seol amach na fógraí ríomhphoist.

    9. \n

  9. Update version numbers post-release in stable branch(es).

    10. \n

  10. Add stub release notes for the next patch release in main and backport.

    11. \n
\n

Tá go leor sonraí ann, mar sin léigh ar aghaidh le do thoil.

\n
\n
\n

RiachtanaisLink to this heading#

\n

Beidh cúpla rud ag teastáil uait sula dtosaíonn tú. Más é seo do chéad eisiúint, beidh ort comhordú a dhéanamh le scaoilteoir eile chun na rudaí seo go léir a líneáil suas, agus scríobh chuig liosta seoltaí Ops ag iarraidh an rochtain agus na ceadanna riachtanacha.

\n\n
\n
\n

Tascanna réamhscaoilteLink to this heading#

\n

Ní mór aire a thabhairt do chúpla earra sula dtosaíonn tú fiú leis an bpróiseas scaoilte. Tosaíonn an stuif seo thart ar sheachtain roimh an scaoileadh; is féidir an chuid is mó de a dhéanamh am ar bith chun an scaoileadh iarbhír.

\n
\n

10 lá (nó níos mó) roimh scaoileadh slándálaLink to this heading#

\n
    \n

  1. Iarr na `ID CVE`_ maidir leis na saincheisteanna slán< https://cveform.mitre.org/> dála atá á scaoileadh. Aitheantas CVE amháin in aghaidh na heisiúna, a iarrtar le Díoltóir: djangoproject agus Táirge: django.

    2. \n

  2. Ginigh an paiste/paistí (príobháideacha) ábhartha ag baint úsáide as git format-patch, ceann don bhrainse príom agus ceann do gach brainse chobhsaí atá á phaiteáil.

    3. \n
\n
\n
\n

Seachtain roimh scaoileadh slándálaLink to this heading#

\n
    \n

  1. Seol réamh-fhógra amach go díreach seachtain roimh an scaoileadh slándála. Tá an teimpléad don ríomhphost sin agus liosta de na faighteoirí sa wiki príobháideach django-slándála` `GitHub. BCC na faighteoirí réamhfhógra agus bí cinnte go gcuirfidh tú na ID CVE ábhartha san áireamh. Ceangail na paistí ábhartha go léir (ag díriú ar ``main agus na brainsí cobhsaí) agus sínigh an téacs ríomhphoist leis an eochair a úsáidfidh tú chun an scaoileadh, le ordú mar:

    \n
    Shell
    $ gpg --clearsign --digest-algo SHA256 prenotification-email.txt\n
    \n
    2. \n

  2. Notify django-announce of the upcoming\nsecurity release with a general message such as:

    \n
    Text
    Notice of upcoming Django security releases (3.2.24, 4.2.10 and 5.0.2)\n\nDjango versions 5.0.2, 4.2.10, and 3.2.24 will be released on Tuesday,\nFebruary 6th, 2024 around 1500 UTC. They will fix one security defect\nwith severity "moderate".\n\nFor details of severity levels, see:\nhttps://docs.djangoproject.com/en/dev/internals/security/#how-django-discloses-security-issues\n
    \n
    3. \n
\n
\n
\n

Cúpla lá roimh aon scaoileadhLink to this heading#

\n
    \n

  1. As the release approaches, watch Trac to make sure no release blockers are\nleft for the upcoming release. Under exceptional circumstances, such as to\nmeet a pre-determined security release date, a release could still go ahead\nwith an open release blocker. The releaser is trusted with the decision to\nrelease with an open release blocker or to postpone the release date of a\nnon-security release if required.

    2. \n

  2. Seiceáil leis na cumaisc eile chun a chinntiú nach bhfuil aon athruithe neamhthiomanta acu don scaoileadh.

    3. \n

  3. Léigh na nótaí scaoilte, lena n-áirítear féachaint ar an leagan ar líne chó:ref: `gabháil aon naisc bhriste <documentation-link-check>`nó earráidí REST, agus déan cinnte go bhfuil an dáta ceart sna nótaí scaoilte.

    4. \n

  4. Seiceáil faoi dhó go luann na nótaí scaoilte amlínte míshuaimseartha d'aon APIs a tugadh faoi deara mar atá díscothaithe, agus go luann siad aon athruithe i dtacaíocht leagan Python.

    5. \n

  5. Seiceáil faoi dhó go bhfuil nasc ag an innéacs nótaí scaoilte leis na nótaí don eisiúint nua; beidh sé seo i docs/releases/index.txt`.

    6. \n

  6. Más a: téarma é seo: scaoileadh gnéit, déan cinnte go bhfuil aistriúcháin ó Transifex comhtháite. De ghnáth déanann bainisteoir aistriúcháin ar leithligh é seo seachas an scaoilteoir, ach seo na céimeanna. Tá an próiseas seo beagán fada mar sin bí cinnte 4-10 uair an chloig a chur ar leataobh chun é seo a dhéanamh, agus go hidéalach pleanáil don tasc seo lá nó dhó roimh an lá scaoilte.

    \n

    Chomh maith le cuntas Transifex cumraithe a bheith agat, ba chóir go mbeadh an tx CLI ar fáil i do < https://developers.transifex.com/docs/cli> PATH`. Ansin, is féidir leat na haistriúcháin go léir a fháil trí rith:

    \n
    Shell
    $ python scripts/manage_translations.py fetch\n
    \n

    Tógann an t-ordú seo roinnt ama le rith. Nuair a dhéantar é, iniúchadh cúramach ar an aschur le haghaidh earráidí agus/nó rabhaidh Má tá roinnt ann, beidh ort iad a dhífhabhtú agus a réiteach ar bhonn cás ar chás.

    \n

    Teastaíonn coigeartú láimhe ó na haistriúcháin a fuarthas le Ar an gcéad dul síos, caithfear na luachanna Po-Revision-Date ``a bhualadh de láimh le go mbeidh siad níos déanaí ná ``Pot-Creation-Date`. Is féidir leat ordú cosúil leis seo a úsáid chun na comhaid `.po ``go léir a nuashonrú mórchóir (comparáid idir an diff i gcoinne an bhrainse chobhsaí ábhartha):

    \n
    Shell
    $ git diff --name-only stable/5.0.x | grep "\\.po"  | xargs sed -ri "s/PO-Revision-Date: [0-9\\-]+ /PO-Revision-Date: $(date -I) /g"\n
    \n

    Ba chóir na comhaid nua .po a iniúchadh de láimh agus go cúramach chun athrú a sheachaint ar chomhad gan aon aistriúcháin nua a sheachaint. Chomh maith leis sin, níor chóir go mbeadh aon athruithe sna “foirmeacha iolra”: má tá aon athruithe ann (athruithe tuarascálacha na Spáinne agus na Fraince de ghnáth) beidh gá leo siúd a chur ar ais.

    \n

    < https://github.com/django/django/pull/16715>Ar deireadh, déan na comhaid athraithe/breise (.po agus .mo` araon) a cheangal agus cruthaigh PR nua atá dírithe ar bhrainse chobhsaí an eisiúint chomhfhreagrach (sampla `PR ag nuashonrú aistriúcháin do 4.2`_).

    \n
    7. \n

  7. <django-admin-manpage>:ref: `Nuashonraigh an leathanach lámhleabhar django-admin `:

    \n
    Shell
    $ cd docs\n$ make man\n$ man _build/man/django-admin.1  # do a quick sanity check\n$ cp _build/man/django-admin.1 man/django-admin.1\n
    \n

    agus ansin an leathanach fear athraithe a thiomnú.

    \n
    8. \n

  8. < https://github.com/django/django-docs-translations>Más é seo an scaoileadh “dot nialas” de shraith nua, cruthaigh brainse nua ón mbrainse cobhsaí reatha sa stór django-docs-translations. Mar shampla, agus Django 4.2 á scaoileadh:

    \n
    Shell
    $ git checkout -b stable/4.2.x origin/stable/4.1.x\n$ git push origin stable/4.2.x:stable/4.2.x\n
    \n
    9. \n

  9. Scríobh an bhlagphost fógra don scaoileadh. Is féidir leat é a iontráil isteach sa riarachán ag am ar bith agus é a mharcáil mar neamhghníomhach. Seo cúpla sampla: `sampla fógra scaoilte slándála `__, `sampla fógra scaoilte rialta `__, `fógra réamh-scaoilte sampla`__.

    10. \n
\n
\n

A few days before a feature freezeLink to this heading#

\n

In preparation for the alpha release, the directory\n/home/www/www/media/releases/A.B must be created on the djangoproject\nserver.

\n

Before the feature freeze, a branch targeting main must be created to\nprepare for the next feature release. It should be reviewed and approved a few\ndays before the freeze, allowing it to be merged after the stable branch is\ncut. The following items should be addressed in this branch:

\n
    \n

  1. Update the VERSION tuple in django/__init__.py, incrementing to the\nnext expected release (example commit).

    2. \n

  2. Create a stub release note for the next feature release. Use the stub from\nthe previous feature release or copy the contents from the current version\nand delete most of the contents leaving only the headings\n(example commit).

    3. \n

  3. Remove .. versionadded:: and .. versionchanged:: annotations in the\ndocumentation from two releases ago, as well as any remaining older\nannotations. For example, in Django 5.1, notes for 4.2 will be removed\n(example commit).

    4. \n

  4. Remove features that have reached the end of their deprecation cycle,\nincluding their docs and the .. deprecated:: annotation. Each removal\nshould be done in a separate commit for clarity. In the commit message, add\na Refs #XXXXX -- prefix linking to the original ticket where the\ndeprecation began if possible. Make sure this gets noted in the removed\nfeatures section in the release notes (example commit).

    5. \n

  5. Increase the default PBKDF2 iterations in\ndjango.contrib.auth.hashers.PBKDF2PasswordHasher by about 20%\n(pick a round number). Run the tests, and update the 3 failing\nhasher tests with the new values. Make sure this gets noted in the\nrelease notes (example commit).

    6. \n
\n

Concrete examples for past feature release bootstrap branches: 5.2 bootstrap, 5.1 bootstrap, 5.0 bootstrap.

\n
\n
\n
\n
\n

Feature freeze tasksLink to this heading#

\n
    \n

  1. Remove empty sections from the release notes (example commit).

    2. \n

  2. Build the release notes locally and read them. Make any necessary change\nto improve flow or fix grammar (example commit).

    3. \n

  3. Create a new stable branch from main. For example, when feature freezing\nDjango 5.2:

    \n
    Shell
    $ git checkout -b stable/5.2.x upstream/main\n$ git push upstream -u stable/5.2.x:stable/5.2.x\n
    \n

    At the same time, update the django_next_version variable in\ndocs/conf.py on the stable release branch to point to the new\ndevelopment version. For example, when creating stable/5.2.x, set\ndjango_next_version to '6.0' on the new stable branch\n(example commit).

    \n
    4. \n

  4. Go to the `Add release page in the admin`__, create a Release object for\nthe final release, ensuring that the Release date field is blank, thus\nmarking it as unreleased. For example, when creating stable/5.2.x,\ncreate 5.2 with the Release date field blank. If the release is part of\nan LTS branch, mark it so.

    \n
    5. \n

  5. Go to the `Add document release page in the admin`__, create a new\nDocumentRelease object for the English language for the newly created\nRelease object. Do not mark this as default.

    \n
    6. \n

  6. Cuir an brainse nua leis `Léigh na Doc< https://readthedocs.org/projects/django/> s`_. < https://github.com/readthedocs/readthedocs.org/issues/5537>Ós rud é go bhfuil difríocht idir na hainmneacha leagan a ghintear go huathoibríoch (“Stable-A.B.X”) ó na hainmneacha leagan a úsáidtear in Read the Docs (“A.b.x”), `cruthaigh ticéad`_ ag iarraidh an leagan nua.

    7. \n

  7. Request the new classifier on PyPI. For example\nFramework :: Django :: 5.2.

    8. \n

  8. Create a roadmap page for the next\nrelease on Trac. To create a new page on the Wiki, navigate to the URL of\nwhere you wish to create the page and a "Create this page" button will be\navailable.

    9. \n

  9. < https://code.djangoproject.com/#Djangoreleaseprocess>Nuashonraigh an brainse reatha atá faoi fhorbairt ghníomhach agus cuir brainse réamh-scaoilte leis sa `próiseas scaoilte Django `_ ar Trac.

    10. \n

  10. Update the docs/fixtures/doc_releases.json JSON fixture for\ndjangoproject.com, so people without access to the production DB can still\nrun an up-to-date copy of the docs site\n(example PR).\nThis will be merged after the final release.

    11. \n
\n
\n
\n

I ndáiríre an scaoilteLink to this heading#

\n

Ceart go leor, is é seo an chuid spraíúil, áit a bhrúimid scaoileadh amach i ndáiríre! Má tá tú ag eisiúint ileisiúint, déan na céimeanna seo arís do gach scaoileadh.

\n
    \n

  1. Seiceáil go bhfuil `Jenkins `__ glas don leagan/na leaganacha atá tú ag cur amach. Is dócha nár cheart duit scaoileadh a eisiúint go dtí go mbeidh sé glas, agus ba cheart duit a chinntiú go gcuimsíonn an rith glas is déanaí na hathruithe atá á scaoileadh agat.

    \n
    2. \n

  2. Glan na nótaí scaoilte don eisiúint seo. Déan na hathruithe seo i príom agus backport chuig gach brainse ina bhfuil na nótaí scaoilte do leagan áirithe suite.

    \n
      \n

    1. <1994a2643881a9e3f9fa8d3e0794c1a9933a1831>Le haghaidh scaoileadh gné, bain an ceannteideal UNDER DEVELOPMENT ag barr na nótaí scaoilte, bain an réimír ``Táthas ag súil leis ``agus nuashonraigh an dáta scaoilte, más gá (:commit: `example commit `).

      2. \n

    2. <34a503162fe222033a1cd3249bccad014fcd1d20>Le haghaidh scaoileadh paiste, bain an réimír ``Táim ag súil leis ``agus nuashonraigh an dáta scaoilte do gach eisiúint, más gá (:commit: `example commit `).

      3. \n
    \n
    3. \n

  3. Tosaíonn scaoileadh i gcónaí ó bhrainse scaoilte, mar sin ba cheart duit a chinntiú go bhfuil tú ar bhrainse cobhsaí cothro Chomh maith leis sin, ba cheart go mbeadh timpeallacht fhíorúil glan tiomnaithe ar fáil agat in aghaidh an leagan atá Mar shampla:

    \n
    Shell
    $ git checkout stable/4.1.x\n$ git pull\n
    \n
    4. \n

  4. Más scaoileadh slándála é seo, cumaisc na paistí cuí ó django-slándáil `. Athbhunaigh na paistí seo de réir mar is gá chun tiomantas simplí a dhéanamh ar gach ceann ar an mbrainse scaoilte seachas tiomantas cumaisc. Chun é seo a chinntiú, déan iad a chumasc leis an bhratach --ff-only; mar shampla:

    \n
    Shell
    $ git checkout stable/4.1.x\n$ git merge --ff-only security/4.1.x\n
    \n

    (Glacann sé leis seo gur brainse sa repo django-slándála ina bhfuil na paistí slándála riachtanacha don chéad eisiúint eile sa tsraith 4.1 é slándálaí/4.1.x`.)

    \n

    Má dhiúltaíonn git cumasc le --ff-only, aistrigh go dtí an brainse paiste slándála agus athbhunaigh é ar an mbrainse atá ar tí é a chumasc isteach (git checkout security/4.1.x; git rebase stable/4.1.x) agus ansin athraigh ar ais agus déan an cumaisc. Déan cinnte go míníonn an teachtaireacht tiomanta do gach socrú slándála gur socrú slándála é an tiomantas agus go leanfaidh fógra (:commit: example security commit <bf39978a53f117ca02e9a0c78b76664a41a54745>).

    \n
    5. \n

  5. Nuashonraigh an uimhir leagan i django/__init__.py don scaoileadh. <2719a7f8c161233f45d34b624a9df9392c86cc1b>Féach le do thoil nótaí maidir le feadán VERSION a shocraí thíos le haghaidh sonraí faoi VERSION` (:commit: `example commit `).

    \n
      \n

    1. If this is a pre-release package also update the "Development Status"\ntrove classifier in pyproject.toml to reflect this. An rc\npre-release should not change the trove classifier (example\ncommit for alpha release,\nexample commit for beta release).

      2. \n

    2. Seachas sin, déan cinnte go bhfuil an aicmitheoir socraithe go Stádas Forbartha:: 5 - Táirgeacht/Cobhsa.

      3. \n
    \n
    6. \n
\n
\n

Building the artifactsLink to this heading#

\n\n
    \n

  1. Clibeáil an scaoileadh ag baint úsáide as git tag. Mar shampla:

    \n
    Shell
    $ git tag --sign --message="Tag 4.1.1" 4.1.1\n
    \n

    <tag>Is féidir leat do chuid oibre a sheiceáil ag rith ``git tag --verify ``.

    \n
    2. \n

  2. Déan cinnte go bhfuil crann go hiomlán glan agat trí git clean -dfx` a reáchtáil.

    3. \n

  3. Run python -m build to generate the release packages. This will create\nthe release artifacts (tarball and wheel) in a dist/ directory. For\nDjango 5.0 or older, you need to run make -f extras/Makefile instead.

    4. \n

  4. Ginigh hashes na bpacáistí scaoilte:

    \n
    Shell
    $ cd dist\n$ md5sum *\n$ sha1sum *\n$ sha256sum *\n
    \n
    5. \n

  5. Cruthaigh comhad “checksums”, Django- <<VERSION> > .checksum.txt ina bhfuil na hashes agus scaoil faisnéis. Tosaigh leis an teimpléad seo agus cuir isteach an leagan ceart, an dáta, an ID eochair GPG (ó gpg --list-keys --keyid-format LONG `), ainm úsáideora GitHub bainisteora scaoilte, URL scaoilte, agus seicsuimeanna:

    \n
    Text
    This file contains MD5, SHA1, and SHA256 checksums for the source-code\ntarball and wheel files of Django <<VERSION>>, released <<DATE>>.\n\nTo use this file, you will need a working install of PGP or other\ncompatible public-key encryption software. You will also need to have\nthe Django release manager's public key in your keyring. This key has\nthe ID ``XXXXXXXXXXXXXXXX`` and can be imported from GitHub, for example,\nif using the open-source GNU Privacy Guard implementation of PGP:\n\n    curl https://github.com/<<RELEASE MANAGER GITHUB USERNAME>>.gpg | gpg --import -\n\nOnce the key is imported, verify this file:\n\n    gpg --verify <<THIS FILENAME>>\n\nOnce you have verified this file, you can use normal MD5, SHA1, or SHA256\nchecksumming applications to generate the checksums of the Django\npackage and compare them to the checksums listed below.\n\nRelease packages\n================\n\nhttps://www.djangoproject.com/download/<<VERSION>>/tarball/\nhttps://www.djangoproject.com/download/<<VERSION>>/wheel/\n\nMD5 checksums\n=============\n\n<<MD5SUM>>  <<RELEASE TAR.GZ FILENAME>>\n<<MD5SUM>>  <<RELEASE WHL FILENAME>>\n\nSHA1 checksums\n==============\n\n<<SHA1SUM>>  <<RELEASE TAR.GZ FILENAME>>\n<<SHA1SUM>>  <<RELEASE WHL FILENAME>>\n\nSHA256 checksums\n================\n\n<<SHA256SUM>>  <<RELEASE TAR.GZ FILENAME>>\n<<SHA256SUM>>  <<RELEASE WHL FILENAME>>\n
    \n
    6. \n

  6. <version>Sínigh an comhad seiceála (gpg --clearsign --digest-algo SHA256 Django- .checksum.txt). <version>Gineann sé seo doiciméad sínithe, Django- <version>.checksum.txt.asc ar féidir leat a fhíorú ansin ag baint úsáide as gpg --verify Django- .checksum.txt.asc.

    7. \n
\n
\n
\n
\n

An scaoileadh (í) a chur ar fáil don phobalLink to this heading#

\n

Anois tá tú réidh chun an scaoileadh a chur amuigh ansin i ndáiríre. Chun seo a dhéanamh:

\n
    \n

  1. Create a new Release entry in the djangoproject.com's admin. If this is a\nsecurity release, this should be done 15 minutes before the announced\nrelease time, no sooner:

    \n
    \n
    Leagan

    Must match the version number as defined in the tarball\n(django-<version>.tar.gz). For example: "5.2", "4.1.1", or "4.2rc1".

    \n
    \n
    Is active

    Set to False until the release is fully published (last step).

    \n
    \n
    LTS

    Enable if the release is part of an LTS\nbranch.

    \n
    \n
    Dates

    Set the release date to today. This release will not be published until\nis_active is enabled.

    \n
    \n
    Artifacts

    Upload the tarball (django-<version>.tar.gz), wheel\n(django-<version>-py3-none-any.whl), and checksum\n(django-<version>.checksum.txt.asc) files created earlier.

    \n
    \n
    \n
    2. \n

  2. Test that the release packages install correctly using pip. Here's one\nsimple method (this just tests that the binaries are available, that they\ninstall correctly, and that migrations and the development server start, but\nit'll catch silly mistakes):\nhttps://code.djangoproject.com/wiki/ReleaseTestNewVersion.

    3. \n

  3. Rith an tógáil `confirm-release`__ ar Jenkins chun an comhad (í) seicsum a fhíorú (m.sh. bain úsáid as 4.2rc1` le haghaidh https://media.djangoproject.com/pgp/Django-4.2rc1.checksum.txt).

    \n
    4. \n

  4. Uaslódáil na pacáistí scaoilte chuig PyPi (le haghaidh réamh-eisiúintí, uaslódáil ach an comhad roth):

    \n
    Shell
    $ twine upload --repository django dist/*\n
    \n
    5. \n

  5. Update the newly created Release in the admin in djangoproject.com\nand enable the is_active flag.

    6. \n

  6. Brúigh do chuid oibre agus an chlib nua:

    \n
    Shell
    $ git push\n$ git push --tags\n
    \n
    7. \n

  7. Déan an blag post ag fógairt an scaoileadh beo.

    8. \n

  8. Le haghaidh scaoileadh leagan nua (m.sh. 4.1, 4.2), nuashonraigh an leagan cobhsaí réamhshocraithe de na doiciméid tríd an bhratach is_default a fhilleadh go True` ar an réad cuí DocumentRelease` sa bhunachar sonraí docs.djangoproject.com (déanfaidh sé seo go huathoibríoch go False` do gach duine eile).

    \n

    Cruthaigh rudaí nua DocumentRelease do gach teanga a bhfuil iontráil aige don eisiúint roimhe seo. Nuashonraigh comhad `robots.docs.txt`__ djangoproject.com tríd an toradh a ghintear ón ordú manage_translations.py robots_txt` a reáchtáil sa bhrainse chobhsaí reatha ón stóras `django-docs-translationy`__. Mar shampla, agus Django 4.2 á scaoileadh:

    \n
    Shell
    $ git checkout stable/4.2.x\n$ git pull\n$ python manage_translations.py robots_txt\n
    \n
    9. \n

  9. Post the release announcement to the django-announce mailing list and the\nDjango Forum. This should include a link to the announcement blog post.

    10. \n

  10. Más scaoileadh slándála é seo, seol ríomhphost ar leithligh chuig oss-security@lists.openwall.com. Cuir ábhar tuairisciúil ar fáil, mar shampla, “Django” móide teideal an eisiúna ó na nótaí scaoilte (lena n-áirítear ID CVE). Ba chóir go mbeadh na sonraí leochaileachta san áireamh sa chomhlacht teachtaireachta, mar shampla, téacs blag an bhlag Cuir nasc leis an bpost blag fógra san áireamh.

    11. \n
\n
\n
\n

Iar-scaoileadhLink to this heading#

\n

Tá tú beagnach déanta! Níl le déanamh anois ach:

\n
    \n

  1. If this is not a pre-release, update the VERSION tuple in\ndjango/__init__.py again, incrementing to whatever the next expected\nrelease will be. For example, after releasing 4.1.1, update VERSION to\nVERSION = (4, 1, 2, 'alpha', 0) (example commit).

    2. \n

  2. Cuir an scaoileadh i liosta leaganacha Trac `_ más gá (agus déan é an réamhshocraithe tríd an socrú ``default_version` a athrú i `trac.ini`__ an code.djangoproject.com, más scaoileadh deiridh é). Ba chóir an leagan nua X.Y a chur leis tar éis an scaoileadh alfa agus ba chóir an leagan réamhshocraithe a nuashonrú tar éis scaoileadh “dot nialas”.

    \n
    3. \n

  3. Más scaoileadh deiridh é seo:

    \n
      \n

    1. < https://code.djangoproject.com/#Djangoreleaseprocess>Nuashonraigh an brainse cobhsaí reatha agus bain an brainse réamh-scaoilte sa phróiseas scaoilte `Django `_ ar Trac.

      2. \n

    2. < https://github.com/django/djangoproject.com/pull/1444>Nuashonraigh leathanach íoslódála djangoproject.com (`sampla PR`__).

      3. \n
    \n
    4. \n

  4. Más scaoileadh slándála a bhí ann, déan nuashonraithe:doc: `/releases/security `le sonraí na saincheisteanna a ndearnadh aghaidh orthu.

    5. \n

  5. If this was a pre-release, the translation catalogs need to be updated:

    \n
      \n

    1. Make a new branch from the recently released stable branch:

      \n
      Shell
      git checkout stable/A.B.x\ngit checkout -b update-translations-catalog-A.B.x\n
      \n
      2. \n

    2. Ensure that the release's dedicated virtual environment is enabled and\nrun the following:

      \n
      Shell
      $ cd django\n$ django-admin makemessages -l en --domain=djangojs --domain=django\nprocessing locale en\n
      \n
      3. \n

    3. Review the diff before pushing and avoid committing changes to the\n.po files without any new translations (example commit).

      4. \n

    4. Make a pull request against the corresponding stable branch and merge\nonce approved.

      5. \n

    5. Forward port the updated source translations to the main branch\n(example commit).

      6. \n
    \n
    6. \n

  6. If this was an rc pre-release, call for translations for the upcoming\nrelease in the Django Forum - Internationalization category.

    7. \n
\n
\n
\n

Nótaí maidir leis an tuple VERSION a shocrúLink to this heading#

\n

Tá tuairisciú leagan Django á rialú ag an tuipéal VERSION i django/__init__.py`. Is tuple cúig ghné é seo, a bhfuil a n-eilimintí:

\n
    \n

  1. Leagan mór.

    2. \n

  2. Leagan mion.

    3. \n

  3. Leagan micrea-leagan.

    4. \n

  4. Stádas - is féidir a bheith ar cheann de “alfa”, “béite”, “rc” nó “críochnaitheach”.

    5. \n

  5. Uimhir an tsraith, le haghaidh pacáistí alpha/beta/RC a ritheann i seicheamh (ag ceadú, mar shampla, “béita 1", “béite 2", srl.).

    6. \n
\n

Le haghaidh scaoileadh deiridh, bíonn an stádas “deiridh” i gcónaí agus is é uimhir na sraithe i gcónaí 0. Tuairiscítear uimhir shraith 0 le stádas “alfa” mar “réamh-alfa”.

\n

Roinnt samplaí:

\n\n
","rootId":"how-to-release-django","toc":[{"title":"Forbhreathnú","anchor":"overview","children":[]},{"title":"Riachtanais","anchor":"prerequisites","children":[]},{"title":"Tascanna réamhscaoilte","anchor":"pre-release-tasks","children":[{"title":"10 lá (nó níos mó) roimh scaoileadh slándála","anchor":"or-more-days-before-a-security-release","children":[]},{"title":"Seachtain roimh scaoileadh slándála","anchor":"a-week-before-a-security-release","children":[]},{"title":"Cúpla lá roimh aon scaoileadh","anchor":"a-few-days-before-any-release","children":[{"title":"A few days before a feature freeze","anchor":"a-few-days-before-a-feature-freeze","children":[]}]}]},{"title":"Feature freeze tasks","anchor":"feature-freeze-tasks","children":[]},{"title":"I ndáiríre an scaoilte","anchor":"actually-rolling-the-release","children":[{"title":"Building the artifacts","anchor":"building-the-artifacts","children":[]}]},{"title":"An scaoileadh (í) a chur ar fáil don phobal","anchor":"making-the-release-s-available-to-the-public","children":[]},{"title":"Iar-scaoileadh","anchor":"post-release","children":[]},{"title":"Nótaí maidir leis an tuple VERSION a shocrú","anchor":"notes-on-setting-the-version-tuple","children":[]}],"breadcrumbs":[{"docname":"internals/index","title":"Inmheánacha Django","url":"/ga/5.2/internals/"}],"prev":{"docname":"internals/git","title":"Stóráil cód foinse Django","url":"/ga/5.2/internals/git/"},"next":null,"formats":{"html":"/ga/5.2/internals/howto-release-django/","markdown":"/ga/5.2/internals/howto-release-django.md","json":"/ga/5.2/internals/howto-release-django.json"},"source":"https://github.com/django/django/blob/stable/5.2.x/docs/internals/howto-release-django.txt","official":"https://docs.djangoproject.com/ga/5.2/internals/howto-release-django/","inVersions":["6.1","6.0","5.2"],"inLocales":["en","sv","zh-hans","ga","fr","ja","id","it","pt-br","ko","es","el","pl"]}