A few more updates
This commit is contained in:
parent
0b3095ed1b
commit
6256bf9526
18
pep-0101.txt
18
pep-0101.txt
|
@ -275,16 +275,24 @@ How to Make A Release
|
|||
% make test
|
||||
(Do all the expected tests pass?)
|
||||
|
||||
If you're feeling lucky and have some time to kill, run the full
|
||||
test suite:
|
||||
|
||||
% make TESTOPTS='-u all' test
|
||||
|
||||
If the tests pass, then you can feel good that the tarball is
|
||||
fine. If some of the tests fail, or anything else about the
|
||||
freshly unpacked directory looks weird, you better stop now and
|
||||
figure out what the problem is.
|
||||
|
||||
___ Upload the tgz file to creosote.python.org. Tim will have
|
||||
already uploaded the exe file to creosote, but if not, you'll
|
||||
need to do that too. These steps can take a long time depending
|
||||
on your network bandwidth. scp both files from your own machine
|
||||
to creosote.
|
||||
___ Upload the tgz file to creosote.python.org using scp.
|
||||
|
||||
___ Tim has been having trouble uploading to creosote, so he will
|
||||
usually put the file on SF, giving you the file name and the md5
|
||||
checksum. It's best to do a wget from creosote to SF, but
|
||||
calculating the URL can be not-fun. You can usually get the URL
|
||||
from the file download page, if you start the download and then
|
||||
immediately cancel it.
|
||||
|
||||
___ While you're waiting, you can start twiddling the web pages to
|
||||
include the announcement.
|
||||
|
|
Loading…
Reference in New Issue