summary | shortlog | log | commit | commitdiff | tree
raw | patch | inline | side by side (parent: ca1a117)
raw | patch | inline | side by side (parent: ca1a117)
author | richard <richard@57a73879-2fb5-44c3-a270-3262357dd7e2> | |
Tue, 8 Jan 2002 00:00:56 +0000 (00:00 +0000) | ||
committer | richard <richard@57a73879-2fb5-44c3-a270-3262357dd7e2> | |
Tue, 8 Jan 2002 00:00:56 +0000 (00:00 +0000) |
git-svn-id: http://svn.roundup-tracker.org/svnroot/roundup/trunk@505 57a73879-2fb5-44c3-a270-3262357dd7e2
BUILD.txt | patch | blob | history | |
doc/announcement.txt | patch | blob | history |
diff --git a/BUILD.txt b/BUILD.txt
index 6cc6cd1f60eacb1bfa96faca90704adea61bb7a9..25212621a5eb50e3877da480bd86ce4faa6b9e3f 100644 (file)
--- a/BUILD.txt
+++ b/BUILD.txt
This means that we only need to ever build source releases. This is done by
running:
- 0. python setup.py clean --all
- 1. Edit setup.py to ensure that all information therein (version, contact
+ 0. Edit setup.py and doc/announcement.txt to reflect the new version and
+ appropriate announcments.
+ 1. python setup.py clean --all
+ 2. Edit setup.py to ensure that all information therein (version, contact
information etc) is correct.
- 2. python setup.py sdist --manifest-only
- 3. Check the MANIFEST to make sure that any new files are included. If
+ 3. python setup.py sdist --manifest-only
+ 4. Check the MANIFEST to make sure that any new files are included. If
they are not, edit MANIFEST.in to include them. "Documentation" for
MANIFEST.in may be found in disutils.filelist._parse_template_line.
- 4. python setup.py sdist
+ 5. python setup.py sdist
(if you find sdist a little verbose, add "--quiet" to the end of the
command)
- 5. FTP the tar.gz from the dist directory to to the "incoming" directory on
- "upload.sourceforge.net".
- 6. Make a quick release at:
- http://sourceforge.net/project/admin/qrs.php?package_id=&group_id=31577
So, those commands in a nice, cut'n'pasteable form :)
python setup.py clean --all
python setup.py sdist --quiet
-2. Author
+2. Distributing Releases
+========================
+
+Once a release is built, follow these steps:
+ 1. FTP the tar.gz from the dist directory to to the "incoming" directory on
+ "upload.sourceforge.net".
+ 2. 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...
+
+
+3. Author
=========
richard@users.sourceforge.net
diff --git a/doc/announcement.txt b/doc/announcement.txt
index cdba40605b5220c517128612d8ccb839d52170f8..45713323cd4ac5616360c78752c64100402f39a9 100644 (file)
--- a/doc/announcement.txt
+++ b/doc/announcement.txt
- Roundup 0.3.1b1 - an issue tracking system
+ Roundup 0.4.0b1 - an issue tracking system
If you are upgrading from pre-0.3.0, please read MIGRATION.txt.