... | @@ -8,18 +8,17 @@ This policy describes the procedure for removing named.conf options. |
... | @@ -8,18 +8,17 @@ This policy describes the procedure for removing named.conf options. |
|
|
|
|
|
We certainly don't want to remove any options that are still in widespread use. Before making the decision to go ahead with deprecating an option, we plan to post a notice on the bind-users mailing list to solicit feedback. Depending on the level of concern from the list, we may move ahead or decide to defer deprecating the option.
|
|
We certainly don't want to remove any options that are still in widespread use. Before making the decision to go ahead with deprecating an option, we plan to post a notice on the bind-users mailing list to solicit feedback. Depending on the level of concern from the list, we may move ahead or decide to defer deprecating the option.
|
|
|
|
|
|
|
|
|
|
Below is a table of candidate options we may deprecate and remove. Feel free to add suggestions, or add comments.
|
|
Below is a table of candidate options we may deprecate and remove. Feel free to add suggestions, or add comments.
|
|
|
|
|
|
| option | deprecated in | comments |
|
|
| option | will be deprecated in | comments |
|
|
| ------ | ------------- | --------
|
|
| ------ | ------------- | --------
|
|
| dialup | | |
|
|
| dialup | | |
|
|
| dnssec-lookaside | | |
|
|
| dnssec-lookaside | | |
|
|
| managed-keys | 9.16 | |
|
|
| managed-keys | 9.15/9.16 | |
|
|
| trusted-keys | 9.16 | |
|
|
| trusted-keys | 9.15/9.16 | |
|
|
| cleaning-interval | 9.16 | |
|
|
| cleaning-interval | 9.15/9.16 | |
|
|
|
|
|
|
|
|
|
|
|
|
In addition, there are already quite some options that are ancient, obsoleted, or never implemented before 9.15. They are listed in this issue: https://gitlab.isc.org/isc-projects/bind9/issues/1086 and may be removed in the next stable release after 9.16.
|
|
|
|
|
|
## Deprecating
|
|
## Deprecating
|
|
|
|
|
... | @@ -29,11 +28,10 @@ Deprecating an option can be done at any time, but preferably before the next ES |
... | @@ -29,11 +28,10 @@ Deprecating an option can be done at any time, but preferably before the next ES |
|
|
|
|
|
## Removing
|
|
## 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. 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. 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.
|
|
|
|
|
|
|
|
|
|
## Removing related code
|
|
## Removing related code
|
|
|
|
|
|
The code that relates to a configuration option that is to be removed will in general be deleted at the same time as the configuration option is removed. The BIND 9 team may decide to remove the related code at an earlier stage if it is considered harmful to keep. |
|
The code that relates to a configuration option that is to be removed will in general be deleted at the same time as the configuration option is removed. The BIND 9 team may decide to remove the related code at an earlier stage if it is considered harmful to keep. In that case the option will become obsolete rather than deprecated. |
|
\ No newline at end of file |
|
\ No newline at end of file |