https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6644
--- Comment #3 from Daryl C. W. O'Shea <[email protected]> 2011-08-05 03:28:35 UTC --- Hrm, things probably changed when we broke the rules out of core completely and made sa-update required. You used to get rules generated via make from the bleeding edge sandboxes (IIRC... it's literally been years now). I think the way I'm leaning right now (too avoid inadvertent breakage) is to create another channel for trunk that provides the same update we're providing for the stable branches now. That way the nightly trunk updates continue to work the way they work now (even if we don't have a large enough mass-check corpus to generate scores) and the new channel will be available to those who set sa-update to use it. So (notes to myself): 1. add DNS records like 3.4.0.stable.updates.spamassassin.org. 2. update the stable update script to build trunk and then lint the update using trunk and then update the "3.4.0.stable" update version file. 3. profit. #2 should be doable by invoking the guts of the stable version testing loop one more time with a "3.4.0.stable" token rather than a "3.3.x" token. #3 still eludes me. -- Configure bugmail: https://issues.apache.org/SpamAssassin/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.
