From 0eec5dba538780bdb280ead4eb797d8ab4e8dff9 Mon Sep 17 00:00:00 2001 From: Alberto Escolar Piedras Date: Fri, 12 Apr 2019 12:39:00 +0200 Subject: [PATCH] doc: labels: Add links to feature process Added a few links in the labels description section to the feature process section. Signed-off-by: Alberto Escolar Piedras --- doc/development_process/dev_env_and_tools.rst | 16 ++++++++++------ 1 file changed, 10 insertions(+), 6 deletions(-) diff --git a/doc/development_process/dev_env_and_tools.rst b/doc/development_process/dev_env_and_tools.rst index 41754a6ff44..bda53be448e 100644 --- a/doc/development_process/dev_env_and_tools.rst +++ b/doc/development_process/dev_env_and_tools.rst @@ -294,7 +294,8 @@ Issue priority labels ============= =============================================================== Labels ``priority:{high|medium|low}`` Applicable to Issues only -Description To classify the impact and importance of a bug or feature +Description To classify the impact and importance of a bug or + :ref:`feature ` ============= =============================================================== Note: Issue priorities are generally set or changed during the bug-triage or TSC @@ -347,9 +348,10 @@ Issue only labels ``Regression`` Something, which was working, but does not anymore (bug subtype) ``Question`` This issue is a question to the Zephyr developers -``Enhancement`` Changes/Updates/Additions to existing features -``Feature request`` A request for a new feature -``Feature`` A planned feature with a milestone +``Enhancement`` Changes/Updates/Additions to existing + :ref:`features ` +``Feature request`` A request for a new :ref:`feature ` +``Feature`` A :ref:`planned feature` with a milestone ``Duplicate`` This issue is a duplicate of another issue (please specify) ``Good first issue`` Good for a first time contributor to take @@ -357,5 +359,7 @@ Issue only labels issues with additional information ==================== =========================================================== -Any issue must be clasified and labeled as either ``Bug``, ``Question``, -``Enhancement``, ``Feature``, or ``Feature Request``. +Any issue must be classified and labeled as either ``Bug``, ``Question``, +``Enhancement``, ``Feature``, or ``Feature Request``. More information on how +feature requests are handled and become features can be found in +:ref:`Feature Tracking`.