Skip to content

Commit

Permalink
Clarify the deprecation process does not always span multiple WP
Browse files Browse the repository at this point in the history 
releases
  • Loading branch information
@adamziel
adamziel committed Dec 22, 2022
1 parent 435ea50 commit 75ec4fd
Showing 1 changed file with 2 additions and 1 deletion.
3 changes: 2 additions & 1 deletion docs/contributors/code/coding-guidelines.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -149,7 +149,8 @@ plugin during the major WordPress releases. Many plugins and themes rely on thes
features that can't be accessed in any other way. Naturally, these APIs can't be removed without a warning anymore.
They are a part of the WordPress public API and fall under the
[WordPress Backwards Compatibility policy](https://developer.wordpress.org/block-editor/contributors/code/backward-compatibility/).
Removing them involves a deprecation process that spans multiple WordPress releases.
Removing them involves a deprecation process. It may be relatively easy for some APIs, but it may require effort and
span multiple WordPress releases for others.

**Use private experimental APIs instead.**

Expand Down

0 comments on commit 75ec4fd

Please sign in to comment.