Building Releases
=================

Roundup is currently a source-only release - it has no binary components. I
want it to stay that way, too. This document describes how to build a
source release. Users of Roundup should read the doc/installation.txt file
to find out how to install this software.

Building and distributing a release of Roundup is done by running:

1.  Make sure the unit tests run! "./run_tests.py"
2.  Tag the CVS for the release, eg. "cvs tag -R release-0-6-3"
3.  Edit roundup/__init__.py and doc/announcement.txt to reflect the new
    version and appropriate announcements. Add truncated announcement to
    setup.py description field.
4.  Clean out all *.orig, *.rej, .#* files from the source.
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
    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
    (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
    with all available Python versions.
11. Generate gpg signature with "gpg -a --detach-sign"
12. python setup.py bdist_rpm
13. python setup.py bdist_wininst
14. Send doc/announcement.txt to python-announce@python.org
15. Notify any other news services as appropriate...

      http://freshmeat.net/projects/roundup/


So, those commands in a nice, cut'n'pasteable form::

 find . -name '*.orig' -exec rm {} \;
 find . -name '*.rej' -exec rm {} \;
 find . -name '.#*' -exec rm {} \;
 python setup.py clean --all
 python setup.py sdist --manifest-only
 python setup.py sdist --quiet
 python setup.py bdist_rpm
 python setup.py bdist_wininst
 python setup.py register
 python2.5 setup.py sdist upload --sign