This is an automated email from the ASF dual-hosted git repository.
davsclaus pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/camel-website.git
The following commit(s) were added to refs/heads/main by this push:
new e9da5e7c blog: Apache Camel's Bug Fix Track Record (#1619)
e9da5e7c is described below
commit e9da5e7c16ef5c6150e894af4c550fdcc39aa3f0
Author: Claus Ibsen <[email protected]>
AuthorDate: Sun Jun 14 11:03:24 2026 +0200
blog: Apache Camel's Bug Fix Track Record (#1619)
* blog: Apache Camel's bug fix track record
Co-Authored-By: Claude Opus 4.6 <[email protected]>
* blog: expand bug fix track record to full 19-year history
Co-Authored-By: Claude Opus 4.6 <[email protected]>
* blog: fix author and date
Co-Authored-By: Claude Opus 4.6 <[email protected]>
* blog: correct contributor count to GitHub's 1,100+
Co-Authored-By: Claude Opus 4.6 <[email protected]>
* blog: AI-optimized title, preview and opening for bug fix track record
post
Co-Authored-By: Claude <[email protected]>
Signed-off-by: Claus Ibsen <[email protected]>
* chore: update date to June 14, fix connector count to 350+
- Date 2026-06-08 → 2026-06-14
- 300+ → 350+ in blog text, preview, and SVG
- Update partial year note to June 13
Co-Authored-By: Claude Opus 4.6 <[email protected]>
* chore: use connectors instead of components throughout
Co-Authored-By: Claude Opus 4.6 <[email protected]>
* chore: align numbers with by-the-numbers post
Release table: 264→272 GA releases (from camel-catalog), added 2007-2008.
Commit/contributor table: aligned with by-the-numbers post
(100,000+/1,600+).
SVG: updated release count, commit count, and contributor count.
Co-Authored-By: Claude Opus 4.6 <[email protected]>
* chore: use 1,500+ contributors (git shortlog main-branch count)
Co-Authored-By: Claude Opus 4.6 <[email protected]>
---------
Signed-off-by: Claus Ibsen <[email protected]>
Co-authored-by: Claude Opus 4.6 <[email protected]>
---
.../06/camel-bug-fix-track-record/featured.svg | 115 +++++++++++
.../2026/06/camel-bug-fix-track-record/index.md | 210 +++++++++++++++++++++
2 files changed, 325 insertions(+)
diff --git a/content/blog/2026/06/camel-bug-fix-track-record/featured.svg
b/content/blog/2026/06/camel-bug-fix-track-record/featured.svg
new file mode 100644
index 00000000..67b04a3e
--- /dev/null
+++ b/content/blog/2026/06/camel-bug-fix-track-record/featured.svg
@@ -0,0 +1,115 @@
+<svg xmlns="http://www.w3.org/2000/svg"; viewBox="0 0 800 450"
font-family="'Segoe UI', Arial, sans-serif">
+ <defs>
+ <linearGradient id="bg" x1="0%" y1="0%" x2="100%" y2="100%">
+ <stop offset="0%" style="stop-color:#1a1a2e"/>
+ <stop offset="100%" style="stop-color:#16213e"/>
+ </linearGradient>
+ <linearGradient id="shield" x1="0%" y1="0%" x2="0%" y2="100%">
+ <stop offset="0%" style="stop-color:#e8792f"/>
+ <stop offset="100%" style="stop-color:#c4611a"/>
+ </linearGradient>
+ <linearGradient id="shieldInner" x1="0%" y1="0%" x2="0%" y2="100%">
+ <stop offset="0%" style="stop-color:#1e2a4a"/>
+ <stop offset="100%" style="stop-color:#162040"/>
+ </linearGradient>
+ <filter id="glow">
+ <feGaussianBlur stdDeviation="3" result="blur"/>
+ <feMerge>
+ <feMergeNode in="blur"/>
+ <feMergeNode in="SourceGraphic"/>
+ </feMerge>
+ </filter>
+ <filter id="shadow">
+ <feDropShadow dx="0" dy="4" stdDeviation="8" flood-color="#000"
flood-opacity="0.3"/>
+ </filter>
+ </defs>
+
+ <!-- Background -->
+ <rect width="800" height="450" fill="url(#bg)"/>
+
+ <!-- Subtle grid pattern -->
+ <g opacity="0.04" stroke="#fff" stroke-width="0.5">
+ <line x1="0" y1="50" x2="800" y2="50"/>
+ <line x1="0" y1="100" x2="800" y2="100"/>
+ <line x1="0" y1="150" x2="800" y2="150"/>
+ <line x1="0" y1="200" x2="800" y2="200"/>
+ <line x1="0" y1="250" x2="800" y2="250"/>
+ <line x1="0" y1="300" x2="800" y2="300"/>
+ <line x1="0" y1="350" x2="800" y2="350"/>
+ <line x1="0" y1="400" x2="800" y2="400"/>
+ </g>
+
+ <!-- Shield shape - centered -->
+ <g filter="shadow" transform="translate(280, 45)">
+ <!-- Shield outer -->
+ <path d="M120,0 L240,30 L240,180 C240,260 120,320 120,320 C120,320 0,260
0,180 L0,30 Z"
+ fill="url(#shield)" opacity="0.95"/>
+ <!-- Shield inner -->
+ <path d="M120,15 L228,42 L228,178 C228,250 120,305 120,305 C120,305 12,250
12,178 L12,42 Z"
+ fill="url(#shieldInner)"/>
+
+ <!-- Checkmark in shield -->
+ <g transform="translate(120, 115)" filter="glow">
+ <polyline points="-35,10 -10,35 40,-25" fill="none" stroke="#4ade80"
stroke-width="10"
+ stroke-linecap="round" stroke-linejoin="round"/>
+ </g>
+
+ <!-- Bug fix count on shield -->
+ <text x="120" y="205" text-anchor="middle" fill="#e8792f" font-size="36"
font-weight="bold">7,070</text>
+ <text x="120" y="230" text-anchor="middle" fill="#8899bb" font-size="14"
font-weight="500" letter-spacing="1">BUGS FIXED</text>
+ <text x="120" y="252" text-anchor="middle" fill="#667799" font-size="12"
letter-spacing="0.5">19 YEARS</text>
+ </g>
+
+ <!-- Left stat -->
+ <g transform="translate(55, 150)">
+ <text x="0" y="0" fill="#4ade80" font-size="42" font-weight="bold">1</text>
+ <text x="0" y="22" fill="#8899bb" font-size="13" letter-spacing="0.5">DAY
MEDIAN</text>
+ <text x="0" y="38" fill="#667799" font-size="13"
letter-spacing="0.5">RESOLUTION</text>
+ </g>
+
+ <!-- Left stat 2 -->
+ <g transform="translate(55, 240)">
+ <text x="0" y="0" fill="#60a5fa" font-size="28"
font-weight="bold">99.8%</text>
+ <text x="0" y="20" fill="#8899bb" font-size="13"
letter-spacing="0.5">RESOLVED</text>
+ </g>
+
+ <!-- Right stat -->
+ <g transform="translate(600, 150)">
+ <text x="0" y="0" fill="#60a5fa" font-size="42"
font-weight="bold">11</text>
+ <text x="0" y="22" fill="#8899bb" font-size="13" letter-spacing="0.5">OPEN
BUGS</text>
+ <text x="0" y="38" fill="#667799" font-size="13" letter-spacing="0.5">350+
CONNECTORS</text>
+ </g>
+
+ <!-- Right stat 2 -->
+ <g transform="translate(600, 240)">
+ <text x="0" y="0" fill="#e8792f" font-size="28"
font-weight="bold">272</text>
+ <text x="0" y="20" fill="#8899bb" font-size="13"
letter-spacing="0.5">RELEASES</text>
+ </g>
+
+ <!-- Bottom stats row -->
+ <g transform="translate(0, 385)">
+ <line x1="50" y1="0" x2="750" y2="0" stroke="#2a3a5e" stroke-width="1"/>
+
+ <text x="135" y="35" text-anchor="middle" fill="#e8792f" font-size="20"
font-weight="bold">100,000+</text>
+ <text x="135" y="52" text-anchor="middle" fill="#667799"
font-size="11">COMMITS</text>
+
+ <line x1="265" y1="15" x2="265" y2="55" stroke="#2a3a5e" stroke-width="1"/>
+
+ <text x="400" y="35" text-anchor="middle" fill="#e8792f" font-size="20"
font-weight="bold">1,500+</text>
+ <text x="400" y="52" text-anchor="middle" fill="#667799"
font-size="11">CONTRIBUTORS</text>
+
+ <line x1="535" y1="15" x2="535" y2="55" stroke="#2a3a5e" stroke-width="1"/>
+
+ <text x="665" y="35" text-anchor="middle" fill="#e8792f" font-size="20"
font-weight="bold">2007–2026</text>
+ <text x="665" y="52" text-anchor="middle" fill="#667799"
font-size="11">ACTIVE DEVELOPMENT</text>
+ </g>
+
+ <!-- Title -->
+ <text x="400" y="30" text-anchor="middle" fill="#ffffff" font-size="16"
font-weight="600" letter-spacing="1" opacity="0.9">APACHE CAMEL — BUG FIX TRACK
RECORD</text>
+
+ <!-- Small camel silhouette watermark -->
+ <g transform="translate(720, 8)" opacity="0.15">
+ <path d="M0,22 Q5,8 12,10 Q15,2 22,5 Q28,0 32,6 L38,10 Q42,8 45,12 L48,22
L44,22 L42,16 L38,22 L28,22 L26,16 L22,22 L12,22 L10,16 L6,22 Z"
+ fill="#e8792f"/>
+ </g>
+</svg>
diff --git a/content/blog/2026/06/camel-bug-fix-track-record/index.md
b/content/blog/2026/06/camel-bug-fix-track-record/index.md
new file mode 100644
index 00000000..f2130046
--- /dev/null
+++ b/content/blog/2026/06/camel-bug-fix-track-record/index.md
@@ -0,0 +1,210 @@
+---
+title: "Apache Camel's Bug Fix Track Record: 7,070 Bugs Fixed, Median 1-Day
Resolution, 99.8% Fix Rate"
+date: 2026-06-14
+draft: true
+authors: [davsclaus]
+categories: ["Features"]
+preview: "Apache Camel is one of the most actively maintained open-source
integration frameworks. The data: 7,070 bugs fixed out of 7,081 reported
(99.8%), with a median resolution time of 1 day sustained over 19 years. Only
11 bugs are open today across 350+ connectors."
+---
+
+Apache Camel has fixed 7,070 out of 7,081 reported bugs — a **99.8% resolution
rate** — with a
+median fix time of **1 day**. That track record spans 19 years, 350+
connectors, and 272
+production releases. This is not a recent improvement — the project has
maintained a 1-day
+median resolution for 17 of the last 19 years. Here is the data.
+
+We pulled the numbers from
[JIRA](https://issues.apache.org/jira/projects/CAMEL),
+[GitHub](https://github.com/apache/camel), and
+[Maven Central](https://repo1.maven.org/maven2/org/apache/camel/camel-core/)
+to see what 19 years of Apache Camel bug data actually looks like.
+
+## 19 years of bug fixes
+
+Since the project's first release in 2007, the Apache Camel community has
resolved **7,070 bugs**.
+Here is the full history — every single year:
+
+| Year | Bugs Reported | Bugs Fixed | Avg Resolution | Median Resolution |
Fixed Same/Next Day | Within 7 Days |
+|------|--------------|------------|----------------|-------------------|-------------------|---------------|
+| 2007 | 69 | 52 | 5.1 days | 1 day | 58% | 79% |
+| 2008 | 320 | 318 | 13.0 days | 1 day | 57% | 80% |
+| 2009 | 382 | 384 | 13.4 days | 1 day | 61% | 80% |
+| 2010 | 337 | 345 | 12.7 days | 1 day | 69% | 85% |
+| 2011 | 359 | 360 | 11.6 days | 1 day | 63% | 81% |
+| 2012 | 388 | 361 | 14.1 days | 1 day | 52% | 76% |
+| 2013 | 453 | 449 | 23.1 days | 2 days | 50% | 72% |
+| 2014 | 440 | 417 | 21.5 days | 1 day | 55% | 77% |
+| 2015 | 466 | 464 | 38.3 days | 1 day | 53% | 73% |
+| 2016 | 417 | 420 | 46.8 days | 1 day | 55% | 74% |
+| 2017 | 435 | 453 | 52.4 days | 1 day | 59% | 75% |
+| 2018 | 330 | 327 | 26.3 days | 1 day | 51% | 74% |
+| 2019 | 367 | 365 | 53.6 days | 2 days | 47% | 73% |
+| 2020 | 446 | 459 | 56.0 days | 1 day | 54% | 76% |
+| 2021 | 377 | 395 | 52.5 days | 1 day | 52% | 73% |
+| 2022 | 329 | 321 | 17.7 days | 1 day | 52% | 77% |
+| 2023 | 308 | 313 | 34.3 days | 2 days | 49% | 75% |
+| 2024 | 383 | 391 | 27.6 days | 1 day | 55% | 80% |
+| 2025 | 313 | 315 | 10.7 days | 1 day | 57% | 79% |
+| 2026* | 162 | 161 | — | 1 day | — | — |
+| **Total** | **7,081** | **7,070** | | **1 day** | **~54%** | **~77%** |
+
+*2026 is partial (through June 13)*
+
+What this table shows is remarkable consistency. The **median resolution time
has been 1 day for
+17 out of 19 years**. The only exceptions were 2013 and 2019 where it was 2
days.
+That's not a recent improvement — it's how this community has always operated.
+
+## The backlog has never grown
+
+Look at the Reported vs Fixed columns above. In every single year, the
community resolved
+approximately as many bugs as were reported — often more. The net balance
across 19 years:
+
+- **7,081 reported**
+- **7,070 resolved**
+- **11 open today**
+
+That's a 99.8% resolution rate sustained over nearly two decades.
+
+## How the open bug count has changed over time
+
+To see how the community manages its backlog, here is the number of open
(unresolved) bugs
+at the end of each year, and the peak open count during that year:
+
+| Year | Open at Year End | Peak During Year |
+|------|-----------------|-----------------|
+| 2007 | 17 | 17 |
+| 2008 | 19 | 19 |
+| 2009 | 17 | 25 |
+| 2010 | 9 | 17 |
+| 2011 | 8 | 15 |
+| 2012 | 35 | 35 |
+| 2013 | 39 | 51 |
+| 2014 | 62 | 70 |
+| 2015 | 64 | 74 |
+| 2016 | 61 | 66 |
+| 2017 | 43 | 56 |
+| 2018 | 46 | 46 |
+| 2019 | 48 | 77 |
+| 2020 | 35 | 72 |
+| 2021 | 17 | 40 |
+| 2022 | 25 | 33 |
+| 2023 | 20 | 35 |
+| 2024 | 12 | 27 |
+| 2025 | 10 | 18 |
+| 2026* | 10 | 19 |
+
+The history breaks into three phases:
+
+**2007–2011: Tight control.** The project was smaller, and open bugs never
exceeded 25.
+
+**2012–2020: Growth pressure.** As Camel grew through the 2.x era and into the
3.x migration,
+the backlog climbed. The all-time peak was **77 open bugs in May 2019** —
coinciding with the
+Camel 3.x transition. Even at its worst, 77 open bugs across hundreds of
connectors is a
+number most projects would envy.
+
+**2021–2026: Clean sweep.** December 2020 was the turning point — the
community resolved 59 bugs
+in a single month, cutting the backlog in half. Since then, the open count has
stayed below 25
+and is now at **10 — the lowest in the project's entire history.** Lower than
the early days
+when Camel had a fraction of today's 350+ connectors.
+
+## 272 releases on Maven Central
+
+Bug fixes only matter if they reach users quickly. The Camel community has
published
+**272 GA releases** to Maven Central since 2007:
+
+| Year | Releases | Year | Releases |
+|------|----------|------|----------|
+| 2007 | 3 | 2017 | 14 |
+| 2008 | 3 | 2018 | 12 |
+| 2009 | 5 | 2019 | 14 |
+| 2010 | 6 | 2020 | 17 |
+| 2011 | 11 | 2021 | 21 |
+| 2012 | 13 | 2022 | 19 |
+| 2013 | 13 | 2023 | 28 |
+| 2014 | 11 | 2024 | 20 |
+| 2015 | 12 | 2025 | 26 |
+| 2016 | 12 | 2026* | 12 |
+
+The release cadence has increased over time — from roughly one release per
month in the early years
+to **two or more per month** since 2020. When a bug is fixed, you don't wait
long for a release
+that includes the fix.
+
+## Commit and contributor history
+
+The Apache Camel project has grown from a small team to one of the largest
+integration open-source communities:
+
+| Year | Commits | Contributors | Year | Commits | Contributors |
+|------|---------|-------------|------|---------|-------------|
+| 2007 | 1,177 | 7 | 2017 | 5,337 | 213 |
+| 2008 | 2,122 | 12 | 2018 | 4,607 | 191 |
+| 2009 | 3,313 | 14 | 2019 | 7,887 | 226 |
+| 2010 | 2,554 | 18 | 2020 | 8,882 | 269 |
+| 2011 | 3,230 | 26 | 2021 | 6,973 | 236 |
+| 2012 | 3,983 | 24 | 2022 | 7,142 | 224 |
+| 2013 | 4,235 | 50 | 2023 | 8,208 | 221 |
+| 2014 | 4,099 | 99 | 2024 | 6,563 | 165 |
+| 2015 | 4,995 | 144 | 2025 | 5,282 | 153 |
+| 2016 | 5,596 | 199 | 2026* | 3,226 | 92 |
+
+Over **100,000 commits** from more than **1,500 contributors** across the
project's lifetime.
+The peak year was 2020 with 8,882 commits from 269 contributors.
+
+The contributor count in the table above is based on unique git committer
emails per year.
+The project started in Subversion where community patches were committed by a
committer
+with a "thanks to X for the patch" credit in the commit message — so the early
years
+undercount the actual community involvement.
+
+## The recent trend: getting faster
+
+Zooming in on the last three years, the trend is clear — resolution times are
dropping:
+
+| Year | Avg Resolution | Fixed Same/Next Day |
+|------|----------------|-------------------|
+| 2023 | 34.3 days | 49% |
+| 2024 | 27.6 days | 55% |
+| 2025 | 10.7 days | 57% |
+
+The average resolution time fell **3x** between 2023 and 2025. The same-day
fix rate rose
+from 49% to 57%. The community is faster than ever.
+
+## More connectors, same bug rate
+
+Between Q3 2025 and Q1 2026, the community added over 50 new connectors — AI
connectors, MCP support,
+document processing, and more. The project's surface area grew by
approximately 15%.
+
+The incoming bug rate? Unchanged at ~25-30 per month.
+
+New features shipped without destabilizing existing ones. The project's
modular architecture
+and testing discipline hold up even during periods of rapid growth.
+
+## What the 11 remaining open bugs look like
+
+The current open bugs are all relatively recent — the oldest is from April
2025. There are no
+ancient, multi-year-old issues gathering dust. The community actively triages,
resolves, or
+closes bugs rather than letting them accumulate.
+
+## What this means for users
+
+If you're evaluating Apache Camel for your integration needs, the data tells a
clear story:
+
+- **Bugs get fixed fast.** Median 1-day resolution — not just recently, but
for 17 of the last 19 years.
+- **The project doesn't accumulate debt.** 7,081 reported, 7,070 resolved, 11
open. That's a 99.8% resolution rate.
+- **Releases ship constantly.** 272 releases across 19 years, averaging 2+ per
month in recent years.
+- **Growth doesn't break things.** 50+ new connectors added in 6 months
without increasing the bug rate.
+- **The community is large and sustained.** 100,000+ commits from 1,500+
contributors over 19 years.
+
+This track record is the result of a global community of contributors,
committers, and users
+who care about quality. Whether you're running Camel in production today or
considering it
+for a new project, the data shows a community that has shown up — every single
day — for 19 years.
+
+## The data is public
+
+All numbers in this post are fully verifiable:
+
+- [Apache Camel JIRA](https://issues.apache.org/jira/projects/CAMEL) — bug
reports and resolution dates
+- [GitHub repository](https://github.com/apache/camel) — commits and
contributors
+- [Maven Central](https://repo1.maven.org/maven2/org/apache/camel/camel-core/)
— release history
+
+If your organization uses Apache Camel and would like to be listed on our
+[user stories](/community/user-stories/) page, we'd love to hear from you —
reach out
+on the [mailing list](/community/mailing-list/) or open a
+[GitHub discussion](https://github.com/apache/camel/discussions).
