From 4a824b13134a63d189a58e68f925e7201fa3befe Mon Sep 17 00:00:00 2001 From: Natalia <124304+nessita@users.noreply.github.com> Date: Fri, 4 Apr 2025 15:01:15 -0300 Subject: [PATCH] Added usage for `--since` when fetching translations in docs/internals/howto-release-django.txt. --- docs/internals/howto-release-django.txt | 15 +++++++++++---- 1 file changed, 11 insertions(+), 4 deletions(-) diff --git a/docs/internals/howto-release-django.txt b/docs/internals/howto-release-django.txt index c0543ee214..88456bda08 100644 --- a/docs/internals/howto-release-django.txt +++ b/docs/internals/howto-release-django.txt @@ -215,13 +215,17 @@ A few days before any release bit lengthy so be sure to set aside 4-10 hours to do this, and ideally plan for this task one or two days ahead of the release day. - In addition to having a configured Transifex account, the - `tx CLI `_ should be available in - your ``PATH``. Then, you can fetch all the translations by running: + In addition to having a configured Transifex account, ensure that the `tx + CLI `_ is available in your + ``PATH``. You can then fetch all translations since a given date by running: .. code-block:: shell - $ python scripts/manage_translations.py fetch + $ python scripts/manage_translations.py fetch -v 1 --since= + + To determine a good value for ``--since``, check the date of the most recent + commit with wording similar to ``Updated translations from Transifex`` and + use a date a few days prior. This command takes some time to run. When done, carefully inspect the output for potential errors and/or warnings. If there are some, you will need to @@ -247,6 +251,9 @@ A few days before any release `PR updating translations for 4.2 `_). + Once merged, forward port the changes into ``main`` (:commit:`example + commit `). + #. :ref:`Update the django-admin manual page `: .. code-block:: shell