Re: Config variable source values

[Alan Carroll]

 I don't see the conflict with the policy you quoted. Use of the config 
variable source mechanism means that new configuration options can be added to 
minor versions because it can be done without an incompatible change, exactly 
in line with "MINOR version when you add functionality in a 
backwards-compatible manner". I think the ability to have a smoother 
transition, where configuration changes are enabled but not required, is very 
nice for the people who actually deploy ATS.
But the real local issue here is, should we have the TS-3650 mechanism only for 
core and not for plugins? What is the justification for having it not work only 
for plugins?