SA Bugzilla – Bug 6999
RULE COMMITERS - dependency identification
Last modified: 2020-11-24 09:21:32 UTC
In my crusade to cleanup old rules, offload masscheckers from bloat, etc its very hard to work when rule commiters insist in using dependencies from other ppl's sandboxes, many of which could otherwise be dropped Please check your sandbox rules and duplicate any third party's sandbox dependencies in your own sandbox (especially __BLAH sort of stuff) Sandboxes owners may not respect your dependency needs and blow up you rule work. - PLEASE add your handle/tag to your rule names as in KAM_*, AXB_*, FSL_* etc This would make it easier to find potential issues. - Please make use of 10_hasbase.cf - Please avoid keeping nopublish rules in your sandbox for years. Those who run masshcecks will be thankfull if they can speed up their jobs and comply with the time window to deliver results. Please ack seeing this and don't bark if your rules break after I've sweeped somebody else's "abandoned" sandbox. Thanks Axb
ack
good reminder to bump
We should make a committer rule policy / update any existing ones and add these to there in a wiki I would also add that we want to finalize the policy around touching other people's sandboxes. Can someone run with this?
On the other hand, duplicating other people's rules means that if someone fixes/improves a rule it should be fixed/improved in many places instead of just its own sandbox.
Problems can occur with dependencies on full rules in the sandbox, too. If a rule is demoted it will no longer match - this is ok for some rules, but subrules would suit better as they won't pop in and out. metas as scoring rules based from subrules seems a general good way to go