Hi Justin, On Thu, Mar 20, 2014 at 7:56 PM, Justin Edelson <[email protected]> wrote: > ...This sounds mildly silly, but why don't we leave the feature in, but > only enable it based on the presence of a particular feature flag?...
I'd much rather have that optional sling:features support in a separate bundle that we can move to contrib to make its status clear. Right now, even if one can turn of sling:features support in the resource resolver, the functionality is present in a core bundle so we have to maintain it, and the more people use it the harder it is to remove it. So, to refine my proposal I suggest: -Remove the sling:features support from the resource resolver bundle -Remove the corresponding code from the feature flags bundle -Maybe later make that functionality available again in a separate experimental bundle Justin, would that work for you? Is anyone else opposed to that proposal? -Bertrand
