potiuk opened a new pull request, #447:
URL: https://github.com/apache/airflow-steward/pull/447

   Improvements to `tools/pr-management-stats/dashboard.py`, found while 
running the dashboard against `apache/airflow`:
   
   1. **Per-chart legends, no bottom legend.** Drop the single `Legend / 
methodology` panel (and the now-unused `render_legend`); every chart already 
carries its own inline legend / caption.
   2. **Open-backlog: add a `non-draft` line** alongside the total backlog line.
   3. **New "Maintainer-opened PRs" panel** (below *PRs opened by author 
class*) — splits maintainer-authored PRs (authorAssociation 
OWNER/MEMBER/COLLABORATOR) by **author** and by **`provider:*` area**.
   4. **Distinct per-area colours** for the top-areas ready-for-review trend 
chart (new `AREA_PALETTE`). The previous pressure-band colours (red/amber/grey) 
repeated across areas and were indistinguishable.
   5. **Fix the "pressure by area" age columns** (`>4w` / `1-4w` / `recent`). 
They only counted `_is_untriaged` PRs, so with almost everything triaged they 
showed ~0 everywhere. They now show the **age distribution of each area's open 
non-draft contributor PRs**. The pressure *score* and recommendations still use 
the untriaged-age weighting (unchanged).
   6. **Rename** the ready-queue series label `ready cum` → `ready queue`.
   
   ## Test plan
   - `python3 -m pytest tools/pr-management-stats/tests/` — all 24 pass.
   - Rendered against `apache/airflow` (485 open PRs); verified each fix in the 
output: non-draft backlog line present, maintainer panel populated (601 
maintainer PRs split by author + provider), pressure age columns now non-zero 
(e.g. providers 26 >4w / 36 1-4w / 22 recent), distinct area hues, `ready 
queue` label, no bottom legend.
   - No new `ruff` findings (this file is not a `[tool.ruff]` workspace member, 
so it is not reformatted; the diff is logical-only).
   
   🤖 Generated with [Claude Code](https://claude.com/claude-code)


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to