I've always viewed fatal_deprecations as a test time flag. Sure you could use it in production but that was not the original intent.
In general I would agree that logging a simple warning would suffice, regardless of whether fatal_deprecation=true is set. This is however a general problem and not just related to these flags. Given that we are removing so many options (which were silently deprecated) I don't see any harm in re-adding them. What I'm getting at is... this is probably going to break someone because we were in stealth deprecation mode here...
I've always viewed fatal_deprecations as a test time flag. Sure you could use it in production but that was not the original intent.
In general I would agree that logging a simple warning would suffice, regardless of whether fatal_deprecati on=true is set. This is however a general problem and not just related to these flags. Given that we are removing so many options (which were silently deprecated) I don't see any harm in re-adding them. What I'm getting at is... this is probably going to break someone because we were in stealth deprecation mode here...