You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@spamassassin.apache.org by jm...@apache.org on 2008/01/08 14:42:22 UTC
svn commit: r609981 - /spamassassin/trunk/build/README
Author: jm
Date: Tue Jan 8 05:42:21 2008
New Revision: 609981
URL: http://svn.apache.org/viewvc?rev=609981&view=rev
Log:
sync up with 3.2.x build instructions
Modified:
spamassassin/trunk/build/README
Modified: spamassassin/trunk/build/README
URL: http://svn.apache.org/viewvc/spamassassin/trunk/build/README?rev=609981&r1=609980&r2=609981&view=diff
==============================================================================
--- spamassassin/trunk/build/README (original)
+++ spamassassin/trunk/build/README Tue Jan 8 05:42:21 2008
@@ -123,7 +123,7 @@
svn commit -m "preparing to release X.Y.Z"
(If you are privately preparing a security release, and don't wish to
- perform commits to public SVN repos, you can omit this step until
+ perform commits to public SVN repos, you can defer this step until
later.)
- SVN tag the release files. This is done using "svn copy".
@@ -156,7 +156,7 @@
base of the tag release.
(If you are privately preparing a security release, and don't wish to
- perform commits to public SVN repos, you can omit this step until
+ perform commits to public SVN repos, you can defer this step until
later.)
@@ -188,11 +188,7 @@
- Write the release announcement mail! This is a simple matter of copying
the previous release's announcement, updating the version numbers and
links, fixing the MD5 and SHA1 checksums in this mail, and summarising
- the important changes from the Changes file.
-
- Warning: you must send this using a "From:" address @apache.org,
- otherwise it will be silently discarded at the ASF instead of being
- delivered to the announce list.
+ the important changes from the Changes file.
cp build/announcements/3.1.7.txt build/announcements/3.1.8.txt
svn add !$
@@ -203,7 +199,14 @@
of the website, but included in the vote mail) and request a vote on the
development mailing list to make the release. Post the URL,
md5sums/sha1sums, and proposed release announcement mail to the dev
- list.
+ list. The default location -- ~/public_html/devel/ , or
+ http://people.apache.org/~jm/devel/ , qualifies as "discreet".
+
+ While doing this, also upload a copy of the proposed release
+ announcement to the website:
+
+ version=3.2.4
+ cp build/announcements/$version.txt ~/public_html/devel/PROPOSED-$version.txt
Pre-releases and RCs require just lazy consensus -- ie. no objections.
@@ -266,12 +269,18 @@
make it clear that this is an unofficial "test build" by placing it
in your public_html dir:
- http://people.apache.org/~jm/devel/
+ http://people.apache.org/~jm/rc/
+
+ this command will do it:
+
+ version=X.Y.Z
+ cp -p ~/public_html/devel/Mail-SpamAssassin-$version.* \
+ ~/public_html/rc/
(for full release builds) copy the tarballs to www.apache.org/dist:
version=X.Y.Z
- cp -p ~/site/released/Mail-SpamAssassin-$version.* \
+ cp -p ~/public_html/devel/Mail-SpamAssassin-$version.* \
/www/www.apache.org/dist/spamassassin/source
cd /www/www.apache.org/dist/spamassassin
@@ -287,7 +296,7 @@
cd /www/www.apache.org/dist/spamassassin
prev=X.Y.notZ
- rm -f source/Mail-SpamAssassin-$prev.*
+ rm -f source/Mail-SpamAssassin-$prev.* Mail-SpamAssassin-$prev.*
rm -f binaries/*/Mail-SpamAssassin-$prev.*
(Archive copies are automatically kept on archive.apache.org/dist/ .)
@@ -304,6 +313,7 @@
- rebuild the SpamAssassin website with webmake:
+ PATH=$HOME/sabuildtools/perl584/bin:$HOME/sabuildtools/bin:$PATH
cd /www/spamassassin.apache.org
webmake -F
@@ -333,10 +343,8 @@
- Release a new rules update matching the released code:
ssh spamassassin.zones.apache.org
- sudo -H -u updatesd \
- /home/updatesd/svn/spamassassin/build/mkupdates/run_nightly
- sudo -H -u updatesd \
- /home/updatesd/svn/spamassassin/build/mkupdates/run_part2
+ cd /home/updatesd/svn/spamassassin/build/mkupdates
+ sudo -H -u updatesd ./update-rules 3.2
- update the tag used to point to "current release":