Skip to content
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

Add critical bugs to project board #33

Closed
4 tasks done
ripcurlx opened this issue Feb 18, 2020 · 5 comments
Closed
4 tasks done

Add critical bugs to project board #33

ripcurlx opened this issue Feb 18, 2020 · 5 comments
Assignees
Projects

Comments

@ripcurlx
Copy link

ripcurlx commented Feb 18, 2020

  • label issues with is:priority
  • add issues to project board
  • label issues with is:critical bug where appropriate
  • add remaining critical bugs from support team
@ripcurlx ripcurlx self-assigned this Feb 18, 2020
@ripcurlx ripcurlx added this to To do in Admin Tasks via automation Feb 18, 2020
@ripcurlx ripcurlx moved this from To do to In progress in Admin Tasks Feb 18, 2020
@cbeams
Copy link
Member

cbeams commented Feb 18, 2020

* label issues with `is:priority`

@ripcurlx, thanks for adding this issue. Regarding labeling, I'd prefer that we create a new is:critical bug, or is:critical in conjunction with the existing is:bug label. is:priority is fine, too, but it's implied by is:critical bug. The is:critical bug label will allow us to automate via GitHub Actions adding this to the Critical Bugs board. is:priority alone will not.

Note that I've also updated the description of bisq-network/projects#16 to reference this task in the task list.

@ripcurlx
Copy link
Author

I'll update those priority issues that are critical bugs. I'll still use is:priority as well as there are issues that are within our priorities, but not a bug per se.

@ripcurlx
Copy link
Author

Done

@cbeams
Copy link
Member

cbeams commented Feb 19, 2020

Closing as complete. See bisq-network/projects#16 for remaining tasks related to establishing the Critical Bugs board and process. Thanks @ripcurlx and @leo816!

@ripcurlx, I noticed that the In Progress issues on the board do not have assignees. This by definition should never be the case. Can you assign the issues as appropriate?

@cbeams cbeams closed this as completed Feb 19, 2020
Admin Tasks automation moved this from In progress to Done Feb 19, 2020
@cbeams
Copy link
Member

cbeams commented Feb 19, 2020

@cbeams wrote:

[@ripcurlx] Can you assign the (In progress) issues as appropriate?

All good, I assigned them to @dmos62, as he is obviously the one working on them / submitting PRs for them.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
No open projects
Development

No branches or pull requests

3 participants