Justin Mason wrote:
Theo Van Dinter writes:
On Sun, Dec 31, 2006 at 09:11:08PM -0600, Larry Rosenman wrote:
Is there some process that needs to be automated to ship out the 3.1
branch rules changes via sa-update?
At the moment, we push out the updates manually. It could be automated (I
already have a script that does 95% of it, which I currently run manually,)
but I think 3.1 will probably stay manual for a while.
3.2 has automatic updates, which some of us (ok, at least me,) is still not
too sure about.
I don't know -- I think the manual process hasn't been working out too
great, myself, to be honest ;)
It seems that the manual process is missing a lint check with the
appropriate version(s) to validate the update, but that's no big deal to
fix. I don't think the automated way does it either, but should.
I think that the real issue is rule scoring... with overlapping rules
causing FPs.
This is the biggest reason why I'm not yet running 3.2 on my MXes...
there's nothing to stop rules with inappropriate scores, or rules that
overlap (all with a score of 1, probably) from being auto-promoted and
published. At least with the manual updates someone has to consciously
add those rules and their scores to the update. It doesn't prevent the
overlap problem (unless whoever does the update is really paying
attention), and the scores are still best guess, but I think it lessens
the effect somewhat.
Daryl
