...
- Weekly mass-check
- DONE: all rules, with --net
- DONE: all rules, with --net
- Nightly mass-check: web-based user interface for the following data:
- DONE: freqs for all rules
- DONE: freqs collated across all users' corpora, or individually
- DONE: overlaps between rules
- DONE: historical rule hits data?
- TODO: rule-by-rule comparative performance figures?
- TODO: historical rule hits data?TODO: promotion criteria as defined in RulesProjPromotion, so rules that can be promoted can be identified at a glance
...
- TODO: the RulesProjBuildBot system, comprising these tasks:
- DONE: set up new buildbot master - http://buildbot.spamassassin.org:8011/
- DONE: set up user in zone
- DONE: set up new buildbot slave
- DONE: set up chroot jail
- DONE: get mass-check running in chroot
- DONE: copy in corpus
- DONE: set up additional slaves for additional corpora
- DONE: write mass-check wrapper script to:
- DONE: mass-check that corpus, using rules from .../rulesrc/sandbox/ only
- DONE: implement strict ulimits
- DONE: write mass-check-completed script to:
- DONE: output freqs so it's visible through the Buildbot UI
- write mail-handling script to extract mail-submitted rule attachments