Updating RFC0041 - PowerShell Core Policy#224
Merged
Conversation
14 tasks
TravisEz13
approved these changes
Sep 4, 2019
iSazonov
approved these changes
Sep 5, 2019
Contributor
|
@PowerShell/powershell-committee reviewed this with @SteveL-MSFT, @daxian-dbw, @JamesWTruher, and @joeyaiello and we're approving these changes to preserve back compat with what's in 6.1 and 6.2 |
Contributor
|
Should we also update the RFC version from 0.1 to 0.2? |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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.
RFC0041-Policy specifies policy reg keys other than what current code is using,
so implementing RFC as it is will end up as a breaking change.
As confirmed by RFC owner @TravisEz13, the RFC was never intended to contain a breaking change,
so RFC has to be updated to avoid a breaking change.