Replace '&' with '&' in the URLs generated by classhelp(), to validate.

[roundup.git] / BUILD.txt

diff --git a/BUILD.txt b/BUILD.txt
index 5e5e9c4f268661b9a4231e25b6271b6e010cfdd5..4ee93d194c64e3761d726b5c5b26823eea98cb8b 100644 (file)
--- 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,28 +7,48 @@ want it to stay that way, too.
 This means that we only need to ever build source releases. This is done by
 running:
 
-  0. python setup.py clean --all
-  1. Edit setup.py to ensure that all information therein (version, contact
-     information etc) is correct.
-  2. python setup.py sdist --manifest-only
-  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 "--quiet" 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
-
-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
-
-
-2. Author
-=========
+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. 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)
+
+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