Mercurial > p > roundup > code
changeset 2221:7852c5bc75f6 0.7.0b3
*** empty log message ***
| author | Richard Jones <richard@users.sourceforge.net> |
|---|---|
| date | Sun, 18 Apr 2004 06:23:03 +0000 |
| parents | 34df21044229 |
| children | 9b447ac40be3 |
| files | BUILD.txt |
| diffstat | 1 files changed, 8 insertions(+), 17 deletions(-) [+] |
line wrap: on
line diff
--- a/BUILD.txt Sun Apr 18 06:21:20 2004 +0000 +++ b/BUILD.txt Sun Apr 18 06:23:03 2004 +0000 @@ -23,10 +23,6 @@ command) 8. unpack the new dist file in /tmp then a) run_test.py and b) demo.py with all available Python versions. -9. generate gpg signature with "gpg -a --detach-sign" and upload to - Sourceforge. -10. PyPI registration -11. tag the CVS for the release, eg. "cvs tag -R release-0-6-3" So, those commands in a nice, cut'n'pasteable form:: @@ -41,19 +37,14 @@ Once a release is built, follow these steps: -1. FTP the tar.gz from the dist directory to to the "incoming" directory on +1. generate gpg signature with "gpg -a --detach-sign" and upload to + Sourceforge. +2. tag the CVS for the release, eg. "cvs tag -R release-0-6-3" +3. FTP the tar.gz from the dist directory to to the "incoming" directory on "upload.sourceforge.net". -2. Make a quick release at: +4. 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... +5. PyPI registration +6. Send doc/announcement.txt to python-announce@python.org +7. Notify any other news services as appropriate... - -Author -====== - -richard@users.sourceforge.net -