A policy for removing named.conf options.

[Ondřej Surý]

Hi Warren and everybody,

first, let me thank for the fruitful discussion!

> On 13 Jun 2019, at 15:18, Warren Kumari <warren at kumari.net> wrote:
> 
> Many many people don't look at their logs -- could named also print
> stuff to (stdout, stderr) when starting?
> 
> Note that this will require some testing -- various distributions use
> various init scripts - in many cases things printed at startup don't
> actually make it to the console, and I'm suspecting some init systems
> will barf, but…

It’s undermentioned in the policy proposal, but the named-checkconf
will be loud about the deprecated options.  We can then bug distros to
integrate the named-checkconf run into the pre/postinst maintainer scripts.
(Hey myself, fix the Debian package. Ok, myself…)

> Another phased approach would be to require users to acknowledge that
> the feature is being deprecated -- initially it could warn, and then
> named could require command line flags to enable the (being)
> deprecated features, and then in the next release they would stop (e.g
> named --enable_deprecated_cleaning-interval). I think that this is way
> overkill, but just a thought.

That would take 4 full years to deprecate single option, as we need to take
people that upgrade from ESV to ESV into account, and we were aiming
at slightly “faster” approach :-).

Thanks,
--
Ondřej Surý
ondrej at isc.org