Versions Compared

Old Version 6

changes.mady.by.user Lucas Saldanha

Saved on

compared with

New Version Current

changes.mady.by.user Sally MacFarlane

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

In a nutshell, our bugs are categorized into 5 priorities. If you want more details about the categories head to our policy page. These buckets are:

PriorityExamples
Very High (P1)
  • Security issues
  • Non-planned backward incompatibilities, preventing the node from participating in the network
High (P2)
  • Degrading performance issues
  • Unexpected behaviour of core features (DevP2P, syncing, etc)
Medium (P3)
  • JSON-RPC request not working with a specific client library due to some loose spec assumption
Low (P4)
  • Node doesn't start up when the configuration file has unexpected "end-of-line" character
Very Low (P5)
  • JSON-RPC json object response not ignoring keys with null value
  • Typo on a CLI command description

Why is it important?

All software has bugs. And sometimes we don't find them. This is something that we need to live with. However, when we do find bugs we need to do our best to identify the potential impact of that bug in our system.

...

We try to be deterministic on our assessments, and most of the time it will involve some discussion. However, if you feel like the assessment on a bug priority is wrong, you can always add a comment on the issue and start a discussion. There is also the option of starting a conversation on Rocket Chat Discord.

Can I change the priority of a bug?

...