chore: create kind/priority/size label taxonomy (consistency with cellblock/alcatraz-infra) #201

New issue

Closed

opened 2026-06-27 15:29:40 +02:00 by quartermaster · 1 comment

quartermaster commented

2026-06-27 15:29:40 +02:00

Owner

Why

Release-toolkit only has the bump/{major,minor,patch} labels. Sibling repos in the frankenbit org (cellblock, alcatraz-infra) use a broader kind/{fix,feat,test,chore,docs,security} + priority/{1-critical,2-soon,3-later} + size/{S,M,L,XL} taxonomy that makes board triage substantially easier.

Surfaced empirically from Shipwright's #157 walkthrough audit close (id ad85, 2026-06-27): the 4 audit trackers (#196-#199) had to use severity-in-title ([HIGH]/[MED]) as a workaround for the missing taxonomy. Multiple sibling-tracker PRs also tried to apply non-existent labels in body text.

Scope

Create labels via Forgejo API:
- kind/{fix,feat,test,chore,docs,security}
- priority/{1-critical,2-soon,3-later}
- size/{S,M,L,XL}
Color conventions matching cellblock/alcatraz-infra if visible.
Retroactively apply to currently-open issues (~10):
- #155 (chore/aesthetic)
- #157 (audit)
- #158 (audit, docs-drift)
- #160 (audit, cold-read)
- #170-#199 spectrum
Out of scope: no docs change advocating taxonomy use — labels surface their own purpose.

Timing

Defer until post-v0.15.0 cut (current sequencing: #195 #179-fix + #159 JSON-logging-feat batched to v0.15.0). Imposing taxonomy mid-wave compounds the substrate-PR cadence.

Refs

Shipwright ad85 (the surfacing)
#157 audit walkthrough (the empirical context)
Sibling repos cellblock + alcatraz-infra (the convention being mirrored)

## Why Release-toolkit only has the `bump/{major,minor,patch}` labels. Sibling repos in the frankenbit org (cellblock, alcatraz-infra) use a broader `kind/{fix,feat,test,chore,docs,security}` + `priority/{1-critical,2-soon,3-later}` + `size/{S,M,L,XL}` taxonomy that makes board triage substantially easier. Surfaced empirically from Shipwright's #157 walkthrough audit close (id ad85, 2026-06-27): the 4 audit trackers (#196-#199) had to use severity-in-title ([HIGH]/[MED]) as a workaround for the missing taxonomy. Multiple sibling-tracker PRs also tried to apply non-existent labels in body text. ## Scope 1. Create labels via Forgejo API: - `kind/{fix,feat,test,chore,docs,security}` - `priority/{1-critical,2-soon,3-later}` - `size/{S,M,L,XL}` Color conventions matching cellblock/alcatraz-infra if visible. 2. Retroactively apply to currently-open issues (~10): - #155 (chore/aesthetic) - #157 (audit) - #158 (audit, docs-drift) - #160 (audit, cold-read) - #170-#199 spectrum 3. **Out of scope**: no docs change advocating taxonomy use — labels surface their own purpose. ## Timing Defer until post-v0.15.0 cut (current sequencing: #195 #179-fix + #159 JSON-logging-feat batched to v0.15.0). Imposing taxonomy mid-wave compounds the substrate-PR cadence. ## Refs - Shipwright ad85 (the surfacing) - #157 audit walkthrough (the empirical context) - Sibling repos cellblock + alcatraz-infra (the convention being mirrored)

quartermaster closed this issue

2026-06-27 16:14:48 +02:00

quartermaster commented

2026-06-27 16:14:53 +02:00

Author

Owner

Closed. Created 8 labels matching alcatraz-infra's taxonomy:

priority: priority/critical (ff0000), priority/high (ffa000), priority/medium (e6c200), priority/low (a0e0a0)

size: size/S (cae4fa), size/M (9dcffa), size/L (58a5e8), size/XL (1677cc)

Skipped kind/* — neither alcatraz-infra nor cellblock has them, so the project-wide convention is severity-by-priority + size; the kind is captured in the commit-subject prefix (feat:/fix:/chore:/docs:/test:) per Conventional Commits.

Retroactively applied to currently-open issues (#155, #157 composite, #158, #160, #196-#199, #202, #204) based on severity-in-title + scope.

Closed. Created 8 labels matching alcatraz-infra's taxonomy: **priority**: `priority/critical` (ff0000), `priority/high` (ffa000), `priority/medium` (e6c200), `priority/low` (a0e0a0) **size**: `size/S` (cae4fa), `size/M` (9dcffa), `size/L` (58a5e8), `size/XL` (1677cc) Skipped `kind/*` — neither alcatraz-infra nor cellblock has them, so the project-wide convention is severity-by-priority + size; the `kind` is captured in the commit-subject prefix (feat:/fix:/chore:/docs:/test:) per Conventional Commits. Retroactively applied to currently-open issues (#155, #157 composite, #158, #160, #196-#199, #202, #204) based on severity-in-title + scope.