03/03: doc: Document the process of updating the translation files.

[Maxim Cournoyer]

apteryx pushed a commit to branch master
in repository maintenance.

commit 007a94f59370912a6b2a1ccc44bed96ad4eec7ca
Author: Maxim Cournoyer <maxim.cournoyer@gmail.com>
AuthorDate: Sun Apr 18 12:18:55 2021 -0400

    doc: Document the process of updating the translation files.
    
    In the context of preparing a new release.
    
    * doc/release.org (Updating the translation files): New section.
---
 doc/release.org | 24 +++++++++++++++++++++++-
 1 file changed, 23 insertions(+), 1 deletion(-)

diff --git a/doc/release.org b/doc/release.org
index 5011cba..e0f9f04 100644
--- a/doc/release.org
+++ b/doc/release.org
@@ -42,13 +42,35 @@ your maintenance.git checkout.  Make sure to commit it:
 Create a signed Git tag, like this:
 
   $ git tag -s -u MY-KEY -m "GNU Guix X.YrcZ." vX.YrcZ
-  $ autoreconf -f  # to update $(PACKAGE_VERSION)
 
 Use “rcZ” for release candidates, drop it otherwise.
 
 The tag must be `vX.Y'.  For the sake of consistency, always use
 "GNU Guix X.Y." as the tag comment.
 
+** Updating the translation files
+
+If running from a pristine checkout, you'll need to run bootstrap and
+configure to have the 'release' target available in the Makefile.
+
+  $ ./bootstrap
+  $ ./configure --localstatedir=/var --sysconfdir=/etc
+
+If you already have the 'release' target available, invoking 'make
+release' will automatically invoke ./bootstrap.
+
+Next you will need to fetch, update and commit the translation files,
+if you haven't done so already:
+
+  $ make download-po
+  $ make doc-po-update
+  $ git add po
+  $ git commit -m 'nls: Update translations.'
+
+The downloading and committing of the .po files is not automated as it
+takes time (about 2 minutes), and all files are re-downloaded every
+time it runs.
+
 ** Run “make release” for one or several release candidates
 
 This will automatically build: