From daa7ae4e249d136ba0113547f10f36ed63236208 Mon Sep 17 00:00:00 2001 From: ZhijunWei Date: Wed, 27 Jun 2018 09:03:03 -0400 Subject: [PATCH] Update the Bugs link for triage This content has been moved to [0] [0]: https://docs.openstack.org/project-team-guide/bugs.html Change-Id: I9240be68bcaadf5491b6ee2f406e847ef1b902f3 --- doc/source/contributor/policies/blueprints.rst | 2 +- doc/source/contributor/policies/bugs.rst | 4 ++-- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/doc/source/contributor/policies/blueprints.rst b/doc/source/contributor/policies/blueprints.rst index eab5256bfe8..2aece243edb 100644 --- a/doc/source/contributor/policies/blueprints.rst +++ b/doc/source/contributor/policies/blueprints.rst @@ -84,7 +84,7 @@ The workflow for the life an RFE in Launchpad is as follows: * Priority: there will be only two priorities to choose from, High and Low. It is worth noting that priority is not to be confused with - `importance `_, + `importance `_, which is a property of Launchpad Bugs. Priority gives an indication of how promptly a work item should be tackled to allow it to complete. High priority is to be chosen for work items that must make substantial diff --git a/doc/source/contributor/policies/bugs.rst b/doc/source/contributor/policies/bugs.rst index 1e2e351acd7..1d3e558da12 100644 --- a/doc/source/contributor/policies/bugs.rst +++ b/doc/source/contributor/policies/bugs.rst @@ -149,7 +149,7 @@ Bug Screening Best Practices When screening bug reports, the first step for the bug deputy is to assess how well written the bug report is, and whether there is enough information for anyone else besides the bug submitter to reproduce the bug and come up -with a fix. There is plenty of information on the `OpenStack wiki `_ +with a fix. There is plenty of information on the `OpenStack Bugs `_ on how to write a good bug `report `_ and to learn how to tell a good bug report from a bad one. Should the bug report not adhere to these best practices, the bug deputy's first step @@ -206,7 +206,7 @@ following these suggestions: single node? Is it multi-node? Are you reporting an issue in your own environment or something you encountered in the OpenStack CI Infrastructure, aka the Gate? - * Perceived severity: what would you consider the `importance `_ + * Perceived severity: what would you consider the `importance `_ to be? * Tags (Affected component): try to use the existing tags by relying on