@@ -23,10 +23,6 @@ running:
2323 command)
24248. unpack the new dist file in /tmp then a) run_test.py and b) demo.py
2525 with all available Python versions.
26- 9. generate gpg signature with "gpg -a --detach-sign" and upload to
27- Sourceforge.
28- 10. PyPI registration
29- 11. tag the CVS for the release, eg. "cvs tag -R release-0-6-3"
3026
3127So, those commands in a nice, cut'n'pasteable form::
3228
@@ -41,19 +37,14 @@ Distributing Releases
4137
4238Once a release is built, follow these steps:
4339
44- 1. FTP the tar.gz from the dist directory to to the "incoming" directory on
40+ 1. generate gpg signature with "gpg -a --detach-sign" and upload to
41+ Sourceforge.
42+ 2. tag the CVS for the release, eg. "cvs tag -R release-0-6-3"
43+ 3. FTP the tar.gz from the dist directory to to the "incoming" directory on
4544 "upload.sourceforge.net".
46- 2 . Make a quick release at:
45+ 4 . Make a quick release at:
4746 http://sourceforge.net/project/admin/qrs.php?package_id=&group_id=31577
48- 3. Add a news item at:
49- https://sourceforge.net/news/submit.php?group_id=31577
50- using the top of doc/announcement.txt
51- 4. Send doc/announcement.txt to
[email protected] 52- 5. Notify any other news services as appropriate...
53-
54-
55- Author
56- ======
57-
58- 47+ 5. PyPI registration
48+ 6. Send doc/announcement.txt to
[email protected] 49+ 7. Notify any other news services as appropriate...
5950
0 commit comments