From 75ec4fda506e42ff8b71c8dcca2b3fde4aa0796e Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Adam=20Zieli=C5=84ski?= Date: Thu, 22 Dec 2022 10:39:48 +0100 Subject: [PATCH] Clarify the deprecation process does not always span multiple WP releases --- docs/contributors/code/coding-guidelines.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/docs/contributors/code/coding-guidelines.md b/docs/contributors/code/coding-guidelines.md index b8e0f44eed472e..2608885065cf21 100644 --- a/docs/contributors/code/coding-guidelines.md +++ b/docs/contributors/code/coding-guidelines.md @@ -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.**