docs: api_lifecycle: Change where to list deprecated items

When deprecating APIs, let's tell users to add to one GitHub issue tracking all deprecated APIs meant to be removed, so the process is simpler and hopefully developers do it. Signed-off-by: Alberto Escolar Piedras <[email protected]>
argentum-systems · Aug 15, 2024 · 3f48089 · 3f48089
1 parent e7b267d
commit 3f48089
Showing 1 changed file with 3 additions and 3 deletions.
diff --git a/doc/develop/api/api_lifecycle.rst b/doc/develop/api/api_lifecycle.rst
@@ -236,9 +236,9 @@ The following are the requirements for deprecating an existing API:
   - Code using the deprecated API needs to be modified to remove usage of said
     API
   - The change needs to be atomic and bisectable
-  - Create a GitHub issue to track the removal of the deprecated API, and
-    add it to the roadmap targeting the appropriate release
-    (in the example above, 1.16).
+  - Add an entry in the corresponding release
+    `GitHub issue <https://github.com/zephyrproject-rtos/zephyr/labels/deprecation_tracker>`_
+    tracking removal of deprecated APIs.
 
 During the deprecation waiting period, the API will be in the ``deprecated``
 state. The Zephyr maintainers will track usage of deprecated APIs on