X-Git-Url: https://git.tokkee.org/?a=blobdiff_plain;f=BUILD.txt;h=aeaf23c760ec970f11213da4e0ba5121dcfc6f41;hb=b680e6133ab5b2be7da352e29dbbb79ac2627e0a;hp=67e0c5b6173dc0d43f9e8cd981f7bc1ad480f722;hpb=1984749020970cae473169ccc5b1adc7ca04bc05;p=roundup.git

diff --git a/BUILD.txt b/BUILD.txt
index 67e0c5b..aeaf23c 100644
--- a/BUILD.txt
+++ b/BUILD.txt
@@ -1,15 +1,5 @@
-                                    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.
@@ -17,22 +7,53 @@ want it to stay that way, too.
 This means that we only need to ever build source releases. This is done by
 running:
 
-  1. Edit setup.py to ensure that all information therein (version, contact
-     information etc) is correct.
-  2. python setup.py sdist -o
-  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 "-q" 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
-
-
-
-2. Author
-=========
-richard@sourceforge.net
+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::
+
+ python setup.py clean --all
+ python setup.py sdist --manifest-only
+ python setup.py sdist --quiet
+ python2.3 setup.py register
+
+
+Distributing Releases
+=====================
+
+Once a release is built, follow these steps:
+
+1. FTP the tar.gz from the dist directory to to the "incoming" directory on
+   "upload.sourceforge.net".
+2. Make a quick release at:
+    http://sourceforge.net/project/admin/qrs.php?package_id=&group_id=31577
+3. Add a news item at:
+    https://sourceforge.net/news/submit.php?group_id=31577
+   using the top of doc/announcement.txt
+4. Send doc/announcement.txt to python-announce@python.org
+5. Notify any other news services as appropriate...
+
+
+Author
+======
+
+richard@users.sourceforge.net