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/12/21 11:04:29 UTC
Re: 3.2.4 schedule
Warren Togami writes:
> Hi folks,
>
> RHEL5 currently has spamassassin-3.1.9.
>
> I've been handed an engineering deadline of mid-January to spin a new
> spamassassin package for a future update release of RHEL5. I really
> hope 3.2.4 can be released before that time so I'm not forced to use 3.2.3.
>
> Will 3.2.4 by mid-January likely be feasible, or should I plan on 3.2.3
> with select backports?
It's entirely feasible; technically you could cut a release from the
SVN branch right now, and it'll be good enough to call 3.2.4 (more or
less), IMO.
I'd prefer to get a *real* release out, though. It's up to the committers
as to whether we can close out the remaining bug(s) and get the votes
together for a release.
These just need votes:
5696 min P5 NEW needs 1 votes for 3.2 [review]
cut regexp base strings at Unicode high codepoints
4179 maj P3 NEW needs 2 votes for 3.2 [review]
user rules are not unique to each user
5606 min P5 NEW needs 2 votes for 3.2 [review]
spamc/spamd tests fail due to broken -x logic
5637 nor P5 NEW needs 2 votes for 3.2 [review]
bayes_file_mode is handled incorrectly when creating bayes.mutex
The one bug that needs code is:
5751 maj P2 NEW sa-update leaves rules
broken
but there's still discussion as to how/why/whether to do anything, there,
so it may not make it.
The others in the 3.2.4 target list, in my opinion, can be deferred.
What do you think, guys?
--j.
Re: 3.2.4 schedule
Posted by Doc Schneider <ma...@maddoc.net>.
Sidney Markowitz wrote:
> Justin Mason wrote, On 21/12/07 11:04 PM:
>> The one bug that needs code is:
>>
>> 5751 maj P2 NEW sa-update leaves rules
>> broken
>>
>> but there's still discussion as to how/why/whether to do anything, there,
>> so it may not make it.
>>
>>
>> The others in the 3.2.4 target list, in my opinion, can be deferred.
>>
>> What do you think, guys?
>
> We're now down to 5 bugs in review that need just one more vote:
>
> 4179 [review] user rules are not unique to each user
> 5637 [review] bayes_file_mode is handled incorrectly when crea...
> 5662 [review] DKIM plugin overhaul - whitelisting and terminology
> 5606 [review] spamc/spamd tests fail due to broken -x logic
> 5696 [review] cut regexp base strings at Unicode high codepoints
>
> and one in review that needs two votes:
>
> 5612 [review] DB_File: infinite loop causing 100% cpu usage wh...
>
> And only 5 others labeled for 3.2.4 target. I would like to see a resolution of bug 5751
> in time for a 3.2.4 release (but would not make it a blocker), and I agree with Daryl
> about bug 5673 about handling whitespace in "ALL" headers should get patch 4145 applied
> for 3.2.4 and then keep an open bug for further discussion. The remaining three could be
> deferred.
>
> -- sidney
I reviewed all these and they are good to go. I voted on them.
Sorry I've been lax in reviewing things but my $dayjob is keeping me
extremely busy.
I'll let one of the other PMC members call and voted to cut a rc or pre
3.2.4.
--
-Doc
Penguins: Do it on the ice.
8:44am up 4 days, 16:55, 17 users, load average: 0.18, 0.30, 0.37
SARE HQ http://www.rulesemporium.com/
Re: 3.2.4 schedule
Posted by Sidney Markowitz <si...@sidney.com>.
Justin Mason wrote, On 21/12/07 11:04 PM:
> The one bug that needs code is:
>
> 5751 maj P2 NEW sa-update leaves rules
> broken
>
> but there's still discussion as to how/why/whether to do anything, there,
> so it may not make it.
>
>
> The others in the 3.2.4 target list, in my opinion, can be deferred.
>
> What do you think, guys?
We're now down to 5 bugs in review that need just one more vote:
4179 [review] user rules are not unique to each user
5637 [review] bayes_file_mode is handled incorrectly when crea...
5662 [review] DKIM plugin overhaul - whitelisting and terminology
5606 [review] spamc/spamd tests fail due to broken -x logic
5696 [review] cut regexp base strings at Unicode high codepoints
and one in review that needs two votes:
5612 [review] DB_File: infinite loop causing 100% cpu usage wh...
And only 5 others labeled for 3.2.4 target. I would like to see a resolution of bug 5751
in time for a 3.2.4 release (but would not make it a blocker), and I agree with Daryl
about bug 5673 about handling whitespace in "ALL" headers should get patch 4145 applied
for 3.2.4 and then keep an open bug for further discussion. The remaining three could be
deferred.
-- sidney