1 Building Releases
2 =================
4 Roundup is currently a source-only release - it has no binary components. I
5 want it to stay that way, too.
7 This means that we only need to ever build source releases. This is done by
8 running:
10 1. Edit roundup/__init__.py and doc/announcement.txt to reflect the new
11 version and appropriate announcements.
12 2. python setup.py clean --all
13 3. Edit setup.py to ensure that all information therein (version, contact
14 information etc) is correct.
15 4. python setup.py sdist --manifest-only
16 5. Check the MANIFEST to make sure that any new files are included. If
17 they are not, edit MANIFEST.in to include them. "Documentation" for
18 MANIFEST.in may be found in disutils.filelist._parse_template_line.
19 6. python setup.py sdist
20 (if you find sdist a little verbose, add "--quiet" to the end of the
21 command)
23 So, those commands in a nice, cut'n'pasteable form::
25 python setup.py clean --all
26 python setup.py sdist --manifest-only
27 python setup.py sdist --quiet
28 python2.3 setup.py register
30 or, for the sad RedHat users::
32 python2 setup.py clean --all
33 python2 setup.py sdist --manifest-only
34 python2 setup.py sdist --quiet
35 python2.3 setup.py register
38 Distributing Releases
39 =====================
41 Once a release is built, follow these steps:
43 1. FTP the tar.gz from the dist directory to to the "incoming" directory on
44 "upload.sourceforge.net".
45 2. Make a quick release at:
46 http://sourceforge.net/project/admin/qrs.php?package_id=&group_id=31577
47 3. Add a news item at:
48 https://sourceforge.net/news/submit.php?group_id=31577
49 using the top of doc/announcement.txt
50 4. Send doc/announcement.txt to python-announce@python.org
51 5. Notify any other news services as appropriate...
54 Author
55 ======
57 richard@users.sourceforge.net