diff options
| author | Jacob Walls <jacobtylerwalls@gmail.com> | 2026-04-02 14:20:42 -0400 |
|---|---|---|
| committer | Jacob Walls <jacobtylerwalls@gmail.com> | 2026-04-10 13:37:12 -0400 |
| commit | 9391beeb8799a4b7deb4bb3048bd63465a0e96ef (patch) | |
| tree | 914508345b7db8785962758562016d5c606f257c | |
| parent | 4d8cc40c730cf0daf1d0c9a7e5ccd198b269b3ad (diff) | |
Fixed #37020 -- Removed guidance to edit fetched .po files by hand.
Altering the .po files by hand was causing incorrect line numbers and
plural forms. Since our fetching procedure does not recompile any
hand-edited .po files to .mo files for production use, just accept
Transifex's plural forms as a source of truth.
https://forum.djangoproject.com/t/discourage-releasers-from-editing-po-files-by-hand/44441
| -rw-r--r-- | docs/internals/howto-release-django.txt | 15 |
1 files changed, 1 insertions, 14 deletions
diff --git a/docs/internals/howto-release-django.txt b/docs/internals/howto-release-django.txt index 69795c76f7..248495b34c 100644 --- a/docs/internals/howto-release-django.txt +++ b/docs/internals/howto-release-django.txt @@ -210,10 +210,7 @@ A few days before any release for the new release; this will be in ``docs/releases/index.txt``. #. If this is a :term:`feature release`, ensure translations from Transifex - have been integrated. This is typically done by a separate translation's - manager rather than the releaser, but here are the steps. This process is a - 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. + have been integrated. In addition to having a configured Transifex account, ensure that the `tx CLI <https://developers.transifex.com/docs/cli>`_ is available in your @@ -240,12 +237,6 @@ A few days before any release $ 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" - All the new ``.po`` files should be manually and carefully inspected to - avoid committing a change in a file without any new translations. Also, - there shouldn't be any changes in the "plural forms": if there are any - (usually Spanish and French report changes for this) those will need - reverting. - Lastly, commit the changed/added files (both ``.po`` and ``.mo``) and create a new PR targeting the stable branch of the corresponding release (example `PR updating translations for 4.2 @@ -731,10 +722,6 @@ You're almost done! All that's left to do now is: $ django-admin makemessages -l en --domain=djangojs 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. |