1.1 --- a/README.txt	Fri Jul 22 20:39:10 2005 +0000
     1.2 +++ b/README.txt	Fri Jul 22 21:00:31 2005 +0000
     1.3 @@ -113,3 +113,31 @@
     1.4  that there is no apparent need to explicitly declare the corresponding global
     1.5  variables in stylesheets. Whilst this is nice, we may eventually need to
     1.6  detect such variables and add them in the preparation process.
     1.7 +
     1.8 +Release Procedures
     1.9 +------------------
    1.10 +
    1.11 +Update the XSLOutput.py and XSLForms/__init__.py __version__ attributes.
    1.12 +Change the version number and package filename/directory in the documentation.
    1.13 +Change code examples in the documentation if appropriate.
    1.14 +Update the release notes (see above).
    1.15 +Check the setup.py file and ensure that all package directories are mentioned.
    1.16 +Tag, export.
    1.17 +Generate the API documentation.
    1.18 +Remove generated .pyc files: rm `find . -name "*.pyc"`
    1.19 +Archive, upload.
    1.20 +Upload the introductory documentation.
    1.21 +Update PyPI, PythonInfo Wiki, Vaults of Parnassus entries.
    1.22 +
    1.23 +Generating the API Documentation
    1.24 +--------------------------------
    1.25 +
    1.26 +In order to prepare the API documentation, it is necessary to generate some
    1.27 +Web pages from the Python source code. For this, the epydoc application must
    1.28 +be available on your system. Then, inside the XSLTools directory, run the
    1.29 +apidocs.sh tool script as follows:
    1.30 +
    1.31 +./tools/apidocs.sh
    1.32 +
    1.33 +Some warnings may be generated by the script, but the result should be a new
    1.34 +apidocs directory within the XSLTools directory.