... | @@ -23,13 +23,13 @@ In addition, there are already quite some options that are ancient, obsoleted, o |
... | @@ -23,13 +23,13 @@ In addition, there are already quite some options that are ancient, obsoleted, o |
|
|
|
|
|
## Deprecating
|
|
## Deprecating
|
|
|
|
|
|
A configuration option that is candidate for removal will be deprecated first. During this phase the option will still work, but we will be communicating to users that the option is going to be removed soon. A user that has deprecated options configured will see warnings in their logs and needs to take action to get rid of those log messages. Configuration options that are deprecated will be identified in the Release Note for the release they are deprecated in.
|
|
A configuration option that is candidate for removal will be deprecated first. During this phase the option will still work, but we will be communicating to users that the option is going to be removed soon. A user that has deprecated options configured will see warnings in their logs and needs to take action to get rid of those log messages. Named-checkconf will also report that there are options included that are deprecated. (Request- for a 'configuration file beautifier' mode that would strip out the options that are deprecated and deliver a usable named-conf. This would be useful only if it could also preserve the comments in the file.) Configuration options that are deprecated will be identified in the Release Note for the release they are deprecated in. A list of deprecated options will also be included as an appendix in the ARM.
|
|
|
|
|
|
Deprecating an option can be done at any time, but preferably before the next ESV release. For example, an option that you want to deprecate before the ESV 9.16 will need to go in the 9.15 development or the 9.14 stable release.
|
|
Deprecating an option can be done at any time, but preferably before the next ESV release. For example, an option that you want to deprecate before the ESV 9.16 will need to go in the 9.15 development or the 9.14 stable release.
|
|
|
|
|
|
## Removing
|
|
## Removing
|
|
|
|
|
|
A user that has a removed 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.
|
|
A user that has a removed option configured will be unable to start `named` because the configuration option is no longer known. (If there are multiple statements in the configuration that are removed, please run the whole configuration through the parser and spit out the whole list.) 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.
|
|
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.
|
|
|
|
|
... | | ... | |