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. Add truncated announcement to
12 setup.py description field.
13 2. python setup.py clean --all
14 3. Edit setup.py to ensure that all information therein (version, contact
15 information etc) is correct.
16 4. python setup.py sdist --manifest-only
17 5. Check the MANIFEST to make sure that any new files are included. If
18 they are not, edit MANIFEST.in to include them. "Documentation" for
19 MANIFEST.in may be found in disutils.filelist._parse_template_line.
20 6. python setup.py sdist
21 (if you find sdist a little verbose, add "--quiet" to the end of the
22 command)
24 So, those commands in a nice, cut'n'pasteable form::
26 python setup.py clean --all
27 python setup.py sdist --manifest-only
28 python setup.py sdist --quiet
29 python2.3 setup.py register
32 Distributing Releases
33 =====================
35 Once a release is built, follow these steps:
37 1. FTP the tar.gz from the dist directory to to the "incoming" directory on
38 "upload.sourceforge.net".
39 2. Make a quick release at:
40 http://sourceforge.net/project/admin/qrs.php?package_id=&group_id=31577
41 3. Add a news item at:
42 https://sourceforge.net/news/submit.php?group_id=31577
43 using the top of doc/announcement.txt
44 4. Send doc/announcement.txt to python-announce@python.org
45 5. Notify any other news services as appropriate...
48 Author
49 ======
51 richard@users.sourceforge.net