Article / Maintenance timeline
Delivery and maintenance over two years
The complete monthly series puts delivery, defect reports, and corrections on the same calendar. Separate scales and source-linked records make the counts inspectable.
Two years of delivery and reported problems
September 2024–September 3, 2026. Monthly delivery and known released-defect cases are shown on separate scales. September 2026 contains only three days.
† Adoption occurred March 10 at 16:38:20 UTC; the March bar spans both workflows. Pre/post summaries use that exact instant. Teal marks reports; amber marks first corrected publications. These are known, deduplicated cases with supported released status. Unknown release status and unresolved candidates are excluded from those bars and remain visible below. Two direct-mainline candidates have no established discovery instant and cannot be assigned to a month; they remain unresolved in the ledger.
Exact monthly values, discovery channels, and known backlog
| Month | PRs | Releases | External discovery | Internal human | Automated / agent | Unknown discovery | Corrected | Known backlog at start | Pre-release findings | Unknown release status | Unresolved candidates |
|---|---|---|---|---|---|---|---|---|---|---|---|
| 2024-09 | 0 | 0 | 1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 |
| 2024-10 | 14 | 5 | 0 | 0 | 0 | 2 | 2 | 1 | 0 | 3 | 1 |
| 2024-11 | 2 | 1 | 1 | 0 | 0 | 0 | 1 | 1 | 0 | 0 | 0 |
| 2024-12 | 3 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | 1 |
| 2025-01 | 11 | 3 | 1 | 0 | 0 | 0 | 2 | 1 | 0 | 0 | 0 |
| 2025-02 | 2 | 1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 |
| 2025-03 | 3 | 0 | 1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 |
| 2025-04 | 2 | 1 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | 0 |
| 2025-05 | 1 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | 1 |
| 2025-06 | 4 | 2 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | 0 |
| 2025-07 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | 0 |
| 2025-08 | 3 | 1 | 1 | 0 | 0 | 0 | 1 | 1 | 0 | 0 | 0 |
| 2025-09 | 8 | 4 | 1 | 0 | 0 | 3 | 4 | 1 | 0 | 0 | 0 |
| 2025-10 | 2 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | 0 |
| 2025-11 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | 0 |
| 2025-12 | 1 | 1 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | 0 |
| 2026-01 | 16 | 3 | 0 | 0 | 0 | 0 | 0 | 1 | 1 | 0 | 1 |
| 2026-02 | 6 | 2 | 1 | 0 | 0 | 0 | 1 | 2 | 0 | 0 | 0 |
| 2026-03 | 48 | 6 | 2 | 0 | 0 | 1 | 5 | 2 | 1 | 0 | 3 |
| 2026-04 | 146 | 7 | 6 | 0 | 0 | 8 | 13 | 0 | 0 | 3 | 3 |
| 2026-05 | 49 | 3 | 1 | 0 | 0 | 0 | 2 | 1 | 0 | 0 | 1 |
| 2026-06 | 2 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 |
| 2026-07 | 3 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 2 |
| 2026-08 | 36 | 7 | 0 | 0 | 0 | 1 | 1 | 0 | 1 | 1 | 5 |
| 2026-09 (partial) | 3 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 |
“Known backlog” means identified public reports awaiting a corrected public release, with supported released status. It excludes unknown and undisclosed defects. A zero in a discovery-channel column is not evidence that no one in that channel found defects: discovery attribution is often unknown. Inspect the public-record census.