https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6281
Summary: Speeding up the pipeline from rules update to a final
user
Product: Spamassassin
Version: 3.3.0
Platform: All
OS/Version: All
Status: NEW
Severity: normal
Priority: P5
Component: sa-update
AssignedTo: [email protected]
ReportedBy: [email protected]
The New Year's Y2K10 blunder showed the importance of having a quick way to
update people's rules through sa-update. Even after the event, which polished
somewhat the rusty ways of the pipeline, the second incident (Bug 6279)
demonstrated there is still a lot of room for improvement, and plenty of
chances that things break - this one took about 15 hours to propagate
rules to the last DNS server.
Let's see if we can improve some of the steps involved, and avoid some
potential or real traps.
Here are some steps of a pipeline:
- commit updated rule (human response time, SVN availability, ..??..);
- propagate rules to mirrors (I'm not familiar how this currently works);
- propagate changed rule ID to a master DNS server for spamassassin.org,
increment its zone sequence number, reload the zone;
- propagate zone update to ALL slave DNS servers;
- let users run sa-update - periodically or manually for intervention
--
Configure bugmail:
https://issues.apache.org/SpamAssassin/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
