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 2007/04/10 20:20:45 UTC

3.2.0 schedule

> > does this have to be done for 3.2.0? ;)
> 
> Ideally, but certainly not a show stopper (we need to get 3.2 released
> soon!). 

Definitely!  On this count, I think we should do another RC tomorrow or
the day after; http://issues.apache.org/SpamAssassin/show_bug.cgi?id=5313
is about the only relatively-serious issue, and I suspect that may
actually be working ok, modulo some serious perl-interpreter-level bogons
for one reporter.

--j.

Re: 3.2.0 schedule

Posted by "Daryl C. W. O'Shea" <sp...@dostech.ca>.

Justin Mason wrote:
>>> does this have to be done for 3.2.0? ;)
>> Ideally, but certainly not a show stopper (we need to get 3.2 released
>> soon!). 
> 
> Definitely!  On this count, I think we should do another RC tomorrow or
> the day after; http://issues.apache.org/SpamAssassin/show_bug.cgi?id=5313
> is about the only relatively-serious issue, and I suspect that may
> actually be working ok, modulo some serious perl-interpreter-level bogons
> for one reporter.

If you're satisfied with the feedback on 5313 I think we're ready to go 
today.  I've taken care of the other two bugs (5384 and 5410).

Daryl