You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@spamassassin.apache.org by Justin Mason <jm...@jmason.org> on 2005/09/07 03:56:04 UTC
Re: ANNOUNCE: SpamAssassin 3.1.0-rc2 release candidate available!
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Loren Wilton writes:
> It isn't fixed in rc2.
>
> You only posted that analysis 2 days before the rc2 release, and the tarball
> had already been cut at the time you posted the message. (It takes a day or
> two between release cutoff and the release showing up, since it needs to be
> tested before the announcement.)
>
> Furthermore, you only posted the notice here in the users group where it
> could easily be missed by the SA devs. The proper thing to do is open a bug
> in Bugzilla on this subject, and include the info that you posted here.
>
> FWIW, the change that is causing the problems was a deliberate change to
> work around another problem in another tool. So the fix isn't likely to be
> as simple as backing out that change, since that would just bring the
> previous bug back.
Following up on this -- yes, Loren has nailed it here. It would be
best to open this as a bug in bugzilla for further followup.
- --j. (just back from a week's vacation)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)
Comment: Exmh CVS
iD8DBQFDHki0MJF5cimLx9ARAmrQAJsESlKBkU7bdWHCJMWGRMn+7kwfzACdH2eD
QCjLAPOEV25EZKwZUJmG+ZQ=
=Y2Xl
-----END PGP SIGNATURE-----