Bug Prioritization

[0xKheops]

Inspired by [Bug Prioritization | WebKit](https://webkit.org/bug-prioritization/)

Standard priority rules

Each bug is assigned the first appropriate priority listed below from top to bottom.

P1 - “Drop tools and fix”

• Any issue with the core functionality of the extension, including: 1) signing transactions, 2) viewing balances and 3) connecting to dapps.
• Any reproducible crash or hang.
• Any regression from a previous publicly released version of Talisman.
• Serious problem on important network due to network change or newly-important network.
• Serious problem on important dapp due to dapp change or newly-important dapp.
• Serious security issue, i.e. CVE.
• The inability to update our software, i.e. rejection from Chrome Store

P2 - “Prioritize fixing; Pre-empts ShapeUp”

• Product that does not function in some non-trivial way.
• Serious performance complaints.
• Product that has really bad cosmetic problems (e.g., content overlapping such that it’s very hard to read).
• Unreproducible crash or hang that has been reported many times.
• Integrations with dapps - may not be fixable on our side, but we should investigate and discuss with dapp team
• Remove noise from Sentry - prevent errors which are not meaningful from making calls to Sentry

P3 - “Fix during Cooldown or add to Pitch”

• Product that works but has some cosmetic problems.
• Minor performance complaints, such as trivial memory leaks.
• Architecture issues that could help with correctness or performance but are not a clear win in advance.
• Unreproducible crash or hang.

P4 - “Fix during Cooldown or add to Pitch”

• All enhancement requests and feature requests not covered the criteria for p1, p2, or p3.

Common adjustments to priority

• If there is a workaround, the priority may be moved down.
• If a bug gets a lot of duplicates, the priority may be moved up.
• If a bug is getting a lot of public attention, the priority may be moved up.
• If a bug is on a very important site, the priority may be moved up.