On Tue, Jan 02, 2007 at 02:33:32AM -0500, Theo Van Dinter wrote:
This is my main issue with the automatic updates btw. I currently don't like
the idea of the nightly/weekly results enabling/disabling rules and changing
scores (though it doesn't do that yet iirc) on production-use updates.
Oh,
Theo Van Dinter writes:
On Tue, Jan 02, 2007 at 02:33:32AM -0500, Theo Van Dinter wrote:
This is my main issue with the automatic updates btw. I currently don't
like
the idea of the nightly/weekly results enabling/disabling rules and changing
scores (though it doesn't do that yet iirc)
Theo Van Dinter writes:
On Mon, Jan 01, 2007 at 02:43:25PM -0500, Daryl C. W. O'Shea wrote:
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
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
On Mon, Jan 01, 2007 at 02:43:25PM -0500, Daryl C. W. O'Shea wrote:
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.
Well, the manual
