Difference between revisions of "Critical bugs"
| Line 12: | Line 12: | ||
Bisq maintainers will scan every day the [https://github.com/bisq-network/bisq/issues issues] within the Bisq repository and apply the label '''is:critical bug''' to all issues that fit the description above. | Bisq maintainers will scan every day the [https://github.com/bisq-network/bisq/issues issues] within the Bisq repository and apply the label '''is:critical bug''' to all issues that fit the description above. | ||
| − | Afterwards they are | + | Afterwards they are added to the [https://github.com/orgs/bisq-network/projects/7 critical bugs board] |
[[File:Critical Bugs Board.png|none|1105]] | [[File:Critical Bugs Board.png|none|1105]] | ||
| Line 18: | Line 18: | ||
This is where we can detail the concept of Critical Bugs and the [https://github.com/orgs/bisq-network/projects/7 Critical Bugs board] and process. Should be linked to appropriately from the larger [[Development Process]] article. Is already linked from [[Dev_Team#Infrastructure]]. Perhaps a screenshot would be nice for giving people immediate context / feel of what is being talked about. Note that a glossary entry has already been added at [[Glossary#Critical_Bug]]. | This is where we can detail the concept of Critical Bugs and the [https://github.com/orgs/bisq-network/projects/7 Critical Bugs board] and process. Should be linked to appropriately from the larger [[Development Process]] article. Is already linked from [[Dev_Team#Infrastructure]]. Perhaps a screenshot would be nice for giving people immediate context / feel of what is being talked about. Note that a glossary entry has already been added at [[Glossary#Critical_Bug]]. | ||
| − | |||
[[Category:Processes]] | [[Category:Processes]] | ||
[[Category:Infrastructure]] | [[Category:Infrastructure]] | ||
Revision as of 08:04, 21 February 2020
This page explains what critical bugs are and covers the workflow for devs willing to solve them.
What are critical bugs?
Starting with our dev budget, we will focus in a first step on our most critical core use cases. A core use case is any set of actions that a user must be able to complete in order to successfully trade and/or manage funds using Bisq.
A critical bug is any bug or other issue that:
- impedes users from completing a core use case in Bisq, and/or
- repeatedly lands users in support, and/or
- puts user funds or privacy at risk
Bisq maintainers will scan every day the issues within the Bisq repository and apply the label is:critical bug to all issues that fit the description above. Afterwards they are added to the critical bugs board
This is where we can detail the concept of Critical Bugs and the Critical Bugs board and process. Should be linked to appropriately from the larger Development Process article. Is already linked from Dev_Team#Infrastructure. Perhaps a screenshot would be nice for giving people immediate context / feel of what is being talked about. Note that a glossary entry has already been added at Glossary#Critical_Bug.
