--- title: "How to release Django" version: 5.2 locale: ga source: https://docs.djangoproject.com/ga/5.2/internals/howto-release-django/ canonical: https://djangodocs.dev/ga/5.2/internals/howto-release-django/ --- # How to release Django 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 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! \*\* ## Forbhreathnú Tá trí chineál eisiúintí ann a d'fhéadfadh go mbeadh ort a dhéanamh: - Scaoiltí slándála: leochaileacht a nochtadh agus a shocrú De ghnáth beidh dhá nó trí eisiúint chomhuaineach i gceist leis seo - m.sh. 3.2.x, 4.0.x, agus, ag brath ar an uainiú, b'fhéidir 4.1.x. - Eisiúintí leagan rialta: scaoileadh deiridh (m.sh. 4.1) nó nuashonrú bugfix (m.sh. 4.1.1). - Réamh-eisiúintí: m.sh. 4.2 alfa, béite, nó rc. Is é an leagan gairid de na céimeanna atá i gceist 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. 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. Update version numbers and create the release artifacts. 4. Create the new `Release` in the admin on `djangoproject.com`. 1. Set the proper date but ensure the flag `is_active` is disabled. 2. Upload the artifacts (tarball, wheel, and checksums). 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. Uaslódáil an leagan/na leaganacha nua chuig PyPi. 7. Enable the `is_active` flag for each release in the admin on `djangoproject.com`. 8. Postáil iontráil an bhlag agus seol amach na fógraí ríomhphoist. 9. Update version numbers post-release in stable branch(es). 10. Add stub release notes for the next patch release in `main` and backport. Tá go leor sonraí ann, mar sin léigh ar aghaidh le do thoil. ## Riachtanais 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. - Timpeallacht Unix leis na huirlisí seo suiteáilte (in ord aibítre): - bash - git - GPG - déanamh - fear - uirlisí hashing (de ghnáth ```md5sum ``, `sha1sum```, agus `sha256sum` ar Linux, nó `md5` agus shasum\` ar macOS) - python - Péire eochair GPG. Cinntigh go bhfuil an chuid príobháideach den eochair seo stóráilte go daingean. Ní mór an chuid poiblí a uaslódáil chuig do chuntas GitHub, agus chuig freastalaí Jenkins a reáchtáil an post “scaoileadh deimhnithe”. > **Níos mó ná eochair GPG amháin** > > Mura bhfuil an eochair is mian leat a úsáid d'eochair shínithe réamhshocraithe, beidh ort -u you@example.com \`\`a chur le gach ordú sínithe GPG a thaispeántar thíos, áit ar\` [you@example.com](mailto:you@example.com) an seoladh ríomhphoist a bhaineann leis an eochair is mian leat a úsáid. - A clean Python virtual environment (Python 3.9+) to build artifacts, with these required Python packages installed: ```shell $ python -m pip install build twine ``` - \< \>Rochtain ar thionscadal chun dénártha \< \> a uaslódáil, go hidéalach le ceadanna breise chun agus cu\< \> ir ar bun do chomhad `$HOME/.pypirc` mar seo: *`~/.pypirc`* ```ini [distutils] index-servers = pypi django [pypi] username = __token__ password = # User-scoped or project-scoped token, to set as the default. [django] repository = https://upload.pypi.org/legacy/ username = __token__ password = # A project token. ``` - Rochtain ar thionscadal \< \>, le ról Bainisteora. Ginigh Comhartha API sa rannán socrú úsáideora \`\_ agus cu\< https://app.transifex.com/user/settings/api/\> ir ar bun do chomhad \`\`$HOME/.transifexRC\` mar seo: *~/.transifexrc \`\`* ```ini [https://www.transifex.com] rest_hostname = https://rest.api.transifex.com token = # API token ``` - Rochtain ar riarachán Django ar `djangoproject.com` mar “cothabhálaí láithreáin”. - Access to create a post in the [Django Forum - Announcements category](https://forum.djangoproject.com/c/announcements/7) and to send emails to the [django-announce](https://groups.google.com/g/django-announce/) mailing list. - Rochtain ar an repo \`\` django-security\`\` i GitHub. I measc rudaí eile, soláthraíonn sé seo rochtain ar an liosta dáileacháin réamhfhógraí (a theastaíonn le haghaidh tascanna ullmhúcháin um scaoileadh slándála). - Access to the Django project on [Read the Docs](https://readthedocs.org/projects/django/). ## Tascanna réamhscaoilte 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. ### 10 lá (nó níos mó) roimh scaoileadh slándála 1. Iarr na maidir leis na saincheisteanna slán\< \> 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. 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. ### Seachtain roimh scaoileadh slándála 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: ```shell $ gpg --clearsign --digest-algo SHA256 prenotification-email.txt ``` 2. [Notify django-announce](/ga/5.2/internals/security/#security-disclosure) of the upcoming security release with a general message such as: ```text Notice of upcoming Django security releases (3.2.24, 4.2.10 and 5.0.2) Django versions 5.0.2, 4.2.10, and 3.2.24 will be released on Tuesday, February 6th, 2024 around 1500 UTC. They will fix one security defect with severity "moderate". For details of severity levels, see: https://docs.djangoproject.com/en/dev/internals/security/#how-django-discloses-security-issues ``` ### Cúpla lá roimh aon scaoileadh 1. As the release approaches, watch Trac to make sure no release blockers are left for the upcoming release. Under exceptional circumstances, such as to meet a pre-determined security release date, a release could still go ahead with an open release blocker. The releaser is trusted with the decision to release with an open release blocker or to postpone the release date of a non-security release if required. 2. Seiceáil leis na cumaisc eile chun a chinntiú nach bhfuil aon athruithe neamhthiomanta acu don scaoileadh. 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 \\`nó earráidí REST, agus déan cinnte go bhfuil an dáta ceart sna nótaí scaoilte. 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. 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. 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. Chomh maith le cuntas Transifex cumraithe a bheith agat, ba chóir go mbeadh an [tx CLI](#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: ```shell $ python scripts/manage_translations.py fetch ``` 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. 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): ```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" ``` 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. \< \>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 ). 7. \:ref: Nuashonraigh an leathanach lámhleabhar django-admin : ```shell $ cd docs $ make man $ man _build/man/django-admin.1 # do a quick sanity check $ cp _build/man/django-admin.1 man/django-admin.1 ``` agus ansin an leathanach fear athraithe a thiomnú. 8. \< \>Más é seo an scaoileadh “dot nialas” de shraith nua, cruthaigh brainse nua ón mbrainse cobhsaí reatha sa stór [django-docs-translations](#django-docs-translations). Mar shampla, agus Django 4.2 á scaoileadh: ```shell $ git checkout -b stable/4.2.x origin/stable/4.1.x $ git push origin stable/4.2.x:stable/4.2.x ``` 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: . #### A few days before a feature freeze In preparation for the alpha release, the directory `/home/www/www/media/releases/A.B` must be created on the djangoproject server. Before the feature freeze, a branch targeting `main` must be created to prepare for the next feature release. It should be reviewed and approved a few days before the freeze, allowing it to be merged after the stable branch is cut. The following items should be addressed in this branch: 1. Update the `VERSION` tuple in `django/__init__.py`, incrementing to the next expected release ([example commit](https://github.com/django/django/commit/96700c7b378c592f0b1732302c22af2fd2c87fc6)). 2. Create a stub release note for the next feature release. Use the stub from the previous feature release or copy the contents from the current version and delete most of the contents leaving only the headings ([example commit](https://github.com/django/django/commit/9b5ad4056ccf9ff7ea548f72d28eb66c1b4f84cc)). 3. Remove `.. versionadded::` and `.. versionchanged::` annotations in the documentation from two releases ago, as well as any remaining older annotations. For example, in Django 5.1, notes for 4.2 will be removed ([example commit](https://github.com/django/django/commit/9edb7833b89e811eefd94974fb987f4605b0c0d7)). 4. Remove features that have reached the end of their deprecation cycle, including their docs and the `.. deprecated::` annotation. Each removal should be done in a separate commit for clarity. In the commit message, add a `Refs #XXXXX --` prefix linking to the original ticket where the deprecation began if possible. Make sure this gets noted in the removed features section in the release notes ([example commit](https://github.com/django/django/commit/f2d9c76aa7096ef3eed675b9eb824858f9dd81e5)). 5. Increase the default PBKDF2 iterations in `django.contrib.auth.hashers.PBKDF2PasswordHasher` by about 20% (pick a round number). Run the tests, and update the 3 failing hasher tests with the new values. Make sure this gets noted in the release notes ([example commit](https://github.com/django/django/commit/7288866da4dddf3705148c703421858ec19cdb78)). Concrete examples for past feature release bootstrap branches: [5.2 bootstrap](https://github.com/django/django/pull/18127), [5.1 bootstrap](https://github.com/django/django/pull/17246), [5.0 bootstrap](https://github.com/django/django/pull/16432). ## Feature freeze tasks 1. Remove empty sections from the release notes ([example commit](https://github.com/django/django/commit/9e6e58bad237a80ddd5e3ab8b834cecdaad8455e)). 2. Build the release notes locally and read them. Make any necessary change to improve flow or fix grammar ([example commit](https://github.com/django/django/commit/435bdab93889dae01e71c79598edab10627cc1f9)). 3. Create a new stable branch from `main`. For example, when feature freezing Django 5.2: ```shell $ git checkout -b stable/5.2.x upstream/main $ git push upstream -u stable/5.2.x:stable/5.2.x ``` At the same time, update the `django_next_version` variable in `docs/conf.py` on the stable release branch to point to the new development version. For example, when creating `stable/5.2.x`, set `django_next_version` to `'6.0'` on the new stable branch ([example commit](https://github.com/django/django/commit/1eb62e5b622ef7fd6e0123d8bbf6662d893d5d08)). 4. Go to the , create a `Release` object for the *final* release, ensuring that the *Release date* field is blank, thus marking it as *unreleased*. For example, when creating `stable/5.2.x`, create `5.2` with the Release date field blank. If the release is part of an LTS branch, mark it so. 5. Go to the , create a new `DocumentRelease` object for the English language for the newly created `Release` object. Do not mark this as default. 6. Cuir an brainse nua leis . \< \>Ó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”), ag iarraidh an leagan nua. 7. [Request the new classifier on PyPI](https://github.com/pypa/trove-classifiers/issues/29). For example `Framework :: Django :: 5.2`. 8. Create a [roadmap page](https://code.djangoproject.com/wiki/Version6.0Roadmap) for the next release on Trac. To create a new page on the Wiki, navigate to the URL of where you wish to create the page and a "Create this page" button will be available. 9. \< \>Nuashonraigh an brainse reatha atá faoi fhorbairt ghníomhach agus cuir brainse réamh-scaoilte leis sa próiseas scaoilte Django \_ ar Trac. 10. Update the `docs/fixtures/doc_releases.json` JSON fixture for djangoproject.com, so people without access to the production DB can still run an up-to-date copy of the docs site ([example PR](https://github.com/django/djangoproject.com/pull/1446)). This will be merged after the final release. ## I ndáiríre an scaoilte 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. 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. 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. 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. \<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. 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: ```shell $ git checkout stable/4.1.x $ git pull ``` 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: ```shell $ git checkout stable/4.1.x $ git merge --ff-only security/4.1.x ``` (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\`.) 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 \). 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í](#notes-on-setting-the-version-tuple) thíos le haghaidh sonraí faoi VERSION\` (:commit: example commit ). 1. If this is a pre-release package also update the "Development Status" trove classifier in `pyproject.toml` to reflect this. An `rc` pre-release should not change the trove classifier ([example commit for alpha release](https://github.com/django/django/commit/759921c8e9ad151932fc913ab429fef0a6112ef8), [example commit for beta release](https://github.com/django/django/commit/25fec8940b24107e21314ab6616e18ce8dec1c1c)). 2. Seachas sin, déan cinnte go bhfuil an aicmitheoir socraithe go `Stádas Forbartha:: 5 - Táirgeacht/Cobhsa`. ### Building the artifacts > **Optionally use helper scripts** > > You can streamline some of the steps below using helper scripts from the > `scripts` folder: > > - Release script example run: > > ```shell > $ PGP_KEY_ID= PGP_KEY_URL= DEST_FOLDER=~/releases scripts/do_django_release.py > ``` > > - Verify the release (after artifacts were uploaded): > > ```shell > $ VERSION=5.2.1 scripts/verify_release.sh > ``` 1. Clibeáil an scaoileadh ag baint úsáide as `git tag`. Mar shampla: ```shell $ git tag --sign --message="Tag 4.1.1" 4.1.1 ``` \Is féidir leat do chuid oibre a sheiceáil ag rith git tag --verify . 2. Déan cinnte go bhfuil crann go hiomlán glan agat trí git clean -dfx\` a reáchtáil. 3. Run `python -m build` to generate the release packages. This will create the release artifacts (tarball and wheel) in a `dist/` directory. For Django 5.0 or older, you need to run `make -f extras/Makefile` instead. 4. Ginigh hashes na bpacáistí scaoilte: ```shell $ cd dist $ md5sum * $ sha1sum * $ sha256sum * ``` 5. Cruthaigh comhad “checksums”, `Django- < > .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: ```text This file contains MD5, SHA1, and SHA256 checksums for the source-code tarball and wheel files of Django <>, released <>. To use this file, you will need a working install of PGP or other compatible public-key encryption software. You will also need to have the Django release manager's public key in your keyring. This key has the ID ``XXXXXXXXXXXXXXXX`` and can be imported from GitHub, for example, if using the open-source GNU Privacy Guard implementation of PGP: curl https://github.com/<>.gpg | gpg --import - Once the key is imported, verify this file: gpg --verify <> Once you have verified this file, you can use normal MD5, SHA1, or SHA256 checksumming applications to generate the checksums of the Django package and compare them to the checksums listed below. Release packages ================ https://www.djangoproject.com/download/<>/tarball/ https://www.djangoproject.com/download/<>/wheel/ MD5 checksums ============= <> <> <> <> SHA1 checksums ============== <> <> <> <> SHA256 checksums ================ <> <> <> <> ``` 6. \Sínigh an comhad seiceála (`gpg --clearsign --digest-algo SHA256 Django- .checksum.txt`). \Gineann sé seo doiciméad sínithe, `Django- .checksum.txt.asc` ar féidir leat a fhíorú ansin ag baint úsáide as `gpg --verify Django- .checksum.txt.asc`. ## An scaoileadh (í) a chur ar fáil don phobal Anois tá tú réidh chun an scaoileadh a chur amuigh ansin i ndáiríre. Chun seo a dhéanamh: 1. Create a new `Release` entry in the [djangoproject.com's admin](https://www.djangoproject.com/admin/releases/release/add/). If this is a security release, this should be done 15 minutes before the announced release time, no sooner: **Leagan** Must match the version number as defined in the tarball (`django-.tar.gz`). For example: "5.2", "4.1.1", or "4.2rc1". **Is active** Set to False until the release is fully published (last step). **LTS** Enable if the release is part of an LTS (Long Term Support) branch. **Dates** Set the release date to today. This release will not be published until `is_active` is enabled. **Artifacts** Upload the tarball (`django-.tar.gz`), wheel (`django--py3-none-any.whl`), and checksum (`django-.checksum.txt.asc`) files created earlier. 2. Test that the release packages install correctly using `pip`. Here's one simple method (this just tests that the binaries are available, that they install correctly, and that migrations and the development server start, but it'll catch silly mistakes): . 3. Rith an tógáil ar Jenkins chun an comhad (í) seicsum a fhíorú (m.sh. bain úsáid as 4.2rc1\` le haghaidh ). 4. Uaslódáil na pacáistí scaoilte chuig PyPi (le haghaidh réamh-eisiúintí, uaslódáil ach an comhad roth): ```shell $ twine upload --repository django dist/* ``` 5. Update the newly created `Release` in the admin in `djangoproject.com` and enable the `is_active` flag. 6. Brúigh do chuid oibre agus an chlib nua: ```shell $ git push $ git push --tags ``` 7. Déan an blag post ag fógairt an scaoileadh beo. 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). Cruthaigh rudaí nua `DocumentRelease` do gach teanga a bhfuil iontráil aige don eisiúint roimhe seo. Nuashonraigh comhad 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 . Mar shampla, agus Django 4.2 á scaoileadh: ```shell $ git checkout stable/4.2.x $ git pull $ python manage_translations.py robots_txt ``` 9. Post the release announcement to the [django-announce](/ga/5.2/internals/mailing-lists/#django-announce-mailing-list) mailing list and the Django Forum. This should include a link to the announcement blog post. 10. Más scaoileadh slándála é seo, seol ríomhphost ar leithligh chuig [oss-security@lists.openwall.com](mailto: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. ## Iar-scaoileadh Tá tú beagnach déanta! Níl le déanamh anois ach: 1. If this is not a pre-release, update the `VERSION` tuple in `django/__init__.py` again, incrementing to whatever the next expected release will be. For example, after releasing 4.1.1, update `VERSION` to `VERSION = (4, 1, 2, 'alpha', 0)` ([example commit](https://github.com/django/django/commit/a4d19953d46247ee1992b3427fe652e941524272)). 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 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”. 3. Más scaoileadh deiridh é seo: 1. \< \>Nuashonraigh an brainse cobhsaí reatha agus bain an brainse réamh-scaoilte sa phróiseas scaoilte Django \_ ar Trac. 2. \< \>Nuashonraigh leathanach íoslódála djangoproject.com (). 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. If this was a pre-release, the translation catalogs need to be updated: 1. Make a new branch from the recently released stable branch: ```shell git checkout stable/A.B.x git checkout -b update-translations-catalog-A.B.x ``` 2. Ensure that the release's dedicated virtual environment is enabled and run the following: ```shell $ cd django $ django-admin makemessages -l en --domain=djangojs --domain=django processing locale en ``` 3. Review the diff before pushing and avoid committing changes to the `.po` files without any new translations ([example commit](https://github.com/django/django/commit/d2b1ec551567c208abfdd21b27ff6d08ae1a6371)). 4. Make a pull request against the corresponding stable branch and merge once approved. 5. Forward port the updated source translations to the `main` branch ([example commit](https://github.com/django/django/commit/aed303aff57ac990894b6354af001b0e8ea55f71)). 6. If this was an `rc` pre-release, call for translations for the upcoming release in the [Django Forum - Internationalization category](https://forum.djangoproject.com/c/internals/i18n/14). ## Nótaí maidir leis an tuple VERSION a shocrú 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í: 1. Leagan mór. 2. Leagan mion. 3. Leagan micrea-leagan. 4. Stádas - is féidir a bheith ar cheann de “alfa”, “béite”, “rc” nó “críochnaitheach”. 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.). 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”. Roinnt samplaí: - `(4, 1, 1, “deiridh”, 0)` → “4.1.1" - `(4, 2, 0, “alfa”, 0)` → “4.2 réamh-alfa” - `(4, 2, 0, “béite”, 1)` → “4.2 béite 1"