This is an automated email from the ASF dual-hosted git repository. davsclaus pushed a commit to branch blog/camel-bug-fix-track-record in repository https://gitbox.apache.org/repos/asf/camel-website.git
commit b654a5c07ff14a6ee23447cc8d72a91654bf76ec Author: Claus Ibsen <[email protected]> AuthorDate: Sat Jun 6 08:03:56 2026 +0200 blog: Apache Camel's bug fix track record Co-Authored-By: Claude Opus 4.6 <[email protected]> --- .../06/camel-bug-fix-track-record/featured.svg | 102 ++++++++++++++ .../2026/06/camel-bug-fix-track-record/index.md | 147 +++++++++++++++++++++ 2 files changed, 249 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..d524c601 --- /dev/null +++ b/content/blog/2026/06/camel-bug-fix-track-record/featured.svg @@ -0,0 +1,102 @@ +<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, 120)" 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="210" text-anchor="middle" fill="#e8792f" font-size="36" font-weight="bold">1,178</text> + <text x="120" y="235" text-anchor="middle" fill="#8899bb" font-size="14" font-weight="500" letter-spacing="1">BUGS FIXED</text> + </g> + + <!-- Left stat --> + <g transform="translate(70, 160)"> + <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> + + <!-- Right stat --> + <g transform="translate(600, 160)"> + <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">300+ COMPONENTS</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">54%</text> + <text x="135" y="52" text-anchor="middle" fill="#667799" font-size="11">FIXED SAME DAY</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">77%</text> + <text x="400" y="52" text-anchor="middle" fill="#667799" font-size="11">FIXED WITHIN 7 DAYS</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">1.0x</text> + <text x="665" y="52" text-anchor="middle" fill="#667799" font-size="11">FIX RATIO EVERY YEAR</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..06dde7f7 --- /dev/null +++ b/content/blog/2026/06/camel-bug-fix-track-record/index.md @@ -0,0 +1,147 @@ +--- +title: "Apache Camel's Bug Fix Track Record: 1,178 Bugs Fixed in 3 Years" +date: 2026-06-06 +draft: true +authors: [ClausIbsen] +categories: ["Features"] +preview: "A data-driven look at how the Apache Camel community responds to and fixes bugs — 1,178 resolved in 3 years, with a median resolution time of 1 day." +--- + +When you adopt an open-source integration framework, you're making a bet on the community behind it. +Can they keep up? Will bugs get fixed, or pile up? What happens when something breaks at 2 AM? + +We pulled the numbers from [JIRA](https://issues.apache.org/jira/projects/CAMEL) and +[GitHub](https://github.com/apache/camel) to see what three and a half years of Apache Camel bug data actually looks like. + +The short version: **11 open bugs across 300+ components, and half of all bugs are fixed within 24 hours.** + +## 1,178 bugs fixed since January 2023 + +Over the past three and a half years, the Apache Camel community has resolved **1,178 bugs**. +That's roughly one bug fix every single day. + +Here's how the numbers break down by year: + +| Year | Bugs Reported | Bugs Fixed | Avg Resolution | Median Resolution | Fixed Same/Next Day | +|------|--------------|------------|----------------|-------------------|-------------------| +| 2023 | 308 | 313 | 34.3 days | 2 days | 49% | +| 2024 | 383 | 391 | 27.6 days | 1 day | 55% | +| 2025 | 313 | 315 | 10.7 days | 1 day | 57% | +| 2026 (to date) | 162 | 161 | — | 1 day | — | + +A few things stand out: + +- The **median resolution time dropped from 2 days to 1 day** between 2023 and 2024 and has stayed there. +- The **average resolution time fell from 34 days to 11 days** — a 3x improvement. The average is pulled up by occasional old bugs + that get cleaned up, but the trend is clearly downward. +- The percentage of bugs **fixed same-day or next-day rose from 49% to 57%** — the community is getting faster. + +## The backlog never grows + +Every year, the community resolves slightly more bugs than are reported. +The ratio has been ~1.0x for three and a half years straight. + +| Year | Reported | Resolved | Net | +|------|----------|----------|-----| +| 2023 | 308 | 313 | +5 | +| 2024 | 383 | 391 | +8 | +| 2025 | 313 | 315 | +2 | +| 2026 H1 | 162 | 161 | -1 | + +This matters because it means the project never accumulates a growing pile of unresolved issues. +Bugs come in, bugs go out, and the backlog stays near zero. + +As of today, the entire project has **11 open bugs** across over 300 components — one open bug per 27+ components. + +## Bugs reported per month + +Here's the monthly incoming bug rate across the full period: + +| Month | 2023 | 2024 | 2025 | 2026 | +|-------|------|------|------|------| +| Jan | 22 | 22 | 24 | 31 | +| Feb | 27 | 31 | 43 | 39 | +| Mar | 30 | 35 | 30 | 30 | +| Apr | 21 | 34 | 36 | 24 | +| May | 24 | 30 | 25 | 32 | +| Jun | 26 | 28 | 25 | | +| Jul | 21 | 29 | 27 | | +| Aug | 37 | 32 | 22 | | +| Sep | 33 | 47 | 16 | | +| Oct | 28 | 40 | 26 | | +| Nov | 19 | 27 | 24 | | +| Dec | 20 | 28 | 15 | | + +The incoming rate holds steady at roughly **25–30 bugs per month**. The 2024 spike (peaking at 47 in September) +correlates with users migrating to Camel 4.x from 3.x — a natural bump when a major version goes mainstream. +By late 2025, the rate settled back to baseline as the migration wave completed. + +## More components, same bug rate + +Between Q3 2025 and Q1 2026, the community added over 50 new components — AI connectors, MCP support, +document processing, and more. The project's surface area grew by approximately 15%. + +The incoming bug rate? Unchanged. + +New features shipped without destabilizing existing ones. The project's modular architecture and testing +discipline hold up even during periods of rapid growth. + +## Commit activity + +The Apache Camel community remains one of the most active open-source integration projects. + +| Year | Commits | Contributors | Releases | +|------|---------|-------------|----------| +| 2023 | 6,130 | 204 | 28 | +| 2024 | 5,484 | 158 | 20 | +| 2025 | 4,440 | 150 | 27 | +| 2026 H1 | 3,226 | 92 | 11 | + +2026 is on pace to match or exceed 2025 in commits, with Q1 2026 posting the highest single-quarter +commit count (1,893) since early 2023 — achieved with fewer contributors, reflecting rising +productivity per person. + +The release cadence has been consistent: roughly **2 releases per month**, giving users a short path from +bug fix to production. + +## 77% of bugs fixed within a week + +Looking at the full 3-year dataset: + +- **54%** of bugs are fixed same-day or next-day +- **77%** are fixed within 7 days +- Only the remaining 23% take longer, typically because they involve complex edge cases, + hard-to-reproduce environments, or deliberate scheduling for a specific release + +When you report a bug to the Camel community, the most likely outcome is a fix within the same week. + +## 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 bug data tells a clear story: + +- **Bugs get fixed fast.** Median 1-day resolution, sustained for over two years. +- **The project doesn't accumulate debt.** Resolved-to-reported ratio stays at 1.0x, year after year. +- **Growth doesn't break things.** 50+ new components added without increasing the bug rate. +- **Releases ship constantly.** ~2 per month, so fixes reach you quickly. +- **The community is large and active.** Hundreds of contributors, thousands of commits, every year. + +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 shows up — every single day. + +## Try it yourself + +The numbers in this post are fully verifiable. Browse the +[Camel JIRA](https://issues.apache.org/jira/projects/CAMEL) and +[GitHub repository](https://github.com/apache/camel) to see for yourself. + +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).
