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! **
\nTá trí chineál eisiúintí ann a d'fhéadfadh go mbeadh ort a dhéanamh:
\nScaoiltí 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á:
\nMá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.
Cruthléigh na nótaí scaoilte, ag lorg earráidí eagraíochta agus scríbhneoireachta. Blagphost agus fógra ríomhphoist a dhréachtú.
Update version numbers and create the release artifacts.
Create the new Release in the admin on djangoproject.com.
Set the proper date but ensure the flag is_active is disabled.
Upload the artifacts (tarball, wheel, and checksums).
Fíoraigh sínithe pacáiste/na pacáistí, seiceáil an féidir iad a shuiteáil, agus cinntigh íosta feidhmiúlacht.
Uaslódáil an leagan/na leaganacha nua chuig PyPi.
Enable the is_active flag for each release in the admin on\ndjangoproject.com.
Postáil iontráil an bhlag agus seol amach na fógraí ríomhphoist.
Update version numbers post-release in stable branch(es).
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.
\n\nBeidh 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.
\nTimpeallacht Unix leis na huirlisí seo suiteáilte (in ord aibítre):
\nbash
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\nA clean Python virtual environment (Python 3.9+) to build artifacts, with\nthese required Python packages installed:
\n$ python -m pip install build twine\nAccess to Django's project on PyPI to\nupload binaries, ideally with extra permissions to yank a release if necessary. Create a project-scoped token\nfollowing the official documentation\nand set up your $HOME/.pypirc file like this:
~/.pypirc[distutils]\n index-servers =\n pypi\n django\n\n[pypi]\n username = __token__\n password = # User-scoped or project-scoped token, to set as the default.\n\n[django]\n repository = https://upload.pypi.org/legacy/\n username = __token__\n password = # A project token.\nAccess to Django's project on Transifex, with a Manager role. Generate\nan API Token in the user setting section and set up your\n$HOME/.transifexrc file like this:
[https://www.transifex.com]\n rest_hostname = https://rest.api.transifex.com\n token = # API token\nRochtain ar riarachán Django ar djangoproject.com mar “cothabhálaí láithreáin”.
Access to create a post in the Django Forum - Announcements category and to send emails to\nthe django-announce\nmailing 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.
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.
\nReserve one CVE ID per security\nissue as follows. (Or, if you lack CNA credentials, email\ncna@djangoproject.com with a request.)
Enable virtual environment with cvelib installed.
Export user information:
\n\n\n\n$ export CVE_USER=<user-email>@djangoproject.com CVE_ORG=DSF\n
Reserve:
\n\n\n\n$ cve --interactive reserve <quantity>\n
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.
Send out pre-notification exactly one week before the security release.\nThe template for that email and a list of the recipients are in the private\ndjango-security GitHub wiki. BCC the pre-notification recipients, and be\nsure to include the relevant CVE IDs. Attach all the relevant patches\n(targeting main and the stable branches), and sign the email text with\nthe key you'll use for the release, with a command like:
$ gpg --clearsign --digest-algo SHA256 prenotification-email.txt\nNotify django-announce of the upcoming\nsecurity release with a general message such as:
\nNotice 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\nPrepare issue metadata:\n* Severity\n* Short description\n* Reporter\n* Remediator\n* Reported at\n* Confirmed at (usually date CVE reserved)\n* CWE Problem Type\n* CAPEC Impact Type\n* CVSS (4.0) Score & Vector
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.
Seiceáil leis na cumaisc eile chun a chinntiú nach bhfuil aon athruithe neamhthiomanta acu don scaoileadh.
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.
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.
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`.
If this is a feature release, ensure translations from Transifex\nhave been integrated.
\nIn addition to having a configured Transifex account, ensure that the tx\nCLI is available in your\nPATH. You can then fetch all translations since a given date by running:
$ python scripts/manage_translations.py fetch -v 1 --since=<some date>\nTo determine a good value for --since, check the date of the most recent\ncommit with wording similar to Updated translations from Transifex and\nuse a date a few days prior.
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.
\nTeastaí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$ 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"\nLastly, commit the changed/added files (both .po and .mo) and create\na new PR targeting the stable branch of the corresponding release (example\nPR updating translations for 4.2).
Once merged, forward port the changes into main (example commit).
<django-admin-manpage>:ref: `Nuashonraigh an leathanach lámhleabhar django-admin `:
\n$ 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\nagus ansin an leathanach fear athraithe a thiomnú.
\nIf this is the "dot zero" release of a new series, create a new branch from\nthe current stable branch in the django-docs-translations repository. For\nexample, when releasing Django 4.2:
\n$ git checkout -b stable/4.2.x origin/stable/4.1.x\n$ git push origin stable/4.2.x:stable/4.2.x\nScrí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`__.
In preparation for the alpha release, the directory\n/home/www/www/media/releases/A.B must be created on the djangoproject\nserver.
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:
Update the VERSION tuple in django/__init__.py, incrementing to the\nnext expected release (example commit).
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).
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).
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).
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).
Concrete examples for past feature release bootstrap branches: 5.2 bootstrap, 5.1 bootstrap, 5.0 bootstrap.
\nRemove empty sections from the release notes (example commit).
Build the release notes locally and read them. Make any necessary change\nto improve flow or fix grammar (example commit).
Create a new stable branch from main. Be sure to fetch and update\nupstream to latest. For example, when feature freezing Django 5.2:
$ git fetch upstream\n$ git checkout -b stable/5.2.x upstream/main\n$ git push upstream -u stable/5.2.x:stable/5.2.x\nAt 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).
Create Release entries for the next version in the `admin`__ on\ndjangoproject.com. Add one for each milestone (alpha, beta, rc, and\nfinal), leaving is active unset to mark them as unreleased. Set target\ndates per the agreed schedule, and set the LTS flag if applicable. The\nX.Y roadmap page will be available at /download/X.Y/roadmap/.
For example, when creating stable/5.2.x, add Release entries for\n6.0a1, 6.0b1, 6.0rc1, and 6.0. The 6.0 roadmap can be\nthen reviewed at https://www.djangoproject.com/download/6.0/roadmap/.
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.
Add the new branch to Read the Docs. Since the automatically\ngenerated version names ("stable-A.B.x") differ from the version names used\nin Read the Docs ("A.B.x"), update the Read the Docs config for the version\nto point to the slug A.B.x and set it as active. See more details.
Create a PR on PyPI proposing the new Trove classifier.\nFor example Framework :: Django :: 5.2.
Update the current branch under active development and add pre-release\nbranch in the Django release process on Trac.
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.
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.
\nSeiceá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.
\nGlan 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.
<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 `).
<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 `).
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$ git checkout stable/4.1.x\n$ git pull\nMá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:
$ git checkout stable/4.1.x\n$ git merge --ff-only security/4.1.x\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`.)
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>).
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 `).
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).
Seachas sin, déan cinnte go bhfuil an aicmitheoir socraithe go Stádas Forbartha:: 5 - Táirgeacht/Cobhsa.
Clibeáil an scaoileadh ag baint úsáide as git tag. Mar shampla:
$ git tag --sign --message="Tag 4.1.1" 4.1.1\n<tag>Is féidir leat do chuid oibre a sheiceáil ag rith ``git tag --verify ``.
\nDéan cinnte go bhfuil crann go hiomlán glan agat trí git clean -dfx` a reáchtáil.
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.
Ginigh hashes na bpacáistí scaoilte:
\n$ cd dist\n$ md5sum *\n$ sha1sum *\n$ sha256sum *\nCruthaigh 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:
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<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.
Anois tá tú réidh chun an scaoileadh a chur amuigh ansin i ndáiríre. Chun seo a dhéanamh:
\nCreate 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:
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".
Set to False until the release is fully published (last step).
\nEnable if the release is part of an LTS\nbranch.
\nSet the release date to today. This release will not be published until\nis_active is enabled.
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.
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.
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).
\nUpload the release packages to PyPI:
\n$ twine upload --repository django dist/*\nUpdate the newly created Release in the admin in djangoproject.com\nand enable the is_active flag.
Brúigh do chuid oibre agus an chlib nua:
\n$ git push\n$ git push --tags\nDéan an blag post ag fógairt an scaoileadh beo.
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 `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:
$ git checkout stable/4.2.x\n$ git pull\n$ python manage_translations.py robots_txt\nPost the release announcement to the django-announce mailing list and the\nDjango Forum. This should include a link to the announcement blog post.
If this is a security release, publish the CVE metadata. (The\nchecklist app generates JSON for this.):
\n$ cve publish <cve-number> --cve-json-file <path-to-file>\nIf this is a security release, send a separate email to\noss-security@lists.openwall.com. Provide "Django" plus the CVE IDs in\nthe subject line. The message body should include the vulnerability details,\nfor example, the announcement blog post text. Include a link to the\nannouncement blog post.
Tá tú beagnach déanta! Níl le déanamh anois ach:
\nIf 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).
If this was an alpha release:
\nAdd the feature release version in Trac's versions list.
Create a new security branch from the freshly cut stable branch. Be sure\nto fetch and update upstream to latest. For example, after the 5.2\nalpha release:
$ git fetch upstream\n$ git checkout -b security/5.2.x upstream/stable/5.2.x\n$ git push origin -u security/5.2.x:security/5.2.x\nMás scaoileadh deiridh é seo:
\nUpdate the default_version setting in the code.djangoproject.com's\ntrac.ini file (example PR).
Update the current stable branch and remove the pre-release branch in the\nDjango release process on Trac.
< https://github.com/django/djangoproject.com/pull/1444>Nuashonraigh leathanach íoslódála djangoproject.com (`sampla PR`__).
Process the older versions that will reach End-Of-Mainstream and/or\nEnd-Of-Life support when this final release is published:
\nEnsure that the EOL versions are mentioned in the blog post. See\nexample announcement.
Create a tag for the EOL stable branch and delete the stable branch.\nInspect and use the scripts/archive_eol_stable_branches.py helper.
Más scaoileadh slándála a bhí ann, déan nuashonraithe:doc: `/releases/security `le sonraí na saincheisteanna a ndearnadh aghaidh orthu.
If this was a pre-release, the translation catalogs need to be updated:
\nMake a new branch from the recently released stable branch:
\n$ git checkout stable/A.B.x\n$ git checkout -b update-translations-catalog-A.B.x\nEnsure that the release's dedicated virtual environment is enabled and\nrun the following:
\n$ cd django\n$ django-admin makemessages -l en --domain=djangojs --domain=django\nprocessing locale en\nMake a pull request against the corresponding stable branch and merge\nonce approved.
Forward port the updated source translations to the main branch\n(example commit).
If this was an alpha pre-release, coordinate with the maintainer of\nasgiref to determine when to raise the minimum version before the\nfinal release. For the backport, add an upper bound on the next major\nversion (example commits:\nmain,\nbackport).
If this was an rc pre-release, call for translations for the upcoming\nrelease in the Django Forum - Internationalization category.
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í:
Leagan mór.
Leagan mion.
Leagan micrea-leagan.
Stádas - is féidir a bheith ar cheann de “alfa”, “béite”, “rc” nó “críochnaitheach”.
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”.
\nRoinnt samplaí:
\n(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"