Every Apache Camel release ships new features and bug fixes — and those get the headlines. But behind every release there is a quieter effort that rarely gets mentioned: keeping 500+ third-party dependencies current. We compared the parent/pom.xml across every Camel 4.x minor release — from 4.0.0 to 4.20.0 — and counted every dependency version that changed. Here is what we found. 2,449 dependency updates across 20 releases Every minor release updates a significant portion of the dependency tree.

Continue reading ❯

COMMUNITY

Apache Camel has shipped 272 production releases over 19 years without a single month of inactivity. The project averages a new release every 15 days, maintains up to 10 release lines in parallel, and has accumulated 100,000+ commits from over 1,500 contributors since 2007. This track record is not a recent development — it has been sustained continuously since well before the current wave of AI-driven open-source activity. This post presents the evidence.

Continue reading ❯

FEATURES

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, GitHub, and Maven Central to see what 19 years of Apache Camel bug data actually looks like.

Continue reading ❯

COMMUNITY