You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@spamassassin.apache.org by Justin Mason <jm...@jmason.org> on 2008/03/15 11:43:10 UTC
Re: 3.3.0 plans
Quanah Gibson-Mount writes:
> --On Friday, March 14, 2008 3:36 PM +0000 Justin Mason <jm...@jmason.org>
> wrote:
>
> > ok, what bugs really need to be fixed for 3.3.0? feel free to set
> > Priority on bugs on the 3.3.0 milestone. in my opinion this is the
> > only real blocker:
>
> <http://issues.apache.org/SpamAssassin/show_bug.cgi?id=4416> please please
> please. :)
unfortunately, there's no patch there, and it appears that BerkeleyDB
doesn't support upgrading of .db files anyway. unlikely to get in,
given that!
--j.
Re: 3.3.0 plans
Posted by Warren Togami <wt...@redhat.com>.
Justin Mason wrote:
> Quanah Gibson-Mount writes:
>> --On Friday, March 14, 2008 3:36 PM +0000 Justin Mason <jm...@jmason.org>
>> wrote:
>>
>>> ok, what bugs really need to be fixed for 3.3.0? feel free to set
>>> Priority on bugs on the 3.3.0 milestone. in my opinion this is the
>>> only real blocker:
>> <http://issues.apache.org/SpamAssassin/show_bug.cgi?id=4416> please please
>> please. :)
>
> unfortunately, there's no patch there, and it appears that BerkeleyDB
> doesn't support upgrading of .db files anyway. unlikely to get in,
> given that!
>
> --j.
How are the 3.3.0 plans coming along?
Warren