Critical bugs - Revision history

M52go at 05:32, 19 June 2020

2020-06-19T05:32:17Z

Cbeams: Rename 'is:critical bug' to 'is:critical' and link to all issues with that label

2020-02-27T15:53:03Z

Rename 'is:critical bug' to 'is:critical' and link to all issues with that label

Cbeams: Decapitalize critical bug

2020-02-27T15:30:48Z

Decapitalize critical bug

Cbeams: Cbeams moved page Critical Bugs to Critical bugs: Follow article title capitalization rules per Wiki_style_guidelines

2020-02-27T15:28:49Z

Cbeams moved page Critical Bugs to Critical bugs: Follow article title capitalization rules per Wiki_style_guidelines

Cbeams: Cbeams moved page Critical bugs to Critical Bugs without leaving a redirect: revert

2020-02-27T15:28:13Z

Cbeams moved page Critical bugs to Critical Bugs without leaving a redirect: revert

Cbeams: Cbeams moved page Critical Bugs to Critical bugs without leaving a redirect

2020-02-27T15:27:29Z

Cbeams moved page Critical Bugs to Critical bugs without leaving a redirect

Ripcurlx: /* Identification */

2020-02-21T12:59:13Z

Identification

Cbeams: Do a full editing pass for structure and style

2020-02-21T09:22:22Z

Do a full editing pass for structure and style

Ripcurlx at 08:09, 21 February 2020

2020-02-21T08:09:37Z

Cbeams: Use '`' tags for literals`


2020-02-21T08:05:39Z
Use '<code>' tags for literals

				
				
				
				
				
				← Older revision
				Revision as of 08:05, 21 February 2020
				
Line 11:
Line 11:
  * puts user funds or privacy at risk   * puts user funds or privacy at risk
    
− 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 <code>is:critical bug</code> to all issues that fit the description above.
  Afterwards they are added to the [https://github.com/orgs/bisq-network/projects/7 critical bugs board]   Afterwards they are added to the [https://github.com/orgs/bisq-network/projects/7 critical bugs board]

← Older revision		Revision as of 05:32, 19 June 2020
Line 1:		Line 1:
−	This article explains what critical bugs are and covers the process for identifying and fixing them.	+	This article explains what '''critical bugs''' are and covers the process for identifying and fixing them.

	__TOC__		__TOC__

@@ Line 25: / Line 25: @@
 === Identification ===
-Bisq maintainers are notified of new issues as they arrive in the [https://github.com/bisq-network/bisq/issues Bisq repository] and should apply the <code>is:critical bug</code> label to any issue that fits the definition above.
+Bisq maintainers are notified of new issues as they arrive in the [https://github.com/bisq-network/bisq/issues Bisq repository] and should apply the <code>[https://github.com/bisq-network/bisq/labels/is%3Acritical is:critical]</code> label to any issue that fits the definition above.
 Immediately after labeling a critical bug, the Bisq maintainer should add that issue to the <code>To do</code> column of the board, sorting the issue according to its priority relative to the other issues in that column.

@@ Line 3: / Line 3: @@
 __TOC__
-== What is a Critical Bug? ==
+== What is a critical bug? ==
 A [[Glossary#Critical_bug|critical bug]] is any bug or other issue that:
@@ Line 17: / Line 17: @@
 === Board ===
-The Critical Bugs board can be found at https://github.com/orgs/bisq-network/projects/7.
+The critical bugs board can be found at https://github.com/orgs/bisq-network/projects/7.
-[[File:Critical Bugs Board.png|400px|right|thumb|Critical Bugs board]]
+[[File:Critical Bugs Board.png|400px|right|thumb|Critical bugs board]]
 == Process ==

← Older revision		Revision as of 12:59, 21 February 2020
Line 28:		Line 28:

	Immediately after labeling a critical bug, the Bisq maintainer should add that issue to the <code>To do</code> column of the board, sorting the issue according to its priority relative to the other issues in that column.		Immediately after labeling a critical bug, the Bisq maintainer should add that issue to the <code>To do</code> column of the board, sorting the issue according to its priority relative to the other issues in that column.
−
−	''Note (@cbeams): adding newly labeled <code>is:critical bug</code> issues to the <code>To do</code> column of the board should be automatable via a GitHub Action. @ripcurlx to determine whether/when developing such an action would have priority.''

	=== Notification ===		=== Notification ===

@@ Line 1: / Line 1: @@
-This page explains what critical bugs are and covers the workflow for devs willing to solve them.
+This article explains what critical bugs are and covers the process for identifying and fixing them.
 __TOC__
-== What are [[Glossary#Critical_Bug|critical bugs]]? ==
+== What is a Critical Bug? ==
-A '''critical bug''' is any bug or other issue that:
+A [[Glossary#Critical_bug|critical bug]] is any bug or other issue that:
-* impedes users from completing a core use case in Bisq, and/or
+* impedes users from completing a [[Glossary#Core_use_case|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 [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.
+Critical bugs are by definition among the most important and highest priority tasks that can be worked on. The goal is to have zero outstanding critical bugs at any given time. Bisq developers should therefore consider working on critical bugs ahead of anything else.
-Afterwards they are move to the [https://github.com/orgs/bisq-network/projects/7 critical bugs board] and sorted by priority.
-[[File:Critical Bugs Board.png|none|1105]]
+=== Identification ===
-== I want to work on a critical bug ==
+Bisq maintainers are notified of new issues as they arrive in the [https://github.com/bisq-network/bisq/issues Bisq repository] and should apply the <code>is:critical bug</code> label to any issue that fits the definition above.
-If you want to tackle one of this important issues please leave a comment that you want to work on it to get officially assigned.
+Immediately after labeling a critical bug, the Bisq maintainer should add that issue to the <code>To do</code> column of the board, sorting the issue according to its priority relative to the other issues in that column.
-[[File:Assigned issue.png|none|353]]
+''Note (@cbeams): adding newly labeled <code>is:critical bug</code> issues to the <code>To do</code> column of the board should be automatable via a GitHub Action. @ripcurlx to determine whether/when developing such an action would have priority.''
-We do want to prevent that people are working on the same problem at the same time.
+=== Notification ===
-== Do I get compensated by the DAO? ==
+''Note (@cbeams): We may want to have maintainers add a comment to newly-indentified critical bugs mentioning <code>@bisq-network/bisq-devs</code> and <code>@bisq-network/support</code> so that those groups are made aware of the issue and are automatically subscribed to any updates on it. @ripcurlx to decide and update this section accordingly.''
-Delivered work on critical bugs is up for compensation.
+=== Assignment ===
-[[Category:Stubs]]
+If you are a developer interested in working on a given critical bug, you should add a comment to the issue asking to be assigned to it. A Bisq maintainer will follow up with you and make the assignment as appropriate and will transition the issue to the <code>In progress</code> column of the board. You should then proceed to put together a pull request that fixes the bug as per the usual [[Development Process]].
 [[Category:Processes]]

← Older revision	Revision as of 15:28, 27 February 2020
(No difference)

← Older revision	Revision as of 15:27, 27 February 2020
(No difference)