> > The differences between 3.2.x versions are code fixes. There
> > is no difference in rules, when using sa-update.
> >
> > While it is possible to publish per micro version updates,
> > this is not necessary and thus not used for 3.2.x. They all
> > share the very same rules and updates.
>
> Karsten,
>
> what about when we consider and migrate from 3.2.5 to 3.3.x once it is
> officially released ?
Smart move asking one of the more recent additions to the dev team... ;)
> will there be info from the SA Team about what rules have changes and what
> "mods" that have come from the list that most of us are using in 3.2.5 that
> should be double checked for and removed in terms of rules and otherwise?
>
> anything you can clue us in on before hand?
Well, I joined the SA dev team about a year ago, after 3.2.0 has been
released. Since I am going entirely from memory and observations as a
user, take this with a grain of salt.
However, from what I recall when 3.2.0 was released, there was no
detailed list of modified, added or dropped rules. Frankly, it is my
understanding this would be impossible to do in a way for a human to
grok anyway. Rules have been evolving during the entire time, and the GA
run decides which rules to incorporate and about their scores.
That said, I seem to recall that at least published SARE rule-sets have
been mentioned to be added to stock and thus obsoleted.
Speaking about rules posted to the list: Those often will be changed
slightly in the sandbox after the initial post. Let alone some rules
being posted in various versions on this list -- which one do you run?
As with all custom rules and scores, it's the admin's duty to check they
are reasonable. After all, a new stock rule not posted here before might
overlap with your home-brew code, too.
Also, there's no communications channel announcing sa-update rule
updates in detail.
guenther
--
char *t="\10pse\0r\0dtu...@ghno\x4e\xc8\x79\xf4\xab\x51\x8a\x10\xf4\xf4\xc4";
main(){ char h,m=h=*t++,*x=t+2*h,c,i,l=*x,s=0; for (i=0;i<l;i++){ i%8? c<<=1:
(c=*++x); c&128 && (s+=h); if (!(h>>=1)||!t[s+h]){ putchar(t[s]);h=m;s=0; }}}
