Mercurial > p > roundup > code
changeset 4807:641f0895d306
Revise BUILD.txt
| author | anatoly techtonik <techtonik@gmail.com> |
|---|---|
| date | Thu, 22 Aug 2013 15:42:21 +0300 |
| parents | cc7ed637b7d0 |
| children | 08efc4993e82 |
| files | BUILD.txt |
| diffstat | 1 files changed, 9 insertions(+), 11 deletions(-) [+] |
line wrap: on
line diff
--- a/BUILD.txt Mon Jul 08 17:25:33 2013 +0200 +++ b/BUILD.txt Thu Aug 22 15:42:21 2013 +0300 @@ -1,21 +1,19 @@ 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. +Roundup is a pure Python application with no binary components. This file +describes how to build a source release. To find out how to install +Roundup, read the doc/installation.txt file. -Building and distributing a release of Roundup is done by running: +Roundup release checklist: -1. Make sure the unit tests run! "./run_tests.py" -2. Edit roundup/__init__.py, CHANGES.txt and doc/announcement.txt to - reflect the new version and appropriate announcements. -3. Note the date in the CHANGES.txt file. +1. Run unit tests! They should pass successfully. "./run_tests.py" +2. Change version in roundup/__init__.py, record date in CHANGES.txt. +3. Update doc/announcement.txt with new details. 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. +6. Edit setup.py to ensure that all information therein (contacts, + classifiers, etc) is correct. 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
