Okay, here's my proposal for official daily updates for 3.0:
Basic design:
- updates are a set of files that are used to supplement official
releases beginning with 3.0.0 -- initially, these will be .cf files
beginning with a number from 80 to 89.
- updates are published for each individual release: 3.0.0, 3.0.1, etc.
- it is expected that most updates will be equivalent across a
particular set of releases using the same rule base (3.0.x will all be
linked, etc.)
- updates will be pulled or pushed (TBD) about once a day initially
- all updates will be tested using a nightly corpus test system and
will eventually be scored using the perceptron
New rules:
- primary rule sources:
* 70_testing.cf rules from HEAD
* user submissions
- target missed spam
- checked into SVN regularly
- an SVN revision is only released as an update after passing a QA
process including: lint, positive corpus results, and a visual
inspection by a developer - actual updates will probably not be
daily at all initially, but daily is the target
Update software:
- worry about distribution last, worry about generation and
maintenance of rules first
- possible protocols: rsync and http
- apache.org mirror system?
- daemon vs. cron job
- pull vs. push
Daniel
