From 0c373c1b4dc17639463f6593d239e5363c3062cc Mon Sep 17 00:00:00 2001 From: Sal Date: Thu, 27 Aug 2026 12:00:11 +0100 Subject: [PATCH] docs(runbooks): record priority band definitions in triage The public wiki carried a priority definition table that no runbook duplicated, so removing maintainer content from the wiki per ADR 0006 would have dropped it. Record the bands here, where triage classification already lives, and note that `priority:high` covers only the top two. --- runbooks/triage.md | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/runbooks/triage.md b/runbooks/triage.md index 442dcbc40..d1db830e9 100644 --- a/runbooks/triage.md +++ b/runbooks/triage.md @@ -71,6 +71,19 @@ The organization label set in `lib/labels.yml` is the source of truth. Apply at | duplicate | `duplicate` | | not planned | `wontfix` | +### Priority definitions + +Apply `priority:high` only for the top two bands. Everything below is tracked by +project-board `Priority` rather than by a label. + +| Priority | Meaning | +| ------------ | -------------------------------------------------------------------------- | +| **Critical** | Data loss, security vulnerability, or complete breakage with no workaround | +| **High** | Significantly impacts users or blocks important work; schedule next | +| **Medium** | Important but not urgent; prioritize against other planned work | +| **Low** | Nice to have; no fixed timeline | +| **None** | Not yet triaged or genuinely optional | + ## Step 3 — Cross-reference Before responding: