... | ... | @@ -29,7 +29,7 @@ Deprecating an option can be done at any time, but preferably before the next ES |
|
|
|
|
|
## Removing
|
|
|
|
|
|
A user that has an obsoleted option configured will be unable to start `named` because the configuration option is no longer known. We plan to remove options first in an annual stable release, so that we will learn what the impact is of removing a certain option before the change hits the more popular ESV release.
|
|
|
A user that has an obsoleted option configured will be unable to start `named` because the configuration option is no longer known. We plan to remove options first in an annual stable release, so that we will learn what the impact is of removing a certain option before the change hits the more popular ESV release. Configuration options that are removed from BIND 9 will be noted in the Release Note for the first version they are removed from.
|
|
|
|
|
|
An option that is deprecated in an ESV release should be removed from the code base in a successor stable release. For example, an option that has been marked as deprecated before 9.16 should be removed in the 9.17 development release (that will become the stable ESV release, 9.18). If it is not removed in the stable release it should also not be removed in the following ESV release. Following the example, it thus should stay in 9.19/9.20.
|
|
|
|
... | ... | |