Docs: Clarify deprecation policy for Gutenberg plugin #14756
Merged
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
aduth
requested review from
ajitbohra,
chrisvanpatten,
mkaz,
notnownikki and
youknowriad
as code owners
This was referenced Apr 1, 2019
oandregal
approved these changes
Apr 2, 2019
This was referenced Apr 15, 2019
Closed
Closed
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.
Previously: #9925
This pull request seeks to reinstate the prescribed backwards-compatibility support commitment for the plugin, and to clarify the distinction from features which land in a stable release of WordPress.
The current text reads as though it is missing the specific details of support:
[Emphasis mine]
Testing Instructions:
Documentation updates only.