Mercurial > p > roundup > code
comparison BUILD.txt @ 3588:503d4c10f1f8 1.1.1
pre-release stuff
| author | Richard Jones <richard@users.sourceforge.net> |
|---|---|
| date | Fri, 03 Mar 2006 02:29:10 +0000 |
| parents | 616244e247f4 |
| children | d8c2d214d688 |
comparison
equal
deleted
inserted
replaced
| 3587:2372597ebbdb | 3588:503d4c10f1f8 |
|---|---|
| 4 Roundup is currently a source-only release - it has no binary components. I | 4 Roundup is currently a source-only release - it has no binary components. I |
| 5 want it to stay that way, too. This document describes how to build a | 5 want it to stay that way, too. This document describes how to build a |
| 6 source release. Users of Roundup should read the doc/installation.txt file | 6 source release. Users of Roundup should read the doc/installation.txt file |
| 7 to find out how to install this software. | 7 to find out how to install this software. |
| 8 | 8 |
| 9 Building a release of Roundup is done by running: | 9 Building and distributing a release of Roundup is done by running: |
| 10 | 10 |
| 11 1. Make sure the unit tests run! "./run_tests.py" | 11 1. Make sure the unit tests run! "./run_tests.py" |
| 12 2. Tag the CVS for the release, eg. "cvs tag -R release-0-6-3" | 12 2. Tag the CVS for the release, eg. "cvs tag -R release-0-6-3" |
| 13 3. Edit roundup/__init__.py and doc/announcement.txt to reflect the new | 13 3. Edit roundup/__init__.py and doc/announcement.txt to reflect the new |
| 14 version and appropriate announcements. Add truncated announcement to | 14 version and appropriate announcements. Add truncated announcement to |
| 27 10. Unpack the new dist file in /tmp then a) run_test.py and b) demo.py | 27 10. Unpack the new dist file in /tmp then a) run_test.py and b) demo.py |
| 28 with all available Python versions. | 28 with all available Python versions. |
| 29 11. Generate gpg signature with "gpg -a --detach-sign" | 29 11. Generate gpg signature with "gpg -a --detach-sign" |
| 30 12. python setup.py bdist_rpm | 30 12. python setup.py bdist_rpm |
| 31 13. python setup.py bdist_wininst | 31 13. python setup.py bdist_wininst |
| 32 14. Send doc/announcement.txt to python-announce@python.org | |
| 33 15. Notify any other news services as appropriate... | |
| 34 | |
| 35 http://freshmeat.net/projects/roundup/ | |
| 36 | |
| 32 | 37 |
| 33 So, those commands in a nice, cut'n'pasteable form:: | 38 So, those commands in a nice, cut'n'pasteable form:: |
| 34 | 39 |
| 35 find . -name '*.orig' -exec rm {} \; | 40 find . -name '*.orig' -exec rm {} \; |
| 36 find . -name '*.rej' -exec rm {} \; | 41 find . -name '*.rej' -exec rm {} \; |
| 38 python setup.py clean --all | 43 python setup.py clean --all |
| 39 python setup.py sdist --manifest-only | 44 python setup.py sdist --manifest-only |
| 40 python setup.py sdist --quiet | 45 python setup.py sdist --quiet |
| 41 python setup.py bdist_rpm | 46 python setup.py bdist_rpm |
| 42 python setup.py bdist_wininst | 47 python setup.py bdist_wininst |
| 43 python2.3 setup.py register | 48 python setup.py register |
| 49 python2.5 setup.py sdist upload --sign | |
| 44 | 50 |
| 45 | 51 |
| 46 | |
| 47 Distributing Releases | |
| 48 ===================== | |
| 49 | |
| 50 Once a release is built, follow these steps: | |
| 51 | |
| 52 1. FTP the tar.gz from the dist directory to to the "incoming" directory on | |
| 53 "upload.sourceforge.net". | |
| 54 2. Make a quick release at: | |
| 55 http://sourceforge.net/project/admin/qrs.php?package_id=&group_id=31577 | |
| 56 3. PyPI registration / upload:: | |
| 57 | |
| 58 python setup.py register | |
| 59 python2.5 setup.py sdist upload --sign | |
| 60 | |
| 61 4. Send doc/announcement.txt to python-announce@python.org | |
| 62 5. Notify any other news services as appropriate... | |
| 63 | |
| 64 http://freshmeat.net/projects/roundup/ | |
| 65 |