gluster/glusterdocs
1
0
Fork 0
mirror of https://github.com/gluster/glusterdocs.git synced 2026-02-05 15:47:01 +01:00
Code Issues Releases Activity

Update Bug-Triage.md (#651)

Browse Source 
- Fix links
- Remove gerrit information

Signed-off-by: Sheetal Pamecha <spamecha@redhat.com>
This commit is contained in:
Sheetal Pamecha
2021-02-12 11:13:02 +05:30
committed by GitHub
parent cbf62960fe
commit 36c4b76f1d
1 changed files with 5 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files

11
docs/Contributors-Guide/Bug-Triage.md
View File

@@ -92,19 +92,18 @@ good title may contain:
- A brief explanation of the root cause (if it was found)
- Some of the symptoms people are experiencing
### Adding people to 'watch list' or changing the "Assigned to" field
### Assigning issue or Adding people's github handle in the comment
Normally, developers and potential assignees of an area are already
watching all the issues by default, but sometimes reports describe general
issues. Only if you know developers who work in the area covered by the
issue, and if you know that these developers accept getting CCed or assigned
to certain reports, you can add that person to the CC field or even assign
the bug report to her/him.
to certain reports, you can mention in comment or even assign the bug report
to her/him.
To get an idea who works in which area, check To know component owners ,
To get an idea who works in which area, check to know component owners,
you can check the "MAINTAINERS" file in root of glusterfs code directory
or querying changes in [Gerrit](http://review.gluster.org) (see
[Simplified dev workflow](/Developer-guide/Simplified-Development-Workflow.md))
(see [Simplified dev workflow](../Developer-guide/Simplified-Development-Workflow.md))
### Bugs present in multiple Versions