[hop-website] branch master updated: Add issue priority guide

[ha...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

hansva pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/hop-website.git


The following commit(s) were added to refs/heads/master by this push:
     new 0eff0ff86 Add issue priority guide
     new 455e1232d Merge pull request #168 from hansva/master
0eff0ff86 is described below

commit 0eff0ff860c098cb181303c9f22fbde2e8339806
Author: Hans Van Akelyen <ha...@gmail.com>
AuthorDate: Tue Nov 29 10:09:26 2022 +0100

    Add issue priority guide
---
 .../contribution-guides/priority-guide.adoc        | 58 ++++++++++++++++++++++
 1 file changed, 58 insertions(+)

diff --git a/content/community/contribution-guides/priority-guide.adoc b/content/community/contribution-guides/priority-guide.adoc
new file mode 100644
index 000000000..16309f01e
--- /dev/null
+++ b/content/community/contribution-guides/priority-guide.adoc
@@ -0,0 +1,58 @@
+---
+title: "Issue Priorities"
+---
+
+== Issue Priorities
+
+=== Priority 0: Outage
+
+This is reserved only for the most critical of bugs halting all development on the project.
+
+*Example Priority 0 issues*:
+
+ - the build is broken, halting all development
+ - the website is down
+ - a vulnerability requires a point release ASAP
+
+=== Priority 1: Critical
+
+This is considered a high priority. Most P1 bugs should block a release.
+P1 bugs should not be unassigned and require frequent status updates.
+
+*Example Priority 1 issues*:
+
+ - regression in integration tests
+ - important component is nonfunctional
+ - performance regression
+
+=== Priority 2: Default
+
+Most tickets fall into this priority. These can be planned and
+executed by anyone who is interested. No special urgency is associated, but if
+no action is taken on a P2 ticket for a long time, it indicates it is actually
+just P3/nice-to-have.
+
+*Example Priority 2 issues*
+
+ - typical feature request
+ - bug that affects some use cases but don't make a component nonfunctional
+
+=== Priority 3: Nice-to-have
+
+Nice-to-have improvements.
+
+*Example Priority 3 issues*
+
+ - feature request that is nice-to-have
+ - ticket filed as P2 that no one finds time to work on
+
+=== Priority 4
+
+Nice-to-have improvements that are also very small and easy.
+Usually it is quicker to just fix them than to file a bug, but the issue
+can be referenced by a pull request and shows up in release notes.
+
+*Example Priority 4 issues*
+
+ - spelling errors in comments or code
+ - sonar code smells