+1. looks good from here! --j.
Theo Van Dinter writes: > Hi there, > > I have readied a new set of 3.1.4 files. They are available at: > > http://people.apache.org/~felicity/314/ > > Please test out these files and vote as to whether or not to release them as > 3.1.4. Thanks. :) > > BTW: per ASF policies, only PMC member votes are binding for a release, > but we encourage everyone to download, test, and report any issues! > > > My Vote: +1 > > > > BTW: my proposed release announcement is as follows: > > To: users, dev, announce > Subject: ANNOUNCE: Apache SpamAssassin 3.1.4 available! > > Apache SpamAssassin 3.1.4 is now available! This is a maintainance > release of the 3.1.x branch. > > Downloads are available from: > http://spamassassin.apache.org/downloads.cgi?update=200607261100 > [TVD: update the date string appropriately upon release] > > The release file will also be available via CPAN in the near future. > > md5sum of archive files: > c620b0a20791999a8f8091b0888e0195 Mail-SpamAssassin-3.1.4.tar.bz2 > 6259d1b1c5ce34c37596fc262c0b9663 Mail-SpamAssassin-3.1.4.tar.gz > d5b0c02b77b6936beac056bdfa846bbd Mail-SpamAssassin-3.1.4.zip > > sha1sum of archive files: > c764e94a4666c9bcb30b0540183b71e8edef6bb9 Mail-SpamAssassin-3.1.4.tar.bz2 > df88c2e27c1c8ede60a1b967443a3b16cc74cd9f Mail-SpamAssassin-3.1.4.tar.gz > c524dd619e36a13e86bb14091039613c34b187b4 Mail-SpamAssassin-3.1.4.zip > > The release files also have a .asc accompanying them. The file serves > as an external GPG signature for the given release file. The signing > key is available via the wwwkeys.pgp.net key server, as well as > http://spamassassin.apache.org/released/GPG-SIGNING-KEY > > The key information is: > > pub 1024D/265FA05B 2003-06-09 SpamAssassin Signing Key <[EMAIL PROTECTED]> > Key fingerprint = 26C9 00A4 6DD4 0CD5 AD24 F6D7 DEE0 1987 265F A05B > > 3.1.4 includes a large number of bug fixes and documentation updates. > Here is an abbreviated changelog (since 3.1.3) for major updates (see > the Changes file for a complete list): > > - bug 4941: if the first sa-update run failed and wasn't re-run to successful > completion, the local state directory would exist, and therefore SA sees no > rules. now, wait as long as possible to create the directory, and try to > remove it on failure. > - bug 4997: increase module version requirements for Archive::Tar to 1.23 and > IO::Zlib to 1.04 > - bug 4966: fix major BSMTP bug, which rendered SA unusable with exim4 when > BSMTP is used. > - bug 4899: Windows had issues with single quotes around filenames so certain > things like pyzor, etc, wouldn't function. > - bug 4958: sa-update should work on Windows > - bug 4908: gtube.t test failed in non-english locales > - bug 4488: deal with potential memory leak due to Bayes and BayesStore > circular references > - bug 4862: update macro values in update channels (ie: @@CONTACT_ADDRESS@@) > > -- > Randomly Generated Tagline: > "Ford had his own code of ethics. It wasn't much of one, > but it was his and he stuck by it, more or less. One rule > he made was never to buy his own drinks. He wasn't sure if > that counted as an ethic, but you have to go with what > you've got. "
