refactor: compatibility policy for configuration files #2822
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
quake
approved these changes
Jul 13, 2021
zhangsoledad
approved these changes
Jul 13, 2021
doitian
approved these changes
Jul 13, 2021
|
bors r=quake,doitian,zhangsoledad |
|
Build succeeded: |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Compatibility Policy for Configuration Files
Deny unknown configuration items.
To avoid several kinds of mistakes, for example, typos.
Allow deprecated configuration items, but they will be ignored; and warning messages will be output.
After several versions, if these deprecated items satisfied any of the following conditions, they will be fully removed (denied):
The default configuration files will not include any deprecated configuration items.
The default configuration files will not enable any experimental configuration items.