As I mentioned in the flury of emails it'll be tonight before you see
the update... stable version updates are based on the rules as they
were when the mass-check that the update is based on was run.
Therefore the cycle is...
1. rules get changed
2. version gets "tagged" for nightly mass-checks
3. mass-check results get submitted and processed
4. scores get generated based on results and an update is generated a
few hours before the next "tagging" happens for the nightly mass-check
So...
1. rules were changed yesterday
2. a version was tagged for mass-checking last night
3. results have been submitted throughout the day
4. scores will be generated and an update generated this evening (in
about 6 hours) using yesterday's rules and last night's mass-check
results for those rules
For trunk updates... it's simply a mkrules of the latest svn version
at the time they are released. There's no score generation and thus
no dependency on a mass-check happening first. The mass-check is the
reason for the delay of the stable updates.
Thanks. That explains perfectly.
Regards,
KAM
