You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@spamassassin.apache.org by Warren Togami <wt...@redhat.com> on 2009/08/24 18:33:16 UTC

3.3.0 status?

https://issues.apache.org/SpamAssassin/buglist.cgi?query_format=advanced&target_milestone=3.3.0&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED

Which bugs will need to be fixed before 3.3.0?

Time for some new test scores since we have another weekly --net data set?

Warren Togami
wtogami@redhat.com

Re: 3.3.0 status?

Posted by Justin Mason <jm...@jmason.org>.

I was hoping someone would figure out why set 0 scores are so crappy
-- 20% FN rate :(

it could just be that spam has gotten much better, but historically
that's generally indicated a problem with the GA or the logs.  I
haven't had time to look myself yet.

after that, I think we can go ahead and schedule the mass-checks to start.

--j.

On Mon, Aug 24, 2009 at 17:33, Warren Togami<wt...@redhat.com> wrote:
> https://issues.apache.org/SpamAssassin/buglist.cgi?query_format=advanced&target_milestone=3.3.0&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED
>
> Which bugs will need to be fixed before 3.3.0?
>
> Time for some new test scores since we have another weekly --net data set?
>
> Warren Togami
> wtogami@redhat.com
>
>

-- 
--j.