https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6247
--- Comment #35 from Justin Mason <[email protected]> 2009-12-09 03:23:05 UTC --- (In reply to comment #33) > Targeting for 3.3.0. > > Please be sure the following is done before Saturday's weekly masscheck. > > * These three rules added as nopublish so they can be tested. > * Keep the old rules for now so their performance can be compared to the new > whitelist rules, so we can possibly estimate how relevant the overlap is > between the GA scored old rules and these new rules. hi Alex -- 1. take Kevin's file, add it in your sandbox, add "tflags nopublish" to any full rule (ie not meta subrule) that doesn't yet have it 2. ensure the rules don't interfere with the existing old rules, so they can both coexist for one mass-check (3. ensure "make test" passes the basic_lint.t test ;) 4. check 'em in! by the way -- I don't know if we can safely do this in the 3.3.0 release. We need to ensure the changes to these rules don't affect FP%/FN% rates far from the levels were measured at during rescoring. (This can happen if the new rules hit diff mails, or the scores don't sufficiently compensate for FP/FNs measured in the rescore mass-check.) So even if the rules overlap sufficiently close to 100% that we can just drop 'em in as replacements, a final, pre-release step for this bug will be to measure the _new_ scores using the rescore mass-check's logfiles (with s/HABEAS_ACCREDITED_COI/RCVD_IN_RP_CERTIFIED/g etc.), determine FP/FN%, and make sure it matches the old rates (or is at least still acceptable). -- Configure bugmail: https://issues.apache.org/SpamAssassin/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.
