X-Git-Url: https://git.tokkee.org/?a=blobdiff_plain;f=BUILD.txt;h=029e46ef566fd9897c0a4ebaea7a03d9637d5ea4;hb=8d67f20bccc8f06c9615b1f57bad31517c230d73;hp=7527efa527bd9b581f6135bb94d63518569f4f98;hpb=aeb51a142a54ad7dee42f94713787954d3ca6e60;p=roundup.git diff --git a/BUILD.txt b/BUILD.txt index 7527efa..029e46e 100644 --- a/BUILD.txt +++ b/BUILD.txt @@ -1,44 +1,54 @@ - Roundup - ======= - - This software is released under the GNU GPL. The copyright is held by Bizar - Software Pty Ltd (http://www.bizarsoftware.com.au). - - The stylesheet included with this package has been copied from the Zope - management interface and presumably belongs to Digital Creations. - - -1. Building Releases -==================== +Building Releases +================= Roundup is currently a source-only release - it has no binary components. I -want it to stay that way, too. - -This means that we only need to ever build source releases. This is done by -running: - - 0. python setup.py clean --all - 1. Edit setup.py to ensure that all information therein (version, contact - information etc) is correct. - 2. python setup.py sdist --manifest-only - 3. 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. - 4. python setup.py sdist - (if you find sdist a little verbose, add "--quiet" to the end of the - command) - 5. FTP the tar.gz from the dist directory to to the "incoming" directory on - "upload.sourceforge.net". - 6. Make a quick release at: - http://sourceforge.net/project/admin/qrs.php?package_id=&group_id=31577 - -So, those commands in a nice, cut'n'pasteable form :) -python setup.py clean --all -python setup.py sdist --manifest-only -python setup.py sdist --quiet - - -2. Author -========= -richard@sourceforge.net - +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. Edit roundup/__init__.py and doc/announcement.txt to reflect the new + version and appropriate announcements. Add truncated announcement to + setup.py description field. +3. Note the SVN revision in the CHANGES.txt file. +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. 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.12 + +11. python setup.py bdist_rpm +12. python setup.py bdist_wininst +13. Send doc/announcement.txt to python-announce@python.org and + roundup-users@lists.sourceforge.net and + roundup-devel@lists.sourceforge.net + +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 + python setup.py sdist upload --sign + python setup.py bdist_wininst upload --sign + +(if the last two fail make sure you're using python2.5+)