... | ... | @@ -14,7 +14,7 @@ We certainly don't want to remove any options that are still in widespread use. |
|
|
|
|
|
## 1. 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. **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, which currently are stripped by -checkconf.) 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** and in the **Knowledgebase article** describing [Significant features by Release](https://kb.isc.org/docs/aa-01310).
|
|
|
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. The **named-checkconf** utility 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, which currently are stripped by -checkconf.) 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** and in the **Knowledgebase article** describing [Significant features by Release](https://kb.isc.org/docs/aa-01310).
|
|
|
|
|
|
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.
|
|
|
|
... | ... | |