bisq-network / admin

@bisq-network admin team task tracking
1 stars 0 forks source link

Add critical bugs to project board #33

Closed ripcurlx closed 4 years ago

ripcurlx commented 4 years ago
cbeams commented 4 years ago
* 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 commented 4 years ago

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 commented 4 years ago

Done

cbeams commented 4 years ago

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 commented 4 years ago

@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.