diff --git a/BUILD.txt b/BUILD.txt
index b12fc87772f510202ab828844ffd38cd75b38c59..27e3479735832cfe9110f1fb0be468e8d38179bb 100644 (file)
--- a/BUILD.txt
+++ b/BUILD.txt
Building and distributing a release of Roundup is done by running:
1. Make sure the unit tests run! "./run_tests.py"
-2. XXX "tag" SVN??
-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.
+2. Edit roundup/__init__.py and doc/announcement.txt to reflect the new
+ version and appropriate announcements.
+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
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...
+11. Assuming all is well tag the release in SVN::
- http://freshmeat.net/projects/roundup/
+ svn cp https://roundup.svn.sourceforge.net/svnroot/roundup/roundup/trunk \
+ https://roundup.svn.sourceforge.net/svnroot/roundup/roundup/tags/release-1-4-16
+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::
python setup.py bdist_rpm
python setup.py bdist_wininst
python setup.py register
- python2.5 setup.py sdist upload --sign
-
+ 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+)