issue_template: Update wording

To be consistent with our labels, lets call incoming issues
"sightings" and not "bugs".  They become bugs once they've
been evaluation by the assigned engineer.

Signed-off-by: paul luse <paul.e.luse@intel.com>
Change-Id: I0d4b8798ddd457aa950f4be23f101adb7251af71
Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/14742
Tested-by: SPDK CI Jenkins <sys_sgci@intel.com>
Reviewed-by: Krzysztof Karas <krzysztof.karas@intel.com>
Reviewed-by: Ben Walker <benjamin.walker@intel.com>
Reviewed-by: Tomasz Zawadzki <tomasz.zawadzki@intel.com>
This commit is contained in:
paul luse 2022-09-28 16:39:54 -07:00 committed by Tomasz Zawadzki
parent 01a8884934
commit 307b8c112f

View File

@ -1,5 +1,5 @@
---
name: Bug report
name: Sighting report
about: Create a report to help us improve. Please use the issue tracker only for reporting suspected issues.
title: ''
labels: 'Sighting'
@ -7,7 +7,7 @@ assignees: ''
---
# Bug report
# Sighting report
<!--- Provide a general summary of the issue in the Title above -->
@ -21,12 +21,12 @@ assignees: ''
## Possible Solution
<!--- Not obligatory, but suggest a fix/reason for the bug, -->
<!--- Not obligatory, but suggest a fix/reason for the potential issue, -->
## Steps to Reproduce
<!--- Provide a link to a live example, or an unambiguous set of steps to -->
<!--- reproduce this bug. Include code to reproduce, if relevant -->
<!--- reproduce this sighting. Include code to reproduce, if relevant -->
1.
2.
3.