Update customization examples too, expand upgrade notice a bit.

[roundup.git] / BUILD.txt

diff --git a/BUILD.txt b/BUILD.txt
index 53f93faae4485db3bd61f4e494addd52e059aacb..aeaf23c760ec970f11213da4e0ba5121dcfc6f41 100644 (file)
--- a/BUILD.txt
+++ b/BUILD.txt
@@ -7,21 +7,26 @@ want it to stay that way, too.
 This means that we only need to ever build source releases. This is done by
 running:
 
-1. Make sure the unit tests run! "python 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. Tag the CVS with a release tag (ie. 'release-N-N-N')
-4. python setup.py clean --all
-5. Edit setup.py to ensure that all information therein (version, contact
-   information etc) is correct.
-6. python setup.py sdist --manifest-only
-7. 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.
-8. python setup.py sdist
-   (if you find sdist a little verbose, add "--quiet" to the end of the
-    command)
+1.  Make sure the unit tests run! "./run_tests"
+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.  python setup.py clean --all
+4.  Edit setup.py to ensure that all information therein (version, contact
+    information etc) is correct.
+5.  python setup.py sdist --manifest-only
+6.  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.
+7.  python setup.py sdist
+    (if you find sdist a little verbose, add "--quiet" to the end of the
+     command)
+8.  unpack the new dist file in /tmp then a) run_test.py and b) demo.py
+    with all available Python versions.
+9.  generate gpg signature with "gpg -a --detach-sign" and upload to
+    Sourceforge.
+10. PyPI registration
+11. tag the CVS for the release, eg. "cvs tag -R release-0-6-3"
 
 So, those commands in a nice, cut'n'pasteable form::