Re: [VOTE] SpamAssassin 3.1.7 release

[Justin Mason <jm...@jmason.org>]

Thomas Schulz writes:
> > Hi --
> > 
> > new tarballs!  Please check 'em out and vote at:
> > 
> > http://people.apache.org/~jm/devel/
> > 
> > by the way: 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:
> 
> Should the release announcement include the change section from the
> 3.1.6 release (labeled as such) for the benefit of those skipping
> the 3.1.6 release in favor of the 3.1.7 release?

Since we have never done that before, I would say not -- no point
starting it now ;)

--j.

> > To: users, dev, announce
> > Subject: ANNOUNCE: Apache SpamAssassin 3.1.7 available!
> > 
> > Apache SpamAssassin 3.1.7 is now available!  This is a maintenance
> > release of the 3.1.x branch.
> > 
> > Downloads are available from:
> >    http://spamassassin.apache.org/downloads.cgi?update=200610010200
> >    [DOS: update the date string appropriately upon release]
> > 
> > The release file will also be available via CPAN in the near future.
> > 
> > md5sum of archive files:
> >   77242e45baa7e2b418e4d3f22a86a69e  Mail-SpamAssassin-3.1.7.tar.bz2
> >   4b342c63949d47f3ce56b3fc1c8881c1  Mail-SpamAssassin-3.1.7.tar.gz
> >   b62794d50e0921dbb9f5211a65e4dc0e  Mail-SpamAssassin-3.1.7.zip
> > 
> > sha1sum of archive files:
> >   6660dd3aa87f4ddd3ba9b19cf232dd006c6e8219  Mail-SpamAssassin-3.1.7.tar.bz2
> >   3d31eff0eb9a158fab308958d65cdca81b8944bc  Mail-SpamAssassin-3.1.7.tar.gz
> >   7a882fcf4e253c9c020278f126b783ab41fe31d5  Mail-SpamAssassin-3.1.7.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 <re...@spamassassin.org>
> >       Key fingerprint = 26C9 00A4 6DD4 0CD5 AD24  F6D7 DEE0 1987 265F A05B
> > 
> > 3.1.7 is a "quick-fix" release; it contains only a fix for one bug,
> > introduced accidentally in 3.1.6:
> > 
> > - bug 5119: if admins had set rule scores in the site configuration in
> >   /etc, sa-update would fail.  Back out this change
> > 
> > 
> 
> Tom schulz
> Applied Dynamics Intl.
> schulz@adi.com

Re: Cumulative changes

[Sidney Markowitz <si...@sidney.com>]

On 10/10/06 1:09 PM, Kenneth Porter wrote:
> --On Monday, October 09, 2006 9:37 PM +0100 Justin Mason <jm...@jmason.org> 
> Agreed, but it would be nice if there was a link in the release 
> announcement to the Changes file (or to the previous release announcement). 
> This could be to the file in the Subversion tag directory.
> 
> I had to jump through the wiki to review the svn URL and finally got to:
> 
> <http://svn.apache.org/repos/asf/spamassassin/
> tags/spamassassin_release_3_1_7/Changes>


I agree that making a link to the Changes file easy to find would be a
good idea, whether it is done by adding one sentence to the release
announcement, or at least adding it to the SpamAssassin home page or to
the download page.

http://svn.apache.org/repos/asf/spamassassin/branches/3.1/Changes is a
better URL, as it will continue to work until we release 3.2.

I propose that starting with the 3.1.7 release we add that link to the
downloads page on http://spamassassin.apache.org/downloads.cgi

> Something that's not clear to me is where the version boundaries are in the 
> Changes file. I can't quickly tell where 3.1.6 ends and 3.1.7 begins.

Each release starts with a change such as "3.1.6 devel cycle started"
and ends with "preparing to release 3.1.6". The "preparing to release
3.1.7" hasn't been checked in yet because it has not been released.

 -- Sidney Markowitz
    http://www.sidney.com

Cumulative changes (was: [VOTE] SpamAssassin 3.1.7 release)

[Kenneth Porter <sh...@sewingwitch.com>]

--On Monday, October 09, 2006 9:37 PM +0100 Justin Mason <jm...@jmason.org> 
wrote:

> Since we have never done that before, I would say not -- no point
> starting it now ;)

Agreed, but it would be nice if there was a link in the release 
announcement to the Changes file (or to the previous release announcement). 
This could be to the file in the Subversion tag directory.

I had to jump through the wiki to review the svn URL and finally got to:

<http://svn.apache.org/repos/asf/spamassassin/
tags/spamassassin_release_3_1_7/Changes>

Something that's not clear to me is where the version boundaries are in the 
Changes file. I can't quickly tell where 3.1.6 ends and 3.1.7 begins.

Would it be possible to generate a different file that has the cumulative 
notes from the release announcements, visibly separated at the version 
boundaries? Someone running, say, 3.1.4 could quickly determine how much 
will change when they upgrade to the latest release.

(I'm upgrading some 3.1.4 systems to 3.1.6 and commented out the custom 
scores until 3.1.7 is available.)