mirror of
https://github.com/ipfs/kubo.git
synced 2025-06-25 15:08:45 +08:00
Change issue template to use Severity instead of Priority
Priority is very much subjective. Severity allows us to state examples and decide on it objectivelly. License: MIT Signed-off-by: Jakub Sztandera <kubuxu@protonmail.ch>
This commit is contained in:
@ -1,11 +1,16 @@
|
||||
<!-- Output From `ipfs version --all`) -->
|
||||
<!-- Output From `ipfs version --all` -->
|
||||
#### Version information:
|
||||
|
||||
<!-- Bug, Feature, Enhancement, Etc -->
|
||||
#### Type:
|
||||
|
||||
<!-- from `P0` "Critical" to `P5` "Relatively Unimportant") -->
|
||||
#### Priority:
|
||||
<!-- One of following:
|
||||
Critical - System crash, application panic.
|
||||
High - The main functionality of the application does not work, API breakage, repo format breakage, etc.
|
||||
Medium - A non-essential functionality does not work, performance issues, etc.
|
||||
Low - An optional functionality does not work.
|
||||
Very Low - Translation or documentation mistake. Something that really does not matter much but should be noticed for a future release. -->
|
||||
#### Severity:
|
||||
|
||||
#### Description:
|
||||
|
||||
@ -20,4 +25,4 @@ This is for you! Please read, and then delete this text before posting it.
|
||||
The go-ipfs issues are only for bug reports and directly actionable features.
|
||||
Read https://github.com/ipfs/community/blob/master/contributing.md#reporting-issues if your issue doesn't fit either of those categories.
|
||||
Read https://github.com/ipfs/go-ipfs/blob/master/docs/github-issue-guide.md if you are not sure how to fill in this issue.
|
||||
-->
|
||||
-->
|
||||
|
Reference in New Issue
Block a user