Trino Overview
What needs attention now
Work that waits on maintainers, reviewers, or anyone who can answer, and how much of it there is now. Follow the link to the list, and start from the top. Pull requests, issues, and questions of bots are not counted.
| What | Now | Notes | Where |
|---|---|---|---|
| First pull requests without any response | 25 | oldest waits 149 days, 2 marked stale | First pull requests without any response |
| Approved pull requests, not merged | 42 | 27 approved by a maintainer, oldest approval 947 days ago | Approved, not merged |
| Pull requests waiting on reviewers | 121 | 79 wait over a week, 23 marked stale | Waiting on reviewers: pick from the top |
| Pull requests waiting on the author for over 4 weeks | 62 | oldest waits 1126 days, 43 labeled stale-ignore | Waiting on the author for over 4 weeks |
| Issues of the last 90 days without an answer | 51 | oldest waits 87 days | Issues waiting for a first answer |
| Slack questions of the last 4 weeks without a reply | 1 | of 5 questions, 0 in troubleshooting | Slack questions without an answer |
| Jobs failing in the merge queue and nightly runs in the last 14 days | 25 | most often test (plugin/trino-bigquery), 13 times | Which jobs fail in the merge queue and nightly runs |
| Pull requests in clients and tools, approved or without a response | 106 | most in airlift, 36, oldest open 4361 days | Open pull requests |
| Issues in clients and tools of the last 12 months without an answer | 41 | most in trino-gateway, 20 | Issues without an answer |
The project in numbers
Each number is for the last 30 days and for the last 12 months, with the change against the same time before, and a trend of the last 12 periods of 30 days, oldest on the left. The arrows show only the direction, and the word after them says if the change is better or worse for the project. A change under 5% (2 points for a share) is steady. Small numbers swing a lot in 30 days, so a change that the last 12 months don’t show is likely noise; follow the link to see what is behind a number. Response numbers are for pull requests opened at least 7 days before the end of the period, so that each one had a week to get an answer; a response is the first review or comment from another person, or the merge. Bots are not counted. Open now counts what is open at the end of each period. CI runs are kept for a year, and the merge queue started in May 2026, so CI numbers have no change over 12 months. A blank mark means there is no data yet.
Area | Measure | Last 30 days | Change | Last 12 x 30 days | Last 12 months | Change | Details
---------------+-------------------------------------+--------------+-----------------+-------------------+----------------+----------------+-----------------------------------------------------
Pull requests | Opened by people | 423 | ▲ +39% better | ▄▃▄▅▅▅▅▆▆▆▆█ | 3026 | ▲ +47% better | Pull requests per quarter
| Merged | 255 | ▲ +6% better | ▅▄▅▅▅▅▆▆▅▆██ | 2002 | ▲ +29% better | Pull requests per quarter
| Median time to merge | 1d 1h | ▲ +24% worse | ▄█▃▂▃▄▆▃▅▅▄▅ | 20h 27m | ▲ +58% worse | Time to merge per quarter
| Median time to first response | 11h 27m | ▲ +141% worse | ▂▇▃▃▃▂▆▆▇▇▄█ | 5h 55m | ▲ +107% worse | How fast do reviewers respond?
| No response within 7 days | 23% | ▲ +10 pts worse | ▁▅▅▄▄▄▆█▆▆▄▆ | 18% | ▲ +6 pts worse | Waiting on reviewers: pick from the top
| Open now | 323 | ▲ +6% worse | ▅▅▅▆▆▆▇▇████ | 323 | ▲ +88% worse | Is the backlog growing?
People | Opened a pull request | 85 | ▲ +2% steady | ▅▄▅▆▆▆▇▇▇███ | 394 | ▲ +60% better | Is the community growing?
| Reviewed a pull request | 35 | ▼ -10% worse | ▇█▇▇▇▇▇▇▆███ | 104 | ▼ -5% worse | How concentrated is reviewing?
| Had their first pull request merged | 7 | ▼ -74% worse | ▂▂▂▃▁▃▃▆▃▅█▃ | 119 | ▲ +59% better | Is it getting better for newcomers?
Issues | Opened | 73 | ▲ +9% | ▄▄█▆▅▅▅▃▇▇▆▇ | 730 | ▼ -8% | Are issues handled as fast as they come in?
| Open now | 2468 | = 0% steady | ████████████ | 2468 | ▲ +5% worse | Which areas get the most issues?
CI | Merge queue success rate | 68% | ▼ -2 pts worse | ▆▅█▄▅██ | 48% | | Which jobs fail in the merge queue and nightly runs
| Median duration of a passing PR run | 36m 10s | ▼ -3% steady | █████████▆▆▆ | 41m 53s | | How long a CI run takes
(13 rows)
The last 30 days
What happened, and who made it happen. Say thanks, and welcome the people who just started. Bots are not counted. Companies come from GitHub profiles, public organization memberships, and commit emails, so people without one are not counted there.
| What | Details | More |
|---|---|---|
| Releases | none | How often does Trino release? |
| First pull request merged: 7 people | maswin · i-yuki23 · arturmkr · wombatu-kun · baptistegh · sachinsharma3191 · seokyoung-naver | Welcome |
| Milestones of merged pull requests | jiwen624 (25th), tbaeg (25th), JohnFitzpatrick44 (25th), andrewdibiasio6 (10th) | Milestones |
| Most pull requests merged, of 255 | findepi (51), wendigo (41), chenjian2664 (29), raunaqmorarka (21), electrum (11) | Top authors of the last 12 months |
| Most pull requests reviewed, by 35 people | ebyhr (102), raunaqmorarka (95), wendigo (74), findepi (61), chenjian2664 (38) | Top reviewers of the last 12 months |
| Areas with the most merged pull requests | iceberg (43), docs (35), hive (31), delta-lake (24), clickhouse (10) | Where is the focus? |
| Companies with the most merged pull requests, of 12 | Starburst (148), IceGuard (13), DataDog (5), Amazon (4), Netflix (3) | Which companies contribute? |
| Pull requests merged in clients and tools: 365 | regulator (263), airlift (27), trino-go-client (24), trino-gateway (22), aircompressor (9), vthreadtime (6), slice (4), classfile (3), zest (3), airbase (2), grafana-trino (2) | Activity per repository |
Generated on Fri Nov 20 06:14:38 UTC 2026