1
0
mirror of https://github.com/django/django.git synced 2025-04-22 00:04:43 +00:00

[5.1.x] Documented the updating of translation catalogs in post-release tasks.

Co-authored-by: Natalia <124304+nessita@users.noreply.github.com>

Backport of 922c1c732a47c02aa5ef28b0b1a2bd9bc9b92d87 from main.
This commit is contained in:
Sarah Boyce 2025-03-20 08:31:06 +01:00
parent f927c9f2aa
commit f581b0b5c2

View File

@ -592,6 +592,38 @@ You're almost done! All that's left to do now is:
#. If this was a security release, update :doc:`/releases/security` with
details of the issues addressed.
#. If this was a pre-release, the translation catalogs need to be updated:
#. Make a new branch from the recently released stable branch:
.. code-block:: shell
git checkout stable/A.B.x
git checkout -b update-translations-catalog-A.B.x
#. Ensure that the release's dedicated virtual environment is enabled and
run the following:
.. code-block:: shell
$ cd django
$ django-admin makemessages -l en --domain=djangojs --domain=django
processing locale en
#. Review the diff before pushing and avoid committing changes to the
``.po`` files without any new translations (:commit:`example commit
<d2b1ec551567c208abfdd21b27ff6d08ae1a6371>`).
#. Make a pull request against the corresponding stable branch and merge
once approved.
#. Forward port the updated source translations to the ``main`` branch
(:commit:`example commit <aed303aff57ac990894b6354af001b0e8ea55f71>`).
#. 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>`_.
.. _Trac's versions list: https://code.djangoproject.com/admin/ticket/versions
New stable branch tasks