From 922c1c732a47c02aa5ef28b0b1a2bd9bc9b92d87 Mon Sep 17 00:00:00 2001 From: Sarah Boyce <42296566+sarahboyce@users.noreply.github.com> Date: Thu, 20 Mar 2025 08:31:06 +0100 Subject: [PATCH] Documented the updating of translation catalogs in post-release tasks. Co-authored-by: Natalia <124304+nessita@users.noreply.github.com> --- docs/internals/howto-release-django.txt | 32 +++++++++++++++++++++++++ 1 file changed, 32 insertions(+) diff --git a/docs/internals/howto-release-django.txt b/docs/internals/howto-release-django.txt index 5427ab31c0..c0543ee214 100644 --- a/docs/internals/howto-release-django.txt +++ b/docs/internals/howto-release-django.txt @@ -680,6 +680,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 + `). + + #. 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 `). + +#. If this was an ``rc`` pre-release, call for translations for the upcoming + release in the `Django Forum - Internationalization category + `_. + .. _Trac's versions list: https://code.djangoproject.com/admin/ticket/versions Notes on setting the VERSION tuple