On 23/05/2011 9:27 AM, John Hardin wrote:
All:
The rules on the 3.3 branch are pretty much stale (the last 3.3 rules
update was published 12/24/2010).
There is no masscheck+promotion process running on the 3.3 branch, and
rule sandbox updates (apart from bugfixes) are only being done with any
regularity on trunk.
Are we going to do a new release with stale rules?
As you know, I made the improvement to the update generation to limit
scores to those defined in sandboxes to act as a safety net against too
high scores being assigned.
Should there be a nightly masscheck+promotion job set up for the 3.3
(i.e. stable production) branch as well and should rule devs remember to
do parallel commits?
Do we need to copy the trunk sandboxes to the 3.3 branch and do a
masscheck/promotion/scoring pass before release?
I also, per Warren's request, provided a current (as of last week)
update for review prior to re-enabling nightly updates. The update is
also the most suitable package to be used as the 3.3.2 release's
associated rule package. I have not heard from *anyone* in regards to
their satisfaction with that update.
In case it's not clear, the rule updates are generated with the rules
from the *trunk* sandboxes (which is why there is a somewhat elaborate
lint testing procedure against every tagged stable release for the
update packages). So copying trunk sandboxes to the 3.3 branch would
not achieve anything.
I'd suggest that there should be nightly masschecks and rule
autopromotion and update generation for the production branch as well as
for trunk. We're doing a lot of rule dev on trunk, but how widely used
is it in actual production?
I'm just waiting for approval from the group to turn the stable updates
back up. trunk updates are of course ongoing already. Are you asking
for generated scores to be released with the trunk update packages?
Daryl
