Skip to content

Commit 721ca16

Browse files
author
Richard Jones
committed
cleanup
1 parent 98058fc commit 721ca16

File tree

1 file changed

+45
-44
lines changed

1 file changed

+45
-44
lines changed

BUILD.txt

Lines changed: 45 additions & 44 deletions
Original file line numberDiff line numberDiff line change
@@ -1,55 +1,56 @@
1-
Roundup
2-
=======
3-
4-
1. Building Releases
5-
====================
1+
Building Releases
2+
=================
63

74
Roundup is currently a source-only release - it has no binary components. I
85
want it to stay that way, too.
96

107
This means that we only need to ever build source releases. This is done by
118
running:
129

13-
0. Edit setup.py and doc/announcement.txt to reflect the new version and
14-
appropriate announcments.
15-
1. python setup.py clean --all
16-
2. Edit setup.py to ensure that all information therein (version, contact
17-
information etc) is correct.
18-
3. python setup.py sdist --manifest-only
19-
4. Check the MANIFEST to make sure that any new files are included. If
20-
they are not, edit MANIFEST.in to include them. "Documentation" for
21-
MANIFEST.in may be found in disutils.filelist._parse_template_line.
22-
5. python setup.py sdist
23-
(if you find sdist a little verbose, add "--quiet" to the end of the
24-
command)
25-
26-
So, those commands in a nice, cut'n'pasteable form :)
27-
python setup.py clean --all
28-
python setup.py sdist --manifest-only
29-
python setup.py sdist --quiet
30-
31-
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-
36-
37-
2. Distributing Releases
38-
========================
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)
22+
23+
So, those commands in a nice, cut'n'pasteable form::
24+
25+
python setup.py clean --all
26+
python setup.py sdist --manifest-only
27+
python setup.py sdist --quiet
28+
29+
or, for the sad RedHat users::
30+
31+
python2 setup.py clean --all
32+
python2 setup.py sdist --manifest-only
33+
python2 setup.py sdist --quiet
34+
35+
36+
Distributing Releases
37+
=====================
3938

4039
Once a release is built, follow these steps:
41-
1. FTP the tar.gz from the dist directory to to the "incoming" directory on
42-
"upload.sourceforge.net".
43-
2. Make a quick release at:
44-
http://sourceforge.net/project/admin/qrs.php?package_id=&group_id=31577
45-
3. Add a news item at:
46-
https://sourceforge.net/news/submit.php?group_id=31577
47-
using the top of doc/announcement.txt
48-
4. Send doc/announcement.txt to [email protected]
49-
5. Notify any other news services as appropriate...
50-
51-
52-
3. Author
53-
=========
40+
41+
1. FTP the tar.gz from the dist directory to to the "incoming" directory on
42+
"upload.sourceforge.net".
43+
2. Make a quick release at:
44+
http://sourceforge.net/project/admin/qrs.php?package_id=&group_id=31577
45+
3. Add a news item at:
46+
https://sourceforge.net/news/submit.php?group_id=31577
47+
using the top of doc/announcement.txt
48+
4. Send doc/announcement.txt to [email protected]
49+
5. Notify any other news services as appropriate...
50+
51+
52+
Author
53+
======
54+
5455
5556

0 commit comments

Comments
 (0)