https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6400
--- Comment #24 from Karsten Bräckelmann <[email protected]> 2011-12-05 23:37:44 UTC --- (In reply to comment #23) > > What's unsubstantiated is your claim that I and my quote would have been the > > reason for not yet including Mailspike. There are NO votes by PMC members or > > committers. That's what matters and changes the game, not a single post on a > > mailing list. > > Kevin's comment 7 should count as a +1. And I worry that others aren't voting > because they believe there was previous consensus to only add DNSBLs at > releases, which I question. I'd argue "Let's just make the rules 3.4 only" in comment 13 would imply a -1 by KAM. Imply, neither one is a vote. If others actually "believe there was previous consensus", they might recall the same discussions I do. > > Thus the need for clearly communicating any such changes. > > I agree with that. I think being unwilling to make the change to existing > releases takes it too far. As you just said, these are EXISTING releases. sa-update can even introduce new plugins, code. Disabled by default in the client. Because that would take it too far, in any but tightly managed site internal processes. Similarly, in my not so humble opinion, introducing new DNSBLs via sa-update to existing releases would take it too far. Anyway, for the formal part: +1 for adding Mailspike to 3.4 -1 on adding any new DNSBL via sa-update to existing releases, but strictly limit this on actual releases with README and release notes -- Configure bugmail: https://issues.apache.org/SpamAssassin/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.
