diff --git a/docs/internals/contributing/localizing.txt b/docs/internals/contributing/localizing.txt
index bb06da156d..f5837dbd8f 100644
--- a/docs/internals/contributing/localizing.txt
+++ b/docs/internals/contributing/localizing.txt
@@ -45,6 +45,13 @@ translating or add a language that isn't yet translated, here's what to do:
      For more information about how to use Transifex, read the
      `Transifex User Guide`_.
 
+Translations from Transifex are only integrated into the Django repository at
+the time of a new major release. We try to update them a second time during one
+of the following minor releases, but that depends on the translation manager's
+availability. So don't miss the string freeze period (between the release
+candidate and the major release) to take the opportunity to complete and fix
+the translations for your language!
+
 Formats
 -------
 
diff --git a/docs/internals/howto-release-django.txt b/docs/internals/howto-release-django.txt
index 56a9de9d40..624489503e 100644
--- a/docs/internals/howto-release-django.txt
+++ b/docs/internals/howto-release-django.txt
@@ -112,6 +112,17 @@ any time leading up to the actual release:
 #. Double-check that the release notes index has a link to the notes
    for the new release; this will be in ``docs/releases/index.txt``.
 
+#. If this is a major 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. Provided you have an
+   account on Transifex::
+
+        python scripts/manage_translations.py fetch
+
+   and then commit the changed/added files (both .po and .mo). Sometimes there
+   are validation errors which need to be debugged, so avoid doing this task
+   immediately before a release is needed.
+
 Preparing for release
 =====================