https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6400
--- Comment #30 from Kevin A. McGrail <[email protected]> 2011-12-07 16:06:26 UTC --- "The policy has been clear for a long time now, we add network rules only at major version releases" I am unfortunately unaware of any such policy. In fact, since I've sort of spearheaded trying to write the policy for RBLs and their inclusion, I can tell you definitively that there is no such policy. However, network rules have caused angst and need to be treated with care on a case-by-case basis. That we can all agree on. In this particular case, I believe it's a good list and worthy of inclusion by default. If it makes people have less anxiety to release it wrapped in a 3.4.0 version block check, fine. If people like my idea to have a disable_rules channel and publish this as-is with a score 0.0 rules channel to disable the rule, I'm cool with that too. But I would like to see more focus on tickets that are holding up 3.4.0 and compromise on those tickets even if we have some 3.4.1 targets, etc. And overall, our release policy is that we release things for the MAJORITY of users NOT for the hyper-minority that is processing 30 million emails a day and can't afford an extra DNS query, etc. My expectation is that people running the uber-systems have people on the dev list, etc. and would know how to add the score 0's NOW prior to the updates channel pushing out the rule. Regards, KAM -- Configure bugmail: https://issues.apache.org/SpamAssassin/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.
