-
-
Notifications
You must be signed in to change notification settings - Fork 3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
expand the issue template and remove the severity field #4624
Conversation
Stebalien
commented
Jan 29, 2018
- Direct users seeking support to the forums.
- Remove the severity field. It doesn't actually help (especially because we can't filter by it and, anyways, we end up deciding the severity).
- Put the section comments inside the sections. This has been annoying me from day 1.
- Put the welcome text at the top so users actually read it.
- Expand on what we want in a description.
* Direct users seeking support to the forums. * Remove the severity field. It doesn't actually help (especially because we can't filter by it and, anyways, *we* end up deciding the severity). * Put the section comments *inside* the sections. This has been annoying me from day 1. * Put the welcome text *at the top* so users actually read it. * Expand on what we want in a description. License: MIT Signed-off-by: Steven Allen <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I am not convinced removing the Severity field is a good idea and would like others feedback on that.
Other than that LGTM.
I've literally never found it useful (not even for the entertainment value). From reading the issue, I can tell how sever it is. Without reading the issue, I can't trust the severity field. IMO, severity is better handled through labels anyways (searchable, easy to see, not set by the reporter). I wonder if it's possible to give labeling permission to contributors. (Although I may just be getting curmudgeonly) |
I agree. Not sure about the possibility of giving labeling permission to contributors. |
Fine grained permissions? GitHub? Silly me. We'd have to use a bot. |
jenkins fails for some reason? Want to file that as an issue? |
Since we decided to remove the Severity field we also need to fix https://github.com/ipfs/go-ipfs/blob/master/docs/github-issue-guide.md so it doesn't mention the Severity field. |
@whyrusleeping standard "timed out waiting for api file show up" bug. |
@Stebalien that generally means that the daemon failed to start for some reason. Not a good sign |
@whyrusleeping unfortunately, it's a common race condition in our tests. Daemon takes too long to start (over 5 seconds). There may be some underlying cause bit I have no idea what it is; I've never reproduced this locally. |
Annoying, but alright. |