Mention regenerating roundup.pot in release instructions.

Author: jsm28

RELEASE.txt

@@ -7,62 +7,66 @@ Roundup, read the doc/installation.txt file.
 
 Roundup release checklist:
 
-1.  Run unit tests! They should pass successfully. "./run_tests.py"
-2.  Update version
+1.  Regenerate locale/roundup.pot.  See "Extracting Translatable
+    Messages" in doc/developers.txt.  This is best done some time in
+    advance of the release to allow for translators to update their
+    translations.
+2.  Run unit tests! They should pass successfully. "./run_tests.py"
+3.  Update version
       CHANGES.txt
       roundup/__init__.py
       website/www/index.txt
       website/www/conf.py  (also update copyright)
-2a. Update license end date in COPYING.txt
-2b. Update doc/acknowledgements.txt (add section for
+3a. Update license end date in COPYING.txt
+3b. Update doc/acknowledgements.txt (add section for
     release, churn contributers etc.).
-3.  Update documentation
+4.  Update documentation
       doc/announcement.txt
       doc/upgrading.txt
-3a. cd to website/www and run 'make linkcheck'. See output in
+4a. cd to website/www and run 'make linkcheck'. See output in
     _tmp/linkcheck/output.txt
        fix broken references in docs
        verify redirects are correct
-4.  Update setup.py info is needed (contacts, classifiers, etc.), and
+5.  Update setup.py info is needed (contacts, classifiers, etc.), and
     check that metadata is valid and long descriptions is proper reST:
       python setup.py check --restructuredtext --metadata --strict
-5.  Clean out all *.orig, *.rej, .#* files from the source.
-6.  Remove previous build files
+6.  Clean out all *.orig, *.rej, .#* files from the source.
+7.  Remove previous build files
       python setup.py clean --all
-7.  Rebuild documentation in "share/doc/roundup/html"
+8.  Rebuild documentation in "share/doc/roundup/html"
       python setup.py build_doc
-8.  python setup.py sdist --manifest-only
-9.  Check the MANIFEST to make sure that any new files are included.
+9.  python setup.py sdist --manifest-only
+10. Check the MANIFEST to make sure that any new files are included.
       (use hg status --rev <last release or tag>:tip to list changed
       added and removed files. Last release e.g. 1.5.1 where tip was
       what would become 1.6)
     If they are not, edit MANIFEST.in to include them. For format docs see
     http://docs.python.org/2/distutils/sourcedist.html#manifest-template
-10. python setup.py sdist
+11. python setup.py sdist
     (if you find sdist a little verbose, add "--quiet" to the end of the
      command)
-11. Unpack the new tarball created in dist/roundup-<version>.tar.gz
+12. Unpack the new tarball created in dist/roundup-<version>.tar.gz
     file in /tmp then
       a) run_tests.py
       b) demo.py
     with all available Python versions.
-12. Assuming all is well tag the release in the version-control
+13. Assuming all is well tag the release in the version-control
     system.
       a) hg tag 1.6.0  # use right version. Should create/commit a changeset
       b) hg push       # update main repo
       c) hg sum        # verify that the tag shows up
-13. Upload source distributive to PyPI - requires you sign up for a
+14. Upload source distributive to PyPI - requires you sign up for a
     pypi account and be added as a maintainer to roundup. Ask existing
     maintainer for access.
       python setup.py sdist upload --repository pypi --sign
     It should appear on http://pypi.python.org/pypi/roundup in no
     time. If you are using python older than 2.7.13 you need a
     .pypirc shown below. URL has changed. If using 2.7.13 or newer,
     you can remove the "--repository pypi" option.
-14. Send doc/announcement.txt to [email protected] and
+15. Send doc/announcement.txt to [email protected] and
     [email protected] and
     [email protected]
-15. Refresh website.
+16. Refresh website.
       website/README.txt
       http://www.roundup-tracker.org/ should state that the stable
       version is the one that you released.