Document 'build_doc' step.

Author: stefanseefeld

BUILD.txt

@@ -16,23 +16,24 @@ Building and distributing a release of Roundup is done by running:
 5.  python setup.py clean --all
 6.  Edit setup.py to ensure that all information therein (version, contact
     information etc) is correct.
-7.  python setup.py sdist --manifest-only
-8.  Check the MANIFEST to make sure that any new files are included. If
+7.  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. If
     they are not, edit MANIFEST.in to include them. "Documentation" for
     MANIFEST.in may be found in disutils.filelist._parse_template_line.
-9.  python setup.py sdist
+10. python setup.py sdist
     (if you find sdist a little verbose, add "--quiet" to the end of the
      command)
-10. Unpack the new dist file in /tmp then a) run_test.py and b) demo.py
+11. Unpack the new dist file in /tmp then a) run_test.py and b) demo.py
     with all available Python versions.
-11. Assuming all is well tag the release in SVN::
+12. Assuming all is well tag the release in SVN::
 
       svn cp https://roundup.svn.sourceforge.net/svnroot/roundup/roundup/trunk \
       https://roundup.svn.sourceforge.net/svnroot/roundup/roundup/tags/release-1-4-16
 
-11. python setup.py bdist_rpm
-12. python setup.py bdist_wininst
-13. Send doc/announcement.txt to [email protected] and
+13. python setup.py bdist_rpm
+14. python setup.py bdist_wininst
+15. Send doc/announcement.txt to [email protected] and
     [email protected] and
     [email protected]
 
@@ -42,6 +43,7 @@ So, those commands in a nice, cut'n'pasteable form::
  find . -name '*.rej' -exec rm {} \;
  find . -name '.#*' -exec rm {} \;
  python setup.py clean --all
+ python setup.py build_doc
  python setup.py sdist --manifest-only
  python setup.py sdist --quiet
  python setup.py bdist_rpm