On 16 Oct 2020, at 21:06, Noel Butler wrote:
perhaps, the rules above should be defined only for version >=4 and versions <4 should have the original rules.
The rule name change is an artifact of how the rules are version-controlled. We have exactly one version of the rules and it resides in the trunk of the Subversion repository. This imposes a discipline: we MUST keep the rules working with the latest release, with past releases to the degree possible, and with the next release. This also means that rules which use new features get exposed to everyone before the features. A terminology change across the codebase isn't done instantaneously so unless you're running from a 'trunk' checkout, you won't see the changes outside of the rules until they are all done, but while adapting the rules we got a few imperfect interim stages before the current implementation, which just works.
What does NOT work is to conflate the change in rule names with a change in configuration directive names. They are different things.
-- Bill Cole b...@scconsult.com or billc...@apache.org (AKA @grumpybozo and many *@billmail.scconsult.com addresses) Not Currently Available For Hire
