Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

docs(MAINTAIN): Add note about deprecation policy exceptions #25159

Merged
merged 3 commits into from
Sep 15, 2023

Conversation

gpanders
Copy link
Member

@gpanders gpanders requested a review from justinmk September 14, 2023 17:28
@@ -69,7 +69,7 @@ remove existing features, or refactor parts of the code that would change
user's workflow. In these cases, a deprecation policy is needed to properly
inform users of the change.

In general, when a feature is slated to be removed it should:
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This was me adding some intentional wiggle room into the policy, but obviously being more explicit is better.

Co-authored-by: Justin M. Keyes <justinkz@gmail.com>
@gpanders gpanders merged commit 73c71ed into neovim:master Sep 15, 2023
@gpanders gpanders deleted the deprecation-exception branch September 15, 2023 14:32
@github-actions github-actions bot removed the request for review from clason September 15, 2023 14:33
dundargoc pushed a commit to dundargoc/neovim that referenced this pull request Sep 27, 2023
@kaddkaka kaddkaka mentioned this pull request Oct 8, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants