Skip to content

Docs: Clarify deprecation policy for Gutenberg plugin - #14756

Merged
aduth merged 1 commit into
masterfrom
update/docs-deprecation
Apr 2, 2019
Merged

aduth merged 1 commit into
masterfrom
update/docs-deprecation

Conversation

@aduth

@aduth aduth commented Apr 1, 2019

Copy link
Copy Markdown
Member

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:

The Gutenberg project's deprecation policy is intended to support backward compatibility for releases, when possible.

[Emphasis mine]

Testing Instructions:

Documentation updates only.

@oandregal oandregal left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

This is much clearer, thanks!

@aduth
aduth merged commit a64a98d into master Apr 2, 2019
@aduth
aduth deleted the update/docs-deprecation branch April 2, 2019 17:21
@youknowriad youknowriad added this to the 5.5 (Gutenberg) milestone Apr 12, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

[Type] Developer Documentation Documentation for developers

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants