Update of /cvsroot/spambayes/spambayes
In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv18034
Modified Files:
README-DEVEL.txt
Log Message:
Add instructions for generating OpenPGP sigs, MD5 checksums and file sizes.
Add instructions for modifying __init__.py's __version__ after the release,
based
on the discussion on [EMAIL PROTECTED]
Index: README-DEVEL.txt
===================================================================
RCS file: /cvsroot/spambayes/spambayes/README-DEVEL.txt,v
retrieving revision 1.15
retrieving revision 1.16
diff -C2 -d -r1.15 -r1.16
*** README-DEVEL.txt 25 Nov 2004 06:39:04 -0000 1.15
--- README-DEVEL.txt 30 Nov 2004 06:05:45 -0000 1.16
***************
*** 505,513 ****
o Now commit spambayes/__init__.py and tag the whole checkout - see the
existing tag names for the tag name format.
o Update the website News, Download and Windows sections.
o Update reply.txt in the website repository as needed (it specifies the
! latest version). Then let Tim, Barry, Tony, or Skip know that they need to
! update the autoresponder.
!
Then announce the release on the mailing lists and watch the bug reports
roll in. 8-)
--- 505,536 ----
o Now commit spambayes/__init__.py and tag the whole checkout - see the
existing tag names for the tag name format.
+ o Create MD5 checksums for the files, and update download.ht with these.
+ Tony uses wxChecksums (http://wxchecksums.sourceforge.net) for this,
+ but you could just do
+ >>> import md5
+ >>> print md5.md5(file("spambayes-1.0.1.exe", "rb").read()).hexdigest()
+ o Calculate the sizes of the files, and update download.ht with these.
+ o Create OpenPGP/PGP signatures for the files. Using GnuPG:
+ % gpg -sab spambayes-1.0.1.zip
+ % gpg -sab spambayes-1.0.1.tar.gz
+ % gpg -sab spambayes-1.0.1.exe
+ Put the created *.asc files in the "sigs" directory of the website.
+ o If your public key isn't already linked to on the Download page, put
+ it there.
o Update the website News, Download and Windows sections.
o Update reply.txt in the website repository as needed (it specifies the
! latest version). Then let Tim, Barry, Tony, or Skip know that they need
! to update the autoresponder.
! o Run "make install version" in the website directory to push the new
! version file, so that "Check for new version" works.
! o Add '+' to the end of spambayes/__init__.py's __version__, to
! differentiate CVS users, and check this change in. After a number of
! changes have been checked in, this can be incremented and have "a0"
! added to the end. For example, with a 1.1 release:
! [before the release process] '1.1rc1'
! [during the release process] '1.1'
! [after the release process] '1.1+'
! [later] '1.2a0'
!
Then announce the release on the mailing lists and watch the bug reports
roll in. 8-)
_______________________________________________
Spambayes-checkins mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/spambayes-checkins
