Theo Van Dinter wrote:
On Tue, Oct 03, 2006 at 07:09:48PM -0400, Daryl C. W. O'Shea wrote:
Cool, thanks. BTW, we need to put out a new 3.1 rule update before
3.1.6 is released (due to eval test code being removed). I'm assuming
you need to do that (or are you automatically rsyncing to your box?).
I'm not quite sure how that's setup as I don't have an account on the
zone box.
So right now what happens is that the updates get written on the zone box,
and I have an rsync cronjob running every 15m to copy it to my machine
which serves it out. I put up a wiki doc to explain how to do the manual
(3.1) updates (http://wiki.apache.org/spamassassin/ManualRuleUpdates),
but you would need an account on the zones machine. We ought to add that
in as a step to be done -- I'm not sure if we want to restrict that to
PMC or committer or what. :|
Yeah, I saw the wiki page (pretty similar to what I'm doing myself), I
just wasn't sure how updates were handled on your mirror since nobody
else has done an update yet.
As for who should have access to the zones box... (sort of related) I'm
a little concerned about what kind of oversight we are required (by the
ASF) to have over rule updates. If we need three PMC +1s for a release,
what do we need for rule updates? I suppose you could argue that
they're just config files, but the rules are a pretty big component of
the product. In any case, there has only been 2 commits (one of which
was the addition of a "1;") in the last 6+ months from all 5 committers
combined, so it's definitely not a pressing issue.
Anyway, the 3.1.6 queue is empty now, except for bug 5044. I just want
to make sure that you weren't reserving exit code 2 for anything before
I commit the sa-update lint changes.
Daryl
