This was extracted (@ 2024-03-20 23:10) from a list of minutes
which have been approved by the Board.
Please Note
The Board typically approves the minutes of the previous meeting at the
beginning of every Board meeting; therefore, the list below does not
normally contain details from the minutes of the most recent Board meeting.
WARNING: these pages may omit some original contents of the minutes.
Meeting times vary, the exact schedule is available to ASF Members and Officers, search for "calendar" in the Foundation's private index page (svn:foundation/private-index.html).
Report was filed, but display is awaiting the approval of the Board minutes.
## Description: The mission of Apache Camel is the creation and maintenance of an open-source integration framework based on known Enterprise Integration Patterns. ## Project Status: Current project status: Ongoing with high activity Issues for the board: There are no issues requiring board attention at this time. ## Membership Data: Apache Camel was founded 2008-12-17 (15 years ago) There are currently 91 committers and 45 PMC members in this project. The Committer-to-PMC ratio is roughly 2:1. Community changes, past quarter: - No new PMC members. Last addition was Andrea Tarocchi on 2023-09-11. - Aurélien Pupier was added as committer on 2023-11-13 - Jono Morris was added as committer on 2023-11-04 - Vignesh Nayak Manel was added as committer on 2023-09-12 ## Project Activity: Apache Camel: - We released Camel 3.14.10 - We released Camel 3.20.7 - We released Camel 3.20.8 - We are about to release 3.20.9 at the time of writing (on vote) - We released Camel 3.21.1 - We released Camel 3.21.2 - We are about to release 3.21.3 at the time of writing (on vote) - We released Camel 4.0.1 - We released Camel 4.0.2 - We released Camel 4.0.3 - We released Camel 4.1.0 - We released Camel 4.2.0 - We are about to release 4.3.0 at the time of writing (on vote) - Note: Camel releases have synchronized releases of Camel-Karaf and Camel-Spring-Boot too for 3.x, while for 4.x only Camel-Spring-Boot is synchronized. - The next Camel 4.x LTS release will be 4.4.0 and we're working on that. - We continued the release train for 3.20.x LTS, and we are about to release the last 3.20.x release before the EOL. - We are still supporting Camel 3.14.x, an LTS train. The release 3.14.10 will be the last one before EOL. - We continued the release train for 3.21.x LTS - We are working on having also a 3.22.x LTS release in the near future - The situation is really healthy and the community is super. We are doing a lot of improvements and we are introducing new features. Apache Camel K: - For Camel K we released a really important 2.1.0 and a 2.0.1 release with a lot of good work from community. It has no coupled dependency from the runtime and its release cycle will be decoupled from the core/runtime release cycle. - Camel K Runtime dependency is now matching the release cycle with Camel Quarkus. - For Camel-K-runtime we released 3.2.0 - At the time of writing two releases are on vote too 3.2.3 and 3.6.0 - Camel K is in good shape and we are doing the best we can to improve the developer experience. Apache Camel Kamelets: - We released Camel Kamelets 4.0.0 - We released Camel Kamelets 4.0.1 - We released Camel Kamelets 4.1.0 - We released Camel Kamelets 4.2.0 - We are working on releasing 4.3.0 - Camel-Kamelets is not only related to camel k anymore so it could be used with all the Camel's flavours - We are improving the overall experience and cleaning up the codebase to make Kamelets runtime agnostic Apache Camel Quarkus: - The Camel-Quarkus work is going ahead following the main camel releases with multiple releases - We released Camel-quarkus 2.16.0 - We released Camel-quarkus 3.2.1 - We released Camel-quarkus 3.2.2 - We released Camel-quarkus 3.2.3 - We released Camel-quarkus 3.4.0 - We released Camel-quarkus 3.5.0 - We released Camel-quarkus 3.6.0 - The health of the project is really good and we are receiving a lot of positive feedback and contribution Camel-Karavan: - Camel-Karavan is improving and more and more contributors are continuing to help. - We released the 4.0.0 version matching the LTS release - We released also the 4.1.0 version - The work is going really well and the community is starting to give feedback. Camel-Kafka-Connector: - Camel Kafka Connector release based on Camel 4.0.0 has been released. - We have a lot of feedback and issues opened and we are working on the backlog - We plan to release a new 4.3.0 release or at most we'll align to the 4.4.0 Overall: - The Camel project and all the subprojects are in good shape and all of them are growing in terms of community involvement. ## Community Health: - 313 issues opened on GitHub, past quarter (3% decrease) and 307 issues closed on GitHub, past quarter (8% decrease): Some of the subproject are using github issues, but Camel core is still on JIRA. We focused mostly on the LTS 4.4.x and some of the Github Issues based projects were focused on backlog activities and alignments. - 4598 commits in the past quarter (15% decrease) and 119 code contributors in the past quarter (9% decrease):The camel core team is focusing on Camel 4.4.x. We saw a good number of contributions from new contributors in subprojects and main Camel. The number of commits is related also to the fact we are starting to use the squash and merge approach instead of the rebase and merge. - 1719 PRs opened on GitHub, past quarter (1% decrease) and 1723 PRs closed on GitHub, past quarter (no change): The number are in line with what we are doing right now, we expect an increase of PRs in the next quarter for two reasons: we introduce dependabot on core Camel and we are going to release multiple LTS releases, so we expect bug fixing and new PRs. - dev@camel.apache.org had a 3% increase in traffic in the past quarter (427 emails compared to 411): There was a spike in the dev ML because of questions and discussions around the development and final decision for Camel 4.4.0, releases schedule, Spring Boot upgrade to 3.2.0 etc. - issues@camel.apache.org had a 18% decrease in traffic in the past quarter (2423 emails compared to 2935): We were focusing on backlog and the clean up done in the last quarter justify the decrease. - users@camel.apache.org had a 7% increase in traffic in the past quarter (228 emails compared to 244): Users are starting to move and ask questions on Zulip - Jira Activity: The number doesn't seem to be accurate in the statistics page. We saw an increase in terms of opened issues. The stats are the following from the reporter: 324 issues opened in JIRA, past quarter (-22% change) 343 issues closed in JIRA, past quarter (-16% change)
## Description: The mission of Apache Camel is the creation and maintenance of an open-source integration framework based on known Enterprise Integration Patterns. ## Project Status: Project status: Ongoing with high activity Issues: There are no issues requiring board attention at this time. ## Membership Data: Apache Camel was founded 2008-12-17 (15 years ago) There are currently 88 committers and 44 PMC members in this project. The Committer-to-PMC ratio is 2:1. Community changes, past quarter: - No new PMC members. Last addition was Nicolas Filotto on 2023-04-05. - Kengo Seki was added as committer on 2023-07-04 ## Project Activity: - We released Camel 3.14.9 - We released Camel 3.18.8 - We released Camel 3.20.6 - We released Camel 3.21.0 - We released Camel 4.0.0-RC1 - We released Camel 4.0.0 - Note: Camel releases have synchronized releases of Camel-Karaf and Camel-Spring-Boot too for 3.x, while for 4.x only Camel-Spring-Boot is synchronized. - We released Camel 4.0.0, our main effort in the last 10 months. - We are continuing release 3.18.x LTS release train and we are in the process of releasing the next patch release. - We started the release train for 3.20.x LTS, and we are already at the sixth patch release. We want to release another patch release soon. - We are still supporting Camel 3.14.x, an LTS train, but it's going EOL, there will be another release 3.14.10. - We released another 3.x LTS Release the 3.21.0 - For Camel K we released a really important 2.0 release with a lot of good work from community. It has no coupled dependency from the runtime and its release cycle will be decoupled from the core/runtime release cycle. - Camel K Runtime dependency is now matching the release cycle with Camel Quarkus. - For Camel-K-runtime we released 2.16.0 - For Camel-Kamelets releases - We released Camel Kamelets 3.20.6 - We released Camel Kamelets 3.21.0 - We released Camel Kamelets 4.0.0-RC1 - We are working hard on releasing version 4.0.0 too - Camel-Kamelets is not only related to camel k anymore so it could be used with all the Camel's flavours - The Camel-Quarkus work is going ahead following the main camel releases with multiple releases - We released Camel-quarkus 2.16.0 - We released Camel-quarkus 3.0.0-RC1 - We released Camel-quarkus 3.0.0-RC2 - We released Camel-quarkus 3.2.0 - Camel-Kameleon and Camel-Karavan are improving and more and more contributors are continuing to help. We are improving the projects by supporting new features and aligning with LTS releases 3.21.0 as in the last report - Camel Kafka Connector release based on Camel 3.20.6 has been released. - Camel Kafka Connector release based on Camel 3.21.0 has been released. - Work for supporting Camel 4.0.0 is going ahead - Generally speaking we are working on supporting Camel 4 in all the runtimes provided and this is taking a lot of effort. ## Community Health: - 296 issues opened on GitHub, past quarter (15% decrease) and 308 issues closed on GitHub, past quarter (5% decrease): Since we were working on releasing Camel 4.0.0 some of the subprojects using gh issues have seen less focused work, Camel is using JIRA for tracking the work. We focused on 4.0.0 for a long time. - 4992 commits in the past quarter (14% decrease) and 133 code contributors in the past quarter (3% increase): The commits decrease is related to the work done for Camel 4.0.0, at some point in the development we choose to slow down a bit. The camel core team was focusing on Camel 4.x. We saw sporadic contributions from new contributors in subprojects and main Camel. - 1601 PRs opened on GitHub, past quarter (4% decrease) and 1602 PRs closed on GitHub, past quarter (4% deccrease): on some of the subprojects the activity was slowing down for stabilization reasons and for the focus on Camel 4.0.0. - dev@camel.apache.org had a 23% increase in traffic in the past quarter (412 emails compared to 334): There was a spike in the dev ML because of questions and discussions around the development and final decision for Camel 4.0.0 - issues@camel.apache.org had a 56% increase in traffic in the past quarter (2964 emails compared to 1888): There was activity in JIRA mostly for Camel 4 work and cleaning up. We also went through opened and future issues and cleaned up again. - users@camel.apache.org had a 6% increase in traffic in the past quarter (260 emails compared to 243): Some users are starting to ask about migration from 3.x to 4.x, but also from 2.x to 3.x - Note: JIRA statistics are not available in the statistics report provided by reporter. So we cannot comment numbers.
## Description: The mission of Apache Camel is the creation and maintenance of an open-source integration framework based on known Enterprise Integration Patterns. ## Project Status: Project status: Ongoing with high activity Issues: There are no issues requiring board attention at this time. ## Membership Data: Apache Camel was founded 2008-12-17 (14 years ago) There are currently 87 committers and 44 PMC members in this project. The Committer-to-PMC ratio is roughly 2:1. Community changes, past quarter: - Nicolas Filotto was added to the PMC on 2023-04-05 - Christoph Deppisch was added as committer on 2023-05-25 - Marcin Grzejszczak was added as committer on 2023-04-20 ## Project Activity: - We released Camel 3.14.8 - We released Camel 3.18.6 - We released Camel 3.18.7 - We released Camel 3.20.3 - We released Camel 3.20.4 - We released Camel 3.20.5 - We released Camel 4.0.0-M2 - We released Camel 4.0.0-M3 - Note: Camel releases have synchronized releases of Camel-Karaf and Camel-Spring-Boot too for 3.x, while for 4.x only Camel-Spring-Boot is synchronized. - We are near releasing the first release candidate for Camel 4.0.0, it will be done in this month and we plan to complete 4.0.0 release in September. - We are continuing release 3.18.x LTS release train and we are in the process of releasing the next patch release. - We started the release train for 3.20.x LTS, and we are already at the fifth patch release. - We are still supporting Camel 3.14.x, an LTS train, but it's going EOL, so there will be one last release. - For Camel K we are working on releasing the first patch release for 1.12.x, but the focus is on the 2.x work. We are focusing on giving to the community a new experience. - For Camel-Kamelets releases - We released Camel Kameletes 0.9.4 - We released Camel Kameletes 3.20.3 - We released Camel Kameletes 3.20.4 - We released Camel Kameletes 3.20.5 - We released Camel Kamelets 4.0.0-M2 - We released Camel Kamelets 4.0.0-M3 - We are improving the Camel-K experience and Camel Kamelets is already looking at Camel 4 - Camel-Kamelets is not only related to camel k anymore so it could be used with all the Camel's flavours - The Camel-Quarkus work is going ahead following the main camel releases with multiple releases - We released Camel-quarkus 2.13.3 - We released Camel-quarkus 3.0.0-M1 - We released Camel-quarkus 3.0.0-M2 - Camel-Kameleon and Camel-Karavan are improving and more and more contributors are starting to help. We are improving the projects by supporting new features and aligning with LTS releases 3.20.x as in the last report - Camel Kafka Connector release based on Camel 3.20.1 has been released. - We are supporting Camel Kafka Connector aligning it to the Camel Core LTS Releases 3.20.x and we released camel-kafka-connector 3.20.3 - Generally speaking we are working on supporting Camel 4 in all the runtimes provided and this is taking a lot of effort. ## Community Health: - 265 issues opened in JIRA, past quarter (25% decrease) and 284 issues closed in JIRA, past quarter (3% decrease): We are in a stabilization phase for Camel 3.x and the LTS are more or less stable. Mostly new issues are about Camel 4.x, but since we are closing down the work for releasing Camel 4.0.0 there is less new issues opened. - 211 issues opened on GitHub, past quarter (13% decrease) and 203 issues closed on GitHub, past quarter (4% decrease): Since we are working on releasing Camel 4.0.0 some of the subprojects using gh issues are seeing less focused work, Camel is using JIRA for tracking the work - 4648 commits in the past quarter (3% increase) and 120 code contributors in the past quarter (no change): More or less we are stable. The camel core team is focusing on Camel 4.x. We saw sporadic contributions from new contributors. - 1362 PRs opened on GitHub, past quarter (7% increase) and 1366 PRs closed on GitHub, past quarter (7% increase): on some of the subprojects the activity is slowing down for stabilization reasons, we also cleaned up some of the subprojects gh PR and there was a lot of work on Camel-Kamelets from this pov - dev@camel.apache.org had a 32% decrease in traffic in the past quarter (304 emails compared to 441): This is mostly because the work done on Camel 4 side is about moving to support Jakarta, there was some discussions but mostly about releasing. - issues@camel.apache.org had a 0% increase in traffic in the past quarter (1901 emails compared to 1891): We are more or less stable here. There was activity in JIRA mostly for Camel 4 work and cleaning up. - users@camel.apache.org had a 26% decrease in traffic in the past quarter (263 emails compared to 352): The activity is less because of the work on Camel 4 but also because users is asking and discussing on the provided Zulip chat
## Description: The mission of Apache Camel is the creation and maintenance of an open-source integration framework based on known Enterprise Integration Patterns. ## Issues: There are no issues requiring board attention at this time. ## Membership Data: Apache Camel was founded 2008-12-17 (14 years ago) There are currently 85 committers and 43 PMC members in this project. The Committer-to-PMC ratio is roughly 2:1. Community changes, past quarter: - Pasquale Congiusti was added to the PMC on 2023-01-19 - Federico Mariani was added as committer on 2023-01-24 ## Project Activity: - We released Camel 3.18.5 - We released Camel 3.20.0 - We released Camel 3.20.1 - We released Camel 3.20.2 - We released Camel 4.0.0-M1 - Note: Camel releases have synchronized releases of Camel-Karaf and Camel-Spring-Boot too for 3.x, while for 4.x only Camel-Spring-Boot is synchronized. - We started the work through Camel 4, we are already releasing some milestones and we are in good shape. - We are continuing release 3.18.x LTS release train. This will be around for a while. - We started the release train for 3.20.x LTS, and we are already at the second patch release. - We released Camel K 1.10.4, 1.11.0, 1.11.1 and 1.12.0, the first release based on Camel 3.20.x LTS Releases from main Camel project. - We released also Camel K 1.11.0 based on Camel 3.19.0 release (non LTS) - Related to Camel K we have also Camel K Runtime and Camel-Kamelets releases - We released Camel K Runtime 1.15.3 - We released Camel K Runtime 1.15.4 - We released Camel K Runtime 1.17.0 - We released Camel Kameletes 0.9.4 - We released Camel Kameletes 3.20.0 - We released Camel Kameletes 3.20.1 - We released Camel Kamelets 3.20.1.1 - We released Camel Kamelets 3.20.2 - We released Camel Kamelets 4.0.0-M1 - We are improving the Camel-K experience and Camel Kamelets is already looking at Camel 4 - The Camel-Quarkus work is going ahead following the main camel releases with multiple releases - We released Camel-quarkus 2.13.2 - We released Camel-quarkus 2.16.0 - Camel-Kameleon and Camel-Karavan are improving and more and more contributors are starting to help. We are improving the projects by supporting new features and aligning with LTS releases 3.20.x - Camel Kafka Connector release based on Camel 3.20.1 has been released. - We are supporting Camel Kafka Connector aligning it to the Camel Core LTS Releases 3.20.x ## Community Health: - 310 issues opened in JIRA, past quarter (6% decrease) and 249 issues closed in JIRA, past quarter (11% decrease): We are in a stabilization phase for Camel 3.x and the LTS are more or less stable. Also with the new 3.20.x release train for LTS, we are going to improve the stability. Mostly new issues are about Camel 4.x - 213 issues opened on GitHub, past quarter (2% increase) and 194 issues closed on GitHub, past quarter (20% increase): We are adding new issues for aligning to Camel 4.x Camel/Camel-Karaf/Camel-Spring-Boot. There are some more issues opened on the Camel K subprojects, since the contributors and users are increasing. - 3919 commits in the past quarter (8% increase) and 120 code contributors in the past quarter (4% decrease): More or less we are stable. We have some new contributors coming from different subprojects and related to some documentation activities and bug fixes. Camel 4.x is mostly a work done by the Camel core team. - 1113 PRs opened on GitHub, past quarter (5% decrease) and 1113 PRs closed on GitHub, past quarter (5% decrease): on some of the subprojects the activity is slowing down for stabilization reasons, on some other like Camel K and Camel Quarkus there is so much activity for aligning to new Camel Releases for Camel 4.x - From this report the dev, users and issues mailing lists have been omitted because the ASF project statistics page for Apache Camel is not up-to-date
## Description: The mission of Apache Camel is the creation and maintenance of an open-source integration framework based on known Enterprise Integration Patterns. ## Issues: There are no issues requiring board attention at this time. ## Membership Data: Apache Camel was founded 2008-12-17 (14 years ago) There are currently 84 committers and 42 PMC members in this project. The Committer-to-PMC ratio is 2:1. Community changes, past quarter: - Jeremy Ross was added to the PMC on 2022-10-27 - Claudio Miranda was added as committer on 2022-09-28 - Rhuan Rocha was added as committer on 2022-10-21 - Thomas Cunningham was added as committer on 2022-09-21 ## Project Activity: - We released Camel 3.14.6 - We released Camel 3.14.7 - We released Camel 3.18.3 - We released Camel 3.18.4 - We released Camel 3.19.0 - Note: Camel releases have synchronized releases of Camel-Karaf and Camel-Spring-Boot too - We released 3.14.6 and 3.14.7: This is an LTS release train. We are going to continue releasing 3.14.x. - We are continuing release 3.18.x LTS release train. This will be around for a while. - We are going to release a new LTS release 3.20.0, before the end of the year. - We are also drafting the Camel 4.x roadmap. We are going to publish a roadmap blog post about by the end of December or beginning of 2023. - We released Camel K 1.10.1, 1.10.2 and 1.10.3, based on the 3.18.x LTS Releases from main Camel project. - We released also Camel K 1.11.0 based on Camel 3.19.0 release (non LTS) - Related to Camel K we have also Camel K Runtime and Camel-Kamelets releases - We released Camel K Runtime 1.15.0 - We released Camel K Runtime 1.15.1 - We released Camel K Runtime 1.15.2 - We released Camel K Runtime 1.16.0 - We released Camel Kameletes 0.9.1 - We released Camel Kameletes 0.9.2 - We released Camel Kameletes 0.9.3 - We released Camel Kameletes 0.10.0 - We are improving the Camel-K experience and we are increasing the Kamelets number, to provide new way of composing integrations, we are also looking at supporting multiple Kamelets Catalog - The Camel-Quarkus work is going ahead following the main camel releases with multiple releases - We released Camel-quarkus 2.12.0 - We released Camel-quarkus 2.13.0 - We released Camel-quarkus 2.13.1 - We released Camel-quarkus 2.14.0 - We released Camel-quarkus 2.15.0 - Camel-Kameleon and Camel-Karavan are improving and more and more contributors are starting to help. We are improving the projects by supporting new features and aligning with LTS releases. - Camel Kafka Connector release based on Camel 3.19.0 is on vote these days. - We are supporting Camel Kafka Connector aligning it to the Camel Core LTS Releases. ## Community Health: - dev@camel.apache.org had a 4% increase in traffic in the past quarter (454 emails compared to 436): There is a little increase because we had some feedback from user migrating from old Camel 3.x to latest LTS 3.18.x. Also some report when upgrading from older version of 3.18.x to newer. - issues@camel.apache.org had a 22% increase in traffic in the past quarter (2125 emails compared to 1734): This is related to some new features we are adding to the development release of Camel 3 torwards 3.18.x LTS and for 3.19.x and 3.20.0 (soon to be released) - users@camel.apache.org had a 5% decrease in traffic in the past quarter (315 emails compared to 330): The situation is more or less the same of last quarter, the 3.14.x and 3.18.x LTS are stable so we are having less discussions around this. - 294 issues opened in JIRA, past quarter (6% decrease) and 248 issues closed in JIRA, past quarter (61% decrease): We are in a stabilization phase for Camel 3.18.x and the LTS are more or less stable. In the last report we were doing some cleanups of the old JIRAs, by closing or abandoning some of them, that's the main reason for the decrease. - 191 issues opened on GitHub, past quarter (-9% change) and 146 issues closed on GitHub, past quarter (-34% change): We are slowing down on issue opened on camel-kamelets for example and we are looking at backlog. Note: Github issues are related to all the subprojects different from Camel/Camel-Karaf/Camel-Spring-Boot. There are some more issues opened on the Camel K subprojects, since the contributors and users are increasing. - 3362 commits in the past quarter (1% decrease) and 132 code contributors in the past quarter (10% increase): More or less we are stable. We have some new contributors coming from different subprojects and related to some documentation activities and bug fixes. - 1087 PRs opened on GitHub, past quarter (6% decrease) and 1087 PRs closed on GitHub, past quarter (6% decrease): on some of the subprojects the activity is slowing down for stabilization reasons, on some other like Camel K and Camel Quarkus there is so much activity for aligning to new Camel Releases from LTS Train.
## Description: The mission of Apache Camel is the creation and maintenance of an open-source integration framework based on known Enterprise Integration Patterns. ## Issues: There are no issues requiring board attention at this time. ## Membership Data: Apache Camel was founded 2008-12-17 (14 years ago) There are currently 81 committers and 41 PMC members in this project. The Committer-to-PMC ratio is roughly 2:1. Community changes, past quarter: - No new PMC members. Last addition was Antonin Stefanutti on 2022-01-28. - No new committers. Last addition was Nicolas Filotto on 2022-03-01. ## Project Activity: - We released Camel 3.14.4 - We released Camel 3.14.5 - We released Camel 3.18.0 - We released Camel 3.18.1 - We released Camel 3.18.2 - Note: Camel releases have synchronized releases of Camel-Karaf and Camel-Spring-Boot too - We released 3.14.4 and 3.14.5: This is an LTS release train. We are going to continue releasing 3.14.x. - We released a new LTS release train, with 3.18.x. We are already releasing new patch releases for this LTS release train and we're planning to do so for one year. - We released Camel K 1.10.0 - Related to Camel K we have also Camel K Runtime and Camel-Kamelets releases - We released Camel K Runtime 1.14.0 - We released Camel Kameletes 0.9.0 - We are improving the Camel-K experience and we are increasing the Kamelets number, to provide new way of composing integrations. - The Camel-Quarkus work is going ahead following the main camel releases with multiple releases - We released Camel-quarkus 2.7.2 - We released Camel-quarkus 2.10.0 - We released Camel-quarkus 2.11.0 - Camel-Kameleon and Camel-Karavan are improving and there is a raise of interest in the community. We are improving the projects by supporting new features and aligning with Camel 3.18.x releases. - Apache Camel was present at ApacheCon Asia in multiple presentations of integration track. - Apache Camel will be present at ApacheCon NA with multiple presentations in the Camel on Cloud track. ## Community Health: - dev@camel.apache.org had a 4% increase in traffic in the past quarter (454 emails compared to 436): There is a little increase because we had some feedback from user migrating from old Camel 3.x to latest LTS 3.18.x. - issues@camel.apache.org had a 22% increase in traffic in the past quarter (2125 emails compared to 1734): This is related to some new features we are adding to the development release of Camel 3 torwards 3.18.0 LTS. - users@camel.apache.org had a 5% decrease in traffic in the past quarter (315 emails compared to 330): The situation is more or less the same of last quarter, the 3.14.x LTS is solid so we have probably less traffic and less feedback. - 287 issues opened in JIRA, past quarter (28% decrease) and 611 issues closed in JIRA, past quarter (73% increase): We are in a stabilization phase for Camel 3.18.x and the LTS are more or less stable, so there is less activity on JIRA. The increase in closed issues is related to some cleanup activities of JIRA during this quarter. - 201 issues opened on GitHub, past quarter (-13% change) and 190 issues closed on GitHub, past quarter (-19% change): We are slowing down on issue opened on camel-kamelets for example and we are looking at backlog. Note: Github issues are related to all the subprojects different from Camel/Camel-Karaf/Camel-Spring-Boot - 3113 commits in the past quarter (14% decrease) and 121 code contributors in the past quarter (3% decrease): As said above the camel codebase is stabilizing around the LTS 3.18.x, so we are focusing a bit more on stabilizing the codebase but also introducing new features with a slower cadence - 1068 PRs opened on GitHub, past quarter (10% decrease) and 1073 PRs closed on GitHub, past quarter (8% decrease): on some of the subprojects the activity is slowing down for stabilization reasons, so there are less PRs. This should change a bit in the next quarter since we are going to align all the subprojects to 3.18.x LTS release of main Camel project.
## Description: The mission of Apache Camel is the creation and maintenance of an open-source integration framework based on known Enterprise Integration Patterns. ## Issues: There are no issues requiring board attention at this time. ## Membership Data: Apache Camel was founded 2008-12-17 (13 years ago) There are currently 81 committers and 41 PMC members in this project. The Committer-to-PMC ratio is roughly 2:1. Community changes, past quarter: - No new PMC members. Last addition was Antonin Stefanutti on 2022-01-28. - No new committers. Last addition was Nicolas Filotto on 2022-03-01. ## Project Activity: - We released Camel 3.11.6 - We released Camel 3.11.7 - We released Camel 3.14.2 - We released Camel 3.14.3 - We released Camel 3.16.0 - We released Camel 3.17.0 - Note: Camel releases have synchronized releases of Camel-Karaf and Camel-Spring-Boot too - We released 3.14.2 and 3.14.3: This is an LTS release train. We are going to continue releasing 3.14.x, while we are preparing to the next LTS 3.18.0. We are working hard on 3.18.0 release, with a lot of new features. - We released Camel K 1.9.0 - We released Camel K 1.9.1 - We released Camel K 1.9.2 - Related to Camel K we have also Camel K Runtime releases - We released Camel K Runtime 1.13.0 - We are improving the Camel-K experience and we are increasing the Kamelets number. - The Camel-Quarkus work is going ahead following the main camel releases with multiple releases - We released Camel-quarkus 2.7.1 - We released Camel-quarkus 2.8.0 - We released Camel-quarkus 2.9.0 - Camel-Kameleon and Camel-Karavan are creating a lot of interest in the community and we are seeing a lot of interactions. We are improving the projects by supporting new features and aligning with LTS releases. ## Community Health: - dev@camel.apache.org had a 4% increase in traffic in the past quarter (454 emails compared to 436): There is a little increase because we had some feedback from user migrating from old Camel 3.x to latest LTS 3.14.x and also because of some queries about Camel K - issues@camel.apache.org had a 22% increase in traffic in the past quarter (2125 emails compared to 1734): This is related to some new features we are adding to the development release of Camel 3 torwards 3.18.0 LTS. - users@camel.apache.org had a 5% decrease in traffic in the past quarter (315 emails compared to 330): The situation is more or less the same of last quarter, the 3.14.x LTS is solid so we have probably less traffic and less feedback. - 379 issues opened in JIRA, past quarter (21% decrease) and 325 issues closed in JIRA, past quarter (27% decrease): We are in a stabilization phase for Camel 3.18.0 and the LTS are more or less stable, so there is less activity on JIRA. Note: Jira issues are related to Camel/Camel-Karaf and Camel-Spring-Boot projects - 201 issues opened on GitHub, past quarter (-13% change) and 190 issues closed on GitHub, past quarter (-19% change): We are slowing down on issue opened on camel-kamelets for example and we are looking at backlog. Note: Github issues are related to all the subprojects different from Camel/Camel-Karaf/Camel-Spring-Boot - 3282 commits in the past quarter (29% decrease) and 121 code contributors in the past quarter (5% increase): As said above the camel codebase is stabilizing around the next LTS 3.18.0, so there are probably less commits. - 1054 PRs opened on GitHub, past quarter (18% decrease) and 1042 PRs closed on GitHub, past quarter (19% decrease): on some of the subprojects the activity is slowing down for stabilization reasons, so there are less PRs.
## Description: The mission of Apache Camel is the creation and maintenance of an open-source integration framework based on known Enterprise Integration Patterns. ## Issues: There are no issues requiring board attention at this time. ## Membership Data: Apache Camel was founded 2008-12-17 (13 years ago) There are currently 81 committers and 41 PMC members in this project. The Committer-to-PMC ratio is roughly 2:1. Community changes, past quarter: - Antonin Stefanutti was added to the PMC on 2022-01-28 - Otavio Rodolfo Piske was added to the PMC on 2022-01-21 - Zineb Bendhiba was added to the PMC on 2022-01-24 - Karen Lease was added as committer on 2022-01-24 - Nicolas Filotto was added as committer on 2022-03-01 ## Project Activity: - We released Camel 3.7.7 - We released Camel 3.11.5 - We released Camel 3.14.0 - We released Camel 3.14.1 - We released Camel 3.15.0 - Note: Camel releases have synchronized releases of Camel-Karaf and Camel-Spring-Boot too - We released 3.14.0 and 3.14.1: This is an LTS release train. We are going to continue releasing 3.14.x and 3.11.x, while we are preparing to the next LTS 3.17.x. We are working hard on 3.16.0 release, with a lot of new features. - We released Camel K 1.8.0 - We released Camel K 1.8.1 - We released Camel K 1.8.2 - Related to Camel K we have also Camel K Runtime releases - We released Camel K Runtime 1.11.0 - We released Camel K Runtime 1.12.0 - We are improving the Camel-K experience and we are expanding and improving the Kamelet concept, by introducing more Kameletes to the provided catalog. The amount of Kamelets is increasing in a really impressive way. We are also improving the CLI experience and we are working on involving more contributors by publishing a roadmap for 2022 - The Camel-Quarkus work is going ahead following the main camel releases with multiple releases - We released Camel-quarkus 2.2.1 - We released Camel-quarkus 2.5.0 - We released Camel-quarkus 2.6.0 - We released Camel-quarkus 2.7.0 - On the Camel-Kafka-Connector side we released - 1.0.0 release based on Kamelets - Camel-Kameleon and Camel-Karavan are creating a lot of interest in the community and we are seeing a lot of interactions. ## Community Health: - dev@camel.apache.org had a 4% increase in traffic in the past quarter (454 emails compared to 436): There is a little increase because we had some feedback from user migrating from old Camel 3.x to latest LTS 3.14.x and also because of some queries about Camel K - issues@camel.apache.org had a 22% increase in traffic in the past quarter (2125 emails compared to 1734): This is related to some new features we are adding to the development release of Camel 3. - users@camel.apache.org had a 5% decrease in traffic in the past quarter (315 emails compared to 330): The situation is more or less the same of last quarter, the 3.14.x LTS is solid so we have probably less traffic - 461 issues opened in JIRA, past quarter (32% increase) and 411 issues closed in JIRA, past quarter (30% increase): As reported we are working hard on development release and we are also looking at backlog. Note: Jira issues are related to Camel/Camel-Karaf and Camel-Spring-Boot projects - 224 issues opened on GitHub, past quarter (-5% change) and 219 issues closed on GitHub, past quarter (no change): More or less the situation is similar to the last quarter. We have a lot of issues on Github opened for camel-kamelets. Note: Github issues are related to all the subprojects different from Camel/Camel-Karaf/Camel-Spring-Boot - 4105 commits in the past quarter (21% increase) and 115 code contributors in the past quarter (-2% change): the core Camel team is working on new features on the codebase so there is an increase in number of commits, contributions related to documentation and website is increasing. - 1142 PRs opened on GitHub, past quarter (23% increase) and 1147 PRs closed on GitHub, past quarter (24% increase): We have a lot of work done on all the subprojects, so we see a lot of PRs coming from new contributors about documentation but also new features.
## Description: The mission of Apache Camel is the creation and maintenance of an open-source integration framework based on known Enterprise Integration Patterns. ## Issues: There are no issues requiring board attention at this time. ## Membership Data: Apache Camel was founded 2008-12-17 (13 years ago) There are currently 79 committers and 38 PMC members in this project. The Committer-to-PMC ratio is roughly 5:3. Community changes, past quarter: - No new PMC members. Last addition was James Netherton on 2021-04-12. - No new committers. Last addition was Marat Gubaidullin on 2021-07-29. ## Project Activity: - We released Camel 3.7.6 - We released Camel 3.11.2 - We released Camel 3.11.3 - We released Camel 3.11.4 - We released Camel 3.12.0 - We released Camel 3.13.0 - We released 3.11.0 release: this releases train is the LTS release with 3.7.x. We're going to stop releasing 3.7.x releases and going ahead with two LTS 3.11.x and 3.14.x. - We are going to release 3.14.0 in the Middle of December: this release will be the last supporting Java 8, so we're going to support it for 2 years instead of 1. intermediate development releases. - We released Camel K 1.6.1 - We released Camel K 1.7.0 - We are improving the Camel-K experience and we are expanding and improving the Kamelet concept, by introducing more Kameletes to the provided catalog. The amount of Kamelets is increasing in a really impressive way. - The Camel-Quarkus work is going ahead following the main camel releases with multiple releases - We released Camel-quarkus 2.3.0 - We released Camel-quarkus 2.4.0 - We released Camel-quarkus 2.5.0 - We are continuing working on the Camel-kafka-connector for basing it on Kamelet concept - 0.11.0 on 21 Sep 2021 - We are going to release 1.0 based on 3.14.0 LTS soon, probably in January. - We added two more projects to the ecosystem - https://github.com/apache/camel-kameleon - https://github.com/apache/camel-karavan ## Community Health: - dev@camel.apache.org had a 45% increase in traffic in the past quarter (501 emails compared to 344): This increase is related to 3.14.x LTS release and migration effort and some camel-k discussion. - issues@camel.apache.org had a 58% increase in traffic in the past quarter (2360 emails compared to 1488): We are working a lot on JIRA to clean up and setup everything related to 3.14.0 release, also we have some issues and discussion around the website. - users@camel.apache.org had a 9% increase in traffic in the past quarter (326 emails compared to 299): the situation is more or less the same of the last quarter, the increase is probably related to users moving from Camel 2.x and 3.x - 212 issues opened in JIRA, past quarter (-42% decrease) and 209 issues closed in JIRA, past quarter (-42% decrease): as reported above, the situation is stable. The activity related to Camel 2 is near to zero and we are focusing on old opened issues. We are getting feedback about new LTS releases, but many of them are coming from other channel like the zulip chat. - 3122 commits in the past quarter (7% decrease) and 119 code contributors in the past quarter (4% decrease): the core Camel team is stabilizing the codebase so there is a little decrease in number of commits, contributions related to documentation and website is increasing. We are much more focusing on giving to the community something stable with 3.14.0 and when it will be released we'll restart to innovate with the next dev releases. - 875 PRs opened on GitHub, past quarter (-7% decrease) and 872 PRs closed on GitHub, past quarter (-8% decrease): the code stabilization and less work on the camel kafka connector side explain the decrease in number of PRs open and closed. Camel-kafka-connector still needs to be aligned to the new LTS with Kamelets support, but in the next quarter we'll release it aligned with the latest LTS. - 210 issues opened on GitHub, past quarter (25% decrease) and 211 issues closed on GitHub, past quarter (22% decrease): It's always related to camel-kamelets repository. There were a lot of issues opened there in the last two quarters.
## Description: The mission of Apache Camel is the creation and maintenance of an open-source integration framework based on known Enterprise Integration Patterns. ## Issues: There are no issues requiring board attention at this time ## Membership Data: Apache Camel was founded 2008-12-17 (13 years ago) There are currently 79 committers and 38 PMC members in this project. The Committer-to-PMC ratio is roughly 5:3. Community changes, past quarter: - No new PMC members. Last addition was James Netherton on 2021-04-12. - Marat Gubaidullin was added as committer on 2021-07-29 - Pasquale Congiusti was added as committer on 2021-07-22 - Zheng Feng was added as committer on 2021-06-30 ## Project Activity: - We released Camel 3.7.5 - We released Camel 3.4.6 - We released Camel 3.11.0 - We released Camel 3.11.1 - The Camel 3.7.x releases are part of the second LTS for Camel 3. We are planning to support 3.7.x for one year. We are releasing these LTS with bug fixes - We released 3.11.0 release: this release is the LTS release with 3.7.x. We're going to stop releasing 3.4.x releases and going ahead with those two LTS. We are already working on the new LTS which will be 3.14.0, with two intermediate development releases. - We released Camel K 1.4.1 - We released Camel K 1.5.0 - We released Camel K 1.5.1 - We released Camel K 1.6.0 - We are improving the Camel-K experience and we are expanding and improving the Kamelet concept, by introducing more Kameletes to the provided catalog - The Camel-Quarkus work is going ahead following the main camel releases with multiple releases - We released Camel-quarkus 2.0.0-M1 - We released Camel-quarkus 2.0.0-M2 - We released Camel-quarkus 2.0.0 - We released Camel-quarkus 2.1.0 - We released Camel-quarkus 2.2.0 - We are continuing working on the Camel-kafka-connector for basing it on Kamelet concept - 0.10.1 on 23 May 2021 - The 0.7.x releases are based on the second LTS of main Camel, 3.7.x - We are working for supporting the next Camel LTS with camel-kafka-connector too - We'll be featured on the Integration track at ApacheCon @Home 2021 and ApacheCon Asia 2021. We received 22 submissions and selected 14 for a two day presence at ApacheCon @Home 2021, first day focusing on Camel, second day focusing on other ASF projects in the software integration ecosystem. ## Community Health: - dev@camel.apache.org had a 8% increase in traffic in the past quarter (386 emails compared to 356): This increase is related to 3.11.x LTS release and migration effort. - issues@camel.apache.org had a 30% decrease in traffic in the past quarter (1616 emails compared to 2280): We are focusing on fixing issues for 3.11.x. - users@camel.apache.org had a 6% decrease in traffic in the past quarter (311 emails compared to 329): the situation is more or less the same of the last quarter, the decrease is probably for the summer time. - 212 issues opened in JIRA, past quarter (-42% decrease) and 209 issues closed in JIRA, past quarter (-42% decrease): as reported above, the situation is stable. The activity related to Camel 2 is near to zero and we are focusing on old opened issues. We are getting feedback about new LTS releases, but many of them are coming from other channel like the zulip chat. - 3053 commits in the past quarter (36% decrease) and 123 code contributors in the past quarter (1% increase): the core Camel team is stabilizing the codebase so there is a little decrease in number of commits, contributions related to documentation and website is increasing. This is related to summer time probably, but also by the fact we are focusing on stabilizing the LTS and codebase is more or less stable at the moment. - 851 PRs opened on GitHub, past quarter (-20% decrease) and 851 PRs closed on GitHub, past quarter (-19% decrease): the code stabilization and less work on the camel kafka connector side explain the decrease in number of PRs open and closed. Camel-kafka-connector still needs to be aligned to the new LTS with Kamelets support. - 251 issues opened on GitHub, past quarter (38% decrease) and 248 issues closed on GitHub, past quarter (24% decrease): The camel-kamelets repository last quarter gave a boost to the github issues, now it's much more stable.
## Description: The mission of Apache Camel is the creation and maintenance of an open-source integration framework based on known Enterprise Integration Patterns. ## Issues: There are no issues requiring board attention at this time ## Membership Data: Apache Camel was founded 2008-12-17 (12 years ago) There are currently 76 committers and 38 PMC members in this project. The Committer-to-PMC ratio is 2:1. Community changes, past quarter: - James Netherton was added to the PMC on 2021-04-12 - Zineb Bendhiba was added as committer on 2021-03-11 ## Project Activity: - We released Camel 3.7.3 on 2021-03-10. - We released Camel 3.9.0 on 2021-03-28. - We released Camel 2.25.4 on 2021-05-28. - We released Camel 3.7.4 on 2021-05-03. - We released Camel 3.10.0 on 2021-05-20. - The Camel 3.7.x releases are part of the second LTS for Camel 3. We are planning to support 3.7.x for one year. We are releasing these LTS with bug fixes - We are already working on 3.11.0 release: this release will be the prelude of the first LTS release of 2021. Originally we would like to have 3.10.0 as LTS, but it turns out more work would be needed, so we decide to go with 3.10.0 as development release and 3.11.0 as LTS immediately after. We're almost ready to release. - We released Camel-K 1.4.0 on 2021-04-17 - We are improving the Camel-K experience and we are expanding and improving the Kamelet concept, by introducing the camel-kamelets repository dedicated to this particular Camel aspect. - The Camel-Quarkus work is going ahead following the main camel releases with 2 versions this quarter - We released Camel-quarkus-1.8.0 on 2021-03-29. - We released Camel-quarkus 1.8.1 on 2021-04-06. - We are continuing working on the Camel-kafka-connector project and we released three versions of it - 0.7.3 on 13 Mar 2021 - 0.9.0 on 31 Mar 2021 - 0.10.0 on 23 May 2021 - The 0.7.x releases are based on the second LTS of main Camel, 3.7.x - We are working for supporting the next Camel LTS with camel-kafka-connector too - We'll be featured on the Integration track at ApacheCon @Home 2021 and ApacheCon Asia 2021. We received 22 submissions and selected 14 for a two day presence at ApacheCon @Home 2021, first day focusing on Camel, second day focusing on other ASF projects in the software integration ecosystem. For ApacheCon Asia 2021 we selected all 8 submissions, also for two days on the Integration track, 6 out of 8 featuring Camel. Schedule for ApacheCon Asia 2021 has been published[1], the schedule for ApacheCon @Home 2021 has been submitted and will be published soon. [1] https://apachecon.com/acasia2021/tracks/integration.html ## Community Health: - dev@camel.apache.org had a 19% decrease in traffic in the past quarter (375 emails compared to 459): This decrease is related to the stabilization of the code base preparing for the next LTS 3.11.0. - issues@camel.apache.org had a 22% increase in traffic in the past quarter (2521 emails compared to 2052): This increase is related to the fact we are getting more feedback on the development releases torward the next LTS release. We are creating new issues for the third LTS release, but we are also starting to see issues for 3.7.x. - users@camel.apache.org had a 13% increase in traffic in the past quarter (356 emails compared to 315): the increase is related to people switching from Camel 2 to Camel 3, since we are already at the second LTS, so we are looking at discussions about this and also issues with Camel 3. This is also related to people moving from second LTS to a development release for the next LTS. This decrease could also be related to the switch to Zulip chat for daily communications between users, committers etc. We have an average of 250/300 messages every day. - 369 issues opened in JIRA, past quarter (-4% decrease) and 356 issues closed in JIRA, past quarter (-1% decrease): as reported above, the situation is stable. We are facing issues and improvements for 3.11 and old development releases for the next LTS, but also starting to see new issues for Camel 3 and the 3.7.x LTS releases. The activity related to Camel 2 is near to zero, even though we are still see people asking for issues and how to migrate. - 4774 commits in the past quarter (4% decrease) and 120 code contributors in the past quarter (1% increase): the core Camel team is stabilizing the codebase so there is a little decrease in number of commits, contributions related to documentation and website is increasing. In this quarter we were much more stable in this area. - 979 PRs opened on GitHub, past quarter (-24% decrease) and 972 PRs closed on GitHub, past quarter (-24% decrease): the code stabilization and also a little less work on the camel kafka connector side explain the decrease in number of PRs open and closed. We expect this stat to increase again once we release the next LTS. - 365 issues opened on GitHub, past quarter (9% increase) and 286 issues closed on GitHub, past quarter (5% increase): There is a new addition in terms of repositories which is the camel-kamelets repository, where we opened and closed a lot of new GH issues
## Description: The mission of Apache Camel is the creation and maintenance of an open-source integration framework based on known Enterprise Integration Patterns. ## Issues: there are no issues requiring board attention at this time ## Membership Data: Apache Camel was founded 2008-12-17 (12 years ago) There are currently 75 committers and 37 PMC members in this project. The Committer-to-PMC ratio is roughly 5:3. Community changes, past quarter: - Gazda was added to the PMC on 2021-02-19 - Bob Paulin was added as committer on 2021-02-16 - Jeremy Ross was added as committer on 2020-12-15 - Jiří Ondrušek was added as committer on 2020-12-15 ## Project Activity: - We released Camel 3.8.0 on 2021-02-13. - We released Camel 3.7.2 on 2021-02-08. - We released Camel 3.7.1 on 2021-01-21. - We released Camel 3.7.0 on 2020-12-16. - We released Camel 3.4.5 on 2020-12-23. - We released Camel 2.25.3 on 2020-12-24. - The Camel 3.7.x releases are part of the second LTS for Camel 3. We are planning to support 3.7.x for one year. The release 3.7.3 for 3.7.x LTS is on vote at the time of writing this report. - We are already working on 3.9.0 release: this release will be the prelude of the first LTS release of 2021, 3.10.0. - We released Camel-K 1.3.0 on 2020-12-22 - We released Camel-K 1.3.1 in 2021-02-01 - We are improving the Camel-K experience and we introduce the Kamelet concept, while pushing the project ahead, by aligning to the Camel main releases. - We are continuing supporting Camel-Quarkus by releasing 3 versions this quarter - We released camel-quarkus-1.7.0 on 2021-02-22 - We released camel-quarkus-1.6.0 on 2021-01-18. - We released camel-quarkus-1.5.0 on 2020-12-18. - We are continuing working on the Camel-kafka-connector project and we released four versions of it - 0.7.0 on 21 Dec 2020 - 0.7.1 on 24 Jan 2021 - 0.7.2 on 14 Feb 2021 - 0.8.0 on 23 Feb 2021 - The 0.7.x releases are based on the second LTS of main Camel, 3.7.x - At the time of writing this report, we are preparing to release 0.7.3, based on Camel 3.7.3 ## Community Health: - dev@camel.apache.org had a 39% increase in traffic in the past quarter (468 emails compared to 336): This increase is related to some technical discussion around what to do with some new ideas into the Camel project. Also we started to have feedback from people using the second LTS releases of Camel 3. - issues@camel.apache.org had a 3% decrease in traffic in the past quarter (2300 emails compared to 2358): Here we are more or less at the same level of last report. We are creating new issues for the third LTS release, but we are also starting to see issues for 3.7.x. So the situation is stable. - users@camel.apache.org had a 13% increase in traffic in the past quarter (346 emails compared to 306): the increase is related to people switching from Camel 2 to Camel 3, since we are already at the second LTS, so we are looking at discussions about this and also issues with Camel 3. - 387 issues opened in JIRA, past quarter (-4% decrease) and 356 issues closed in JIRA, past quarter (-2% decrease): as reporte above, the situation is stable. We are facing issues and improvements for 3.10, but also starting to see new issues for Camel 3 and the 3.7.x LTS releases. The activity related to Camel 2 is near to zero, even though we are still see people asking for issues. - 4974 commits in the past quarter (6% increase) and 117 code contributors in the past quarter (-23% decrease): the core work of Camel 3 is more or less done by the same number of contributors, the fact is the past we had some contributions related to documentation and website. In this quarter we were much more stable in this area. - 1284 PRs opened on GitHub, past quarter (-13% decrease) and 1276 PRs closed on GitHub, past quarter (-13% decrease): some of the PRs in the past quarter were coming from bot and gh action, with the new security policies adopted some of this work needs to be done by hands. - 332 issues opened on GitHub, past quarter (-1% decrease) and 270 issues closed on GitHub, past quarter (-15% decrease): the number of issues is the same but we closed less backlog issues this quarter.
## Description: The mission of Apache Camel is the creation and maintenance of an open-source integration framework based on known Enterprise Integration Patterns. ## Issues: there are no issues requiring board attention at this time ## Membership Data: Apache Camel was founded 2008-12-17 (12 years ago) There are currently 72 committers and 36 PMC members in this project. The Committer-to-PMC ratio is 2:1. Community changes, past quarter: - No new PMC members. Last addition was Omar Al-Safi on 2020-06-01. - No new committers. Last addition was Otavio Rodolfo Piske on 2020-08-31. ## Project Activity: - We released Apache Camel 3.4.3 on 2020-08-11. - We released Apache Camel 3.4.4 on 2020-09-28. - We released Apache Camel 3.5.0 on 2020-09-01. - We released Apache Camel 3.6.0 on 2020-10-20. - The 3.4.x series of releases are part of the LTS on-going effort we are doing, so we are following this patch releases series. We're going to release 3.4.5 in the beginning of 2021 - The new LTS release will be the 3.7.0 which will be released in December. - We are preparing the next patch release for 2.25.x, the 2.25.3 - We released Camel-K 1.2.0 on 2020-10-08 - We released Camel-K 1.2.1 on 2020-11-24 - We are improving the support of Camel 3 and improving the Camel-K experience - We are continuing supporting Camel-Quarkus by releasing 4 versions this quarter - We released the following Camel-Quarkus versions: - 1.1.0 on 9 Sep 2020 - 1.2.0 on 15 Oct 2020 - 1.3.0 on 17 Oct 2020 - 1.4.0 on 19 Nov 2020 - We are continuing working on the Camel-kafka-connector project and we released four versions of it - 0.4.4 on 11 Oct 2020 - 0.5.0 on 09 Sep 2020 - 0.6.0 on 24 Oct 2020 - 0.6.1 on 27 Nov 2020 - The 0.4.4 release is based on Camel 3.4.4 LTS release - We are working on 0.7.x based on 3.7.0 and we'll release once Camel 3.7.0 will be released - We moved our main chat from Gitter to Zulip ## Community Health: - dev@camel.apache.org had a 2% increase in traffic in the past quarter (404 emails compared to 393): This is mainly related to the fact we released the LTS 3.4.x and the little increase in the traffic is because we are about to release the second LTS train - issues@camel.apache.org had a 7% decrease in traffic in the past quarter (2531 emails compared to 2698): Camel 3 is still in his early adoption so not all the users are moving from the 2.x version, but many of them are beginning. We are focusing on new features but also on backlog about stuff we'd like to have in 3.x, but we weren't able to complete - users@camel.apache.org had a 1% increase in traffic in the past quarter (335 emails compared to 330): This is more or less constant, people are starting to ask about Camel 3 and migration from Camel 2. - 407 issues opened in JIRA, past quarter (15% increase) 351 issues closed in JIRA, past quarter (no change) This is related to the new features we'd like to introduce in 3.7.0 and second LTS, in particular some stuff comes from the subprojects - 4650 commits in the past quarter (18% increase) 150 code contributors in the past quarter (23% increase) We saw an increase in new contributors related mainly to documentation and migration, for the commits some of them are related to new features and code generation - 1484 PRs opened on GitHub, past quarter (49% increase) 1477 PRs closed on GitHub, past quarter (47% increase) A Lot of new PRs are coming from some bot we are using. Related to the auto-generation of documentation mainly - 371 issues opened on GitHub, past quarter (-2% decrease) 319 issues closed on GitHub, past quarter (6% increase) We were closing some backlog github issues especially in subprojects
## Description: The mission of Apache Camel is the creation and maintenance of an open-source integration framework based on known Enterprise Integration Patterns. ## Issues: there are no issues requiring board attention at this time ## Membership Data: Apache Camel was founded 2008-12-17 (12 years ago) There are currently 72 committers and 36 PMC members in this project. The Committer-to-PMC ratio is 2:1. Community changes, past quarter: - No new PMC members. Last addition was Omar Al-Safi on 2020-06-01. - Maria Arias de Reyna Dominguez was added as committer on 2020-08-08 - Otavio Rodolfo Piske was added as committer on 2020-08-31 ## Project Activity: - We released Apache Camel 3.4.0 on 2020-06-18. - We released Apache Camel 3.4.1 on 2020-07-16. - We released Apache Camel 3.4.2 on 2020-07-22. - We released Apache Camel 3.5.0 on 2020-09-01. - We released Apache Camel 2.25.2 on 2020-07-21. - The 3.4.x series of releases are part of the LTS on-going effort we are doing, so we are following this patch releases series - At the same time we are working on new innovating releases in 3.6.0 and sequent, until the next LTS which will be released in December. - We are preparing the next patch release for 2.25.x - We released Camel-K-Runtime 1.4.0, 1.4.1 and 1.5.0 respectively on 13 Jul 2020, 21 Jul 2020 and 4 Aug 2020 - We released Camel-K 1.0.1 on 25 Jun 2020 - We released Camel-K 1.1.0 on 21 Jul 2020 - We are improving the support of Camel 3 and improving the Camel-K experience - We are continuing supporting Camel-Quarkus by releasing 3 versions this month - We released the following Camel-Quarkus versions: - 1.0.0-CR3 on 3 Jul 2020 - 1.0.0 on 10 Aug 2020 - 1.0.1 on 26 Aug 2020 - We are continuing working on the Camel-kafka-connector project and we released two version of it - 0.3.0 on 17 Jun 2020 - 0.4.0 on 30 Jul 2020 - The 0.4.x will be based on LTS releases of Camel, so we are expecting to release some patch releases - We are working on 0.5.x based on 3.5.0 and we'll release it soon - The Camel website is going through a revamp with a new fresh and modern style and the community seems to be happy about it. - This is the complete releases list - Apache Camel 3.4.0 on 2020-06-18. - Apache Camel 3.4.1 on 2020-07-16. - Apache Camel 3.4.2 on 2020-07-22. - Apache Camel 3.5.0 on 2020-09-01. - Apache Camel 2.25.2 on 2020-07-21. - Camel-K 1.0.1 on 25 Jun 2020 - Camel-K 1.1.0 on 21 Jul 2020 - Camel-Quarkus 1.0.0-CR3 on 3 Jul 2020 - Camel-Quarkus 1.0.0 on 10 Aug 2020 - Camel-Quarkus 1.0.1 on 26 Aug 2020 - Camel-Kafka-connector 0.3.0 on 17 Jun 2020 - Camel-Kafka-connector 0.4.0 on 30 Jul 2020 - This year Apache Camel participated to Google Summer Of Code: both the selected students passed the evaluation with success - This year Apache Camel participated to Outreachy program: the two person selected did a great job ## Community Health: - dev@camel.apache.org had a 25% decrease in traffic in the past quarter (467 emails compared to 622): This is mainly related to the fact we released the LTS 3.4.x. So there was less activity on dev ML, another reason is the summer time - users@camel.apache.org had a 22% decrease in traffic in the past quarter (367 emails compared to 469): Similar to dev ML, the summer time is one reason, the other one is that Camel 3 is still in his early adoption so not all the users are moving from the 2.x version - 337 issues opened in JIRA, past quarter (-31% decrease) This is related to the LTS releases train and the summer time - 338 issues closed in JIRA, past quarter (-25% decrease) This is related to the LTS releases train and the summer time too. Basically we are adding new features on next releases > 3.4.x and we are reviewing the old issues. - 3000 commits in the past quarter (-13% decrease) During the LTS work we add a lot of stuff, during the summer time we slowed down a bit - 673 PRs opened on GitHub, past quarter (-28% decrease) This decrease is related to the LTS releases and the summer time - 681 PRs closed on GitHub, past quarter (-25% decrease) This decrease is related to the LTS releases and the summer time - 299 issues opened on GitHub, past quarter (-6% decrease) This decrease is related to the summer time and the LTS releases - 207 issues closed on GitHub, past quarter (-40% decrease) This decrease is related to the summer time and the LTS releases. We reviewed the old github issues and closed some of them.
## Description: Apache Camel is a powerful open source integration library based on Enterprise Integration Patterns. Rules for Camel's routing engine can be defined in either a Java based DSL or XML. ## Issues: there are no issues requiring board attention at this time ## Membership Data: Apache Camel was founded 2008-12-17 (11 years ago) There are currently 70 committers and 36 PMC members in this project. The Committer-to-PMC ratio is roughly 9:5. Community changes, past quarter: - Omar Al-Safi was added to the PMC on 2020-06-01 - No new committers. Last addition was Gazda on 2020-03-02. ## Project Activity: - We released Apache Camel 3.2.0 on 06 Apr 2020 - We released Apache Camel 3.3.0 on 05 May 2020 - We are working already on the 3.4.0 version too. - The 3.4.0 release will be a LTS release, so we'll maintain the 3.4.x baseline by backporting fixes, while innovating with new versions - Actually we are doing a big effort on stabilizing the codebase for 3.x branch, there is an ongoing effort and we are doing really well on this particular side. - We released a new 2.x version, the 2.25.1 on 16 Apr 2020. - We are preparing for the next minor release Apache Camel 2.24.4 and the next patch release for 2.25.x - We released Camel-K-Runtime 1.2.1 and 1.3.0 respectively on 20 Mar 2020 and 05 Jun 2020 - We released Camel-K 1.0.0 on 05 Jun 2020 - We are continuing our work on Camel-K by improving the support for Camel 3 and we finally released a 1.0.0 GA. - We are continuing supporting Camel-Quarkus by releasing multiple versions in this quarter - We released the following Camel-Quarkus versions: - 1.0.0-M5 on 13 Mar 2020 - 1.0.0-M6 on 09 Apr 2020 - 1.0.0-M7 on 27 Apr 2020 - 1.0.0-CR2 on 30 May 2020 - We are continuing working on the Camel-kafka-connector project and we released two version of it - 0.1.0 on 25 Apr 2020 - 0.2.0 on 17 May 2020 - We are about to release the 0.3.0 version based on Camel 3.3.0 - This is the complete releases list - 3.2.0 was released on 2020-06-04 - 3.3.0 was released on 2020-05-05 - 2.25.1 released on 2020-04-16 - Camel-K 1.0.0 released on 2020-06-05 - Camel-Quarkus 1.0.0-M5 released on 2020-03-13 - Camel-Quarkus 1.0.0-M6 released on 2020-04-09 - Camel-Quarkus 1.0.0-M7 released on 2020-04-27 - Camel-Quarkus 1.0.0-CR2 released on 2020-05-20 - Camel-Kafka-connector 0.1.0 released on 2020-04-25 - Camel-Kafka-connector 0.2.0 released on 2020-05-17 - This year Apache Camel will participate to Google Summer Of Code: the select students are two and we are already working with them - This year Apache Camel will participate to Outreachy program: the selected persons are two and we are already working with them. ## Community Health: - dev@camel.apache.org had a 1% decrease in traffic in the past quarter (657 emails compared to 658) More or less the activity is the same with questions about migration from Camel 2 to Camel 3 - users@camel.apache.org had a 5% decrease in traffic in the past quarter (488 emails compared to 513) This is related to the questions coming in about migration from camel 2 to 3, but since we are stabilizing the codebase and improving the documentation, the questions coming in are way more less - 442 issues opened in JIRA, past quarter (+2% increase) Just a little increase related to new stuff and housekeeping plus the on-going work for Camel 3.4.0 - 409 issues closed in JIRA, past quarter (+13% increase) We closed a lot of stuff for 3.3.0 and for 3.4.0 - 3187 commits in the past quarter (-14% decrease) The code is stabilizing and we are focusing on less material now, that's why the commits are less - 823 PRs opened on GitHub, past quarter (+28% increase) This is for the stabilization, so feature contributor are continuing to work on them and we have also new contributors opening PRs for documentation and little fixes - 826 PRs closed on GitHub, past quarter (+28% increase) This is for the stabilization, so feature contributor are continuing to work on them and we have also new contributors opening PRs for documentation and little fixes - 292 issues opened on GitHub, past quarter (-3% decrease) This is for the new projects in the ecosystem, we are opening more or less the same number of issues on the subprojects - 320 issues closed on GitHub, past quarter (+42% increase) This is because we went through the existing issues in camel-k and camel-k-runtime before releasing the 1.0.0 GA
## Description: Apache Camel is a powerful open source integration library based on Enterprise Integration Patterns. Rules for Camel's routing engine can be defined in either a Java based DSL or XML. ## Issues: there are no issues requiring board attention at this time ## Membership Data: Apache Camel was founded 2008-12-17 (11 years ago) There are currently 70 committers and 35 PMC members in this project. The Committer-to-PMC ratio is 2:1. Community changes, past quarter: - No new PMC members. Last addition was Dmitry Volodin on 2019-05-08. - Gazda was added as committer on 2020-03-02 ## Project Activity: - We released Apache Camel 3.0.1 on 16 Jan 2020 - We released Apache Camel 3.1.0 on 27 Feb 2020 - We are already working on a patch release for 3.1.x and we'll release 3.1.1 in the next quarter - We are working already on the 3.2.0 version too. - Actually we are doing a big effort on stabilizing the codebase for 3.x branch, there is an ongoing effort and a lot of activity and contributions from old and new contributors - We released a new 2.x version, the 2.24.3 on 26 Dec 2019. - We released also the 2.25.0 version, on 23 Jan 2020, which will be the last major release supported on Camel 2.x - We are preparing for the next minor release Apache Camel 2.24.4 and the first patch release for 2.25.x - We released Camel-K-Runtime 1.0.9 and 1.1.0 respectively on 19 Dec 2019 and 24 Feb 2020 - We released Camel-K 1.0.0-RC1 and Camel-K 1.0.0-RC2 respectively on 24 Dec 2019 and 28 Feb 2020 - We are continuing our work on Camel-K by improving the support for Camel 3 and we plan to release a GA soon after the RC candidates will have more feedback. - We are continuing supporting Camel-Quarkus by releasing multiple versions in this quarter - We released the following Camel-Quarkus versions: - 1.0.0-M2 on 17 Dec 2019 - 1.0.0-M3 on 24 Jan 2020 - 1.0.0-M4 on 06 Mar 2020 - We are continuing working on the Camel-kafka-connector project to be able to release a first version in the coming months - This is the complete releases list - 3.0.1 was released on 2020-16-01 - 3.1.0 was released on 2020-27-02 - 2.25.0 released on 2020-23-01 - 2.24.3 released on 2019-26-12 - Camel-K 1.0.0-RC1 released on 2019-12-24 - Camel-K 1.0.0-RC2 released on 2020-02-245 - Camel-Quarkus 1.0.0-M2 released on 2019-12-17 - Camel-Quarkus 1.0.0-M3 released on 2020-01-24 - Camel-Quarkus 1.0.0-M4 released on 2020-03-06 - This year Apache Camel will participate to Google Summer Of Code: we have already some student proposals we are evaluating and we are giving feedback to them. Actually we have 5 students interested. - This year Apache Camel will participate to Outreachy program: We have already a lot of requests for contributing and getting started. Really nice. More info: https://camel.apache.org/blog/Outreachy-May2020/ ## Community Health: - dev@camel.apache.org had a 56% decrease in traffic in the past quarter (663 emails compared to 1505) This is related to the first Camel 3 GA release - users@camel.apache.org had a 15% increase in traffic in the past quarter (514 emails compared to 445) This is related to the questions coming in about migration from camel 2 to 3 - 388 issues opened in JIRA, past quarter (+21% increase) This is because we created new issues for improvements and new stuff on Camel 3 branch - 329 issues closed in JIRA, past quarter (+4% decrease) This is because we were focusing on existing issues too - 3450 commits in the past quarter (+28% decrease) This is for the new features and some refactoring done in 3.1.0 - 545 PRs opened on GitHub, past quarter (-12% decrease) This is for the stabilization, so feature contributor are continuing to work on them - 556 PRs closed on GitHub, past quarter (-10% decrease) This is for the stabilization, so feature contributor are continuing to work on them - 284 issues opened on GitHub, past quarter (9% increase) This is for the new projects in the ecosystem, we are noticing more contributors and obviously more issue - 195 issues closed on GitHub, past quarter (-13% decrease) This is because there are ongoing issue still to resolve
## Description: Apache Camel is a powerful open source integration library based on Enterprise Integration Patterns. Rules for Camel's routing engine can be defined in either a Java based DSL or XML. ## Issues: there are no issues requiring board attention at this time ## Membership Data: Apache Camel was founded 2008-12-17 (11 years ago) There are currently 69 committers and 35 PMC members in this project. The Committer-to-PMC ratio is roughly 9:5. Community changes, past quarter: - No new PMC members. Last addition was Dmitry Volodin on 2019-05-08. - Omar Al-Safi was added as committer on 2019-11-07 ## Project Activity: - We finally released Apache Camel 3.0.0 on 24 Nov 2019 - We are working already on the first minor release 3.0.1 and we are focusing on bug fixes, stabilization and minor improvements. - We are working already on the 3.1.0 version too. - During this quarter we released two release candidates for Camel 3.0.0: RC2 on 6 Oct 2019 and RC3 on 25 Oct 2019. We use the feedback from the community to finalize the GA release. - We released a new 2.x version, the 2.24.2 on 13 Sept 2019. Also we released 2.23.4 on 22 Sept 2019. - We are working on a new minor release Apache Camel 2.25.0, we're working on bug fixes and stabilisation of the codebase. - We are preparing for the next minor release Apache Camel 2.24.3 expected for the end of the year: we are working on bug fixes mainly. - We released Camel-K-Runtime 1.0.4, 1.0.5 and 1.0.7, respectively on 05 Oct 2019, 18 Oct 2019 and 13 Nov 2019 - We released Camel-K 1.0.0-M2, 1.0.0-M3 and 1.0.0-M4, respectively on 08 Oct 2019, 22 Oct 2019 and 18 Nov 2019 - We are continuing our work on Camel-K by improving the support for Camel 3 and we plan to release a GA soon in the beginning of 2020. - We are continuing to support Camel-Quarkus by releasing multiple versions in this quarter - We released the following Camel-Quarkus versions: - 0.2.0 on 23 Sep 2019 - 0.3.0 on 25 Oct 2019 - 0.3.1 on 30 Oct 2019 - 0.4.0 on 15 Nov 2019 - 1.0.0-M1 on 04 Dec 2019 - We added another project to the Apache Camel ecosystem: camel-kafka-connector, this project is based on Kafka-connect and it is leveraging the components that we already have in Camel. - This is the complete releases list - 3.0.0 was released on 2019-24-11 - 3.0.0-RC2 released on 2019-06-10 - 3.0.0-RC3 released on 2019-25-10 - 2.24.2 released on 2019-13-09 - 2.23.4 released on 2019-22-09 - Camel-K 0.3.4 was released on Tue Jun 11 2019 - Camel-K 1.0.0-M2 released on 2019-10-08 - Camel-K 1.0.0-M3 released on 2019-10-22 - Camel-K 1.0.0-M4 released on 2019-11-18 - Camel-Quarkus 0.2.0 released on 2019-09-23 - Camel-Quarkus 0.3.0 released on 2019-10-25 - Camel-Quarkus 0.3.1 released on 2019-10-30 - Camel-Quarkus 0.4.0 released on 2019-11-15 - Camel-Quarkus 1.0.0-M1 released on 2019-12-04 ## Community Health: - dev@camel.apache.org had a 35% decrease in traffic in the past quarter (1550 emails compared to 2371) This is for the GA release - users@camel.apache.org had a 51% increase in traffic in the past quarter (465 emails compared to 307) This is for the feedback we got - 307 issues opened in JIRA, past quarter (-6% decrease) This is because we were focusing on existing issues - 305 issues closed in JIRA, past quarter (-11% decrease) This is because we were focusing on existing issues - 2601 commits in the past quarter (-13% decrease) This is for the GA release, so more stabilization - 113 code contributors in the past quarter (14% increase) This is for the new projects in the ecosystem, we are noticing more contributors - 602 PRs opened on GitHub, past quarter (19% increase) This is for the new projects in the ecosystem, we are noticing more contributors - 598 PRs closed on GitHub, past quarter (21% increase) This is for the new projects in the ecosystem, we are noticing more contributors - 261 issues opened on GitHub, past quarter (42% increase) This is for the new projects in the ecosystem, we are noticing more contributors - 225 issues closed on GitHub, past quarter (61% increase) This is for the new projects in the ecosystem, we are noticing more contributors
## Description: Apache Camel is a powerful open source integration library based on Enterprise Integration Patterns. Rules for Camel's routing engine can be defined in either a Java based DSL or XML. ## Issues: there are no issues requiring board attention at this time ## Membership Data: Apache Camel was founded 2008-12-17 (11 years ago) There are currently 68 committers and 35 PMC members in this project. The Committer-to-PMC ratio is roughly 9:5. Community changes, past quarter: - No new PMC members. Last addition was Dmitry Volodin on 2019-05-08. - Denis Istomin was added as committer on 2019-07-30 - Jan Bednar was added as committer on 2019-08-01 ## Project Activity: - We are continuing our work towards Apache Camel 3.0.0: we released the Milestone 4 on 11 July 2019 and the Release candidate 1 on 01 September 2019 - We are working already on the final release and we are focusing on bug fixes, stabilization and code cleanup. - We published the new website and we are improving the documentation and looks and feel. The general feedback of the community was really good. - We released a new 2.x version, the 2.24.1 on 23 June 2019. Also we released 2.23.3 on 17 June 2019 and 2.22.5 on 11 June 2019. - We are working on a new minor release Apache Camel 2.25.0, we're working on bug fixes and stabilisation of the codebase. - We are preparing for the next minor release Apache Camel 2.24.2 expected for the end of September/mid October: we are working on bug fixes mainly. - We released Camel-K-Runtime 1.0.0 and 1.0.1, respectively on 26 July 2019 and 23 Aug 2019 - We released Camel-K 0.3.4 (on 11 June 2019) and 1.0.0-M1 (on 29 Jul 2019) - We are continuing our work on Camel-K by improving the support for Camel 3 and keeping the same release timing as Apache Camel. - We created an Apache Camel subproject, Camel-Quarkus. The aim of this project is supporting Camel in the Quarkus framework. - We released the following Camel-Quarkus versions: - 0.0.2 on 29 Jul 2019 - 0.1.0 on 07 Aug 2019 - We completed the work with the students selected for Google Summer of Code 2019, the Apache Camel mentors are following three students. Two out of three students passed successfully the Google Summer of code: the new dataformat based on Any23 task and the new website task. Really nice experience for mentors and students. We'll be part of the project again next year - This is the complete releases list - 3.0.0-RC1 was released on 2019-09-01. - 3.0.0-M4 was released on 2019-07-11. - 2.24.1 was released on 2019-06-23. - 2.23.3 was released on 2019-06-17. - 2.22.5 was released on 2019-06-11. - 3.0.0-M3 was released on 2019-06-07. - Camel-K 0.3.4 was released on Tue Jun 11 2019 - Camel-K 1.0.0-M1 was released on Mon Jul 29 2019 - Camel-K 0.3.3 was released on Fri May 3 2019 - Camel-Quarkus 0.0.2 was released on Mon Jul 29 2019 - Camel-Quarkus 0.1.0 was released on Wed Aug 07 2019 ## Community Health: - dev@camel.apache.org had a 147% increase in traffic in the past quarter (2482 emails compared to 1004) This is because we are near the new camel 3 final release - issues@camel.apache.org had a 34% increase in traffic in the past quarter (2921 emails compared to 2166) This is because we are near the new camel 3 final release and we're starting to have feedback and bugs reported - users@camel.apache.org had a 60% increase in traffic in the past quarter (317 emails compared to 198) This is mainly for announcements and discussion around the new website - 299 issues opened in JIRA, past quarter (-9% decrease) - 319 issues closed in JIRA, past quarter (no change) - 2828 commits in the past quarter (16% increase) This is mainly for Camel 3 activity - 95 code contributors in the past quarter (3% increase) We have new contributors for documentation and new website - 446 PRs opened on GitHub, past quarter (41% increase) - 442 PRs closed on GitHub, past quarter (38% increase) - 176 issues opened on GitHub, past quarter (58% increase) In Apache Camel main repository we don't use GitHub issues, this stats comes from Camel-k and Camel-quarkus subprojects - 130 issues closed on GitHub, past quarter (75% increase) In Apache Camel main repository we don't use GitHub issues, this stats comes from Camel-k and Camel-quarkus subprojects
## Description: - Apache Camel is a powerful open source integration library based on Enterprise Integration Patterns. Rules for Camel's routing engine can be defined in either a Java based DSL or XML. ## Issues: - there are no issues requiring board attention at this time ## Activity: - We are continuing our work towards Apache Camel 3.0.0: we released the Milestone 2 on 31 March 2019 and the Milestone 3 on 04 June 2019 - We are working already on the Milestone 4 and we are focusing on bug fixes, stabilization and some new features. - We are continuing our work on a new website and we migrated some more informations from the old site (like security advisories, release notes etc.) and integrated them in the new site material. - We released a new 2.x version, the 2.24.0 on 12 May 2019. Also we released 2.23.2 on 13 April 2019 and 2.22.4 on 13 April 2019. - We are preparing for the next minor release Apache Camel 2.23.3 expected for the end of June/mid July: we are working on bug fixes mainly. - We are preparing for the last minor release Apache Camel 2.22.5 expected for the end of June/mid July: we are working on bug fixes mainly. This will be the last 2.22.x release. - We are preparing the first patch release for 2.24.x, 2.24.1 which is planned for end of July/ Mid August 2019. - We released the CVE-2019-0188 http://camel.apache.org/staging/security/CVE-2019-0188.html - We released Camel-K-Runtime 0.3.2 and 0.3.3, respectively on 26 April 2019 and 28 May 2019 - We released Camel-K 0.3.1 (on 16 March 2019), 0.3.2 (on 26 March 2019) and 0.3.3 (on 3 May 2019) - We are continuing our work on Camel-K by improving the support for Camel-3.x - We're are working with the students selected for Google Summer of Code 2019, the Apache Camel mentors are following three students. The projects are related to GraphQL, a new dataformat based on Any23 project and the new website. ## Health report: - The project is super healthy, active and stays at a high level ## PMC changes: - Currently 35 PMC members. - Two new members since the last report. - Dmitry Volodin was added to the PMC on Wed May 08 2019 . Pascal Schumacher was added to the PMC on Tue May 07 2019 - Last PMC was added on Wed May 08 2019 (Dmitry Volodin) ## Committer base changes: - Currently 66 committers. - No new committers in the last 3 months. - Last committer addition was on Sat Feb 23 2019 (Andrea Tarocchi) ## Releases: - 2.22.4 was released on Sat Apr 13 2019 - 2.23.2 was released on Sat Apr 13 2019 - 2.24.0 was released on Sun May 12 2019 - 3.0.0-M2 was released on Sun Mar 31 2019 - 3.0.0-M3 was released on Tue Jun 4 2019 - Camel-K 0.3.1 was released on Tue Mar 16 2019 - Camel-K 0.3.2 was released on Tue Mar 26 2019 - Camel-K 0.3.3 was released on Fri May 3 2019 ## Mailing list activity: - users@camel.apache.org: - 1007 subscribers (down -4 in the last 3 months) - 217 emails sent to list (345 in previous quarter) - dev@camel.apache.org: - 349 subscribers (down -1 in the last 3 months) - 1171 emails sent to list (1339 in previous quarter) - issues@camel.apache.org: - 84 subscribers (up 1 in the last 3 months): - 2309 emails sent to list (2065 in previous quarter) - notifications@camel.apache.org: - 8 subscribers (up 0 in the last 3 months) ## JIRA activity: - 318 JIRA tickets created in the last 3 months - 305 JIRA tickets closed/resolved in the last 3 months
## Description: - Apache Camel is a powerful open source integration library based on Enterprise Integration Patterns. Rules for Camel's routing engine can be defined in either a Java based DSL or XML. ## Issues: - there are no issues requiring board attention at this time ## Activity: - We are continuing our work towards Apache Camel 3.0.0: we released the Milestone 1 on 17 February 2019. - We are working on the Milestone 2 and we are focusing on new features, improvements and bug fixes. - We are continuing our work on a new website and on adding more new documentation in the repository. - We are working on a new 2.x release (2.24.0) but we still need to define a timeline for that. - We are preparing for the next minor release Apache Camel 2.23.2 expected for the end of April: we are working on bug fixes mainly. - We released Camel-K-Runtime 0.2.1 and 0.3.0 - We released Camel-K 0.2.1 and 0.3.0 - We are continuing our work on Camel-K by supporting both Camel 2.x and Camel-3.x - We held a Camel BoF at FOSDEM 2019 with two PMCs, one contributor and two community members - We're receiving signups for tasks we marked for Google Summer of Code 2019, so far two students have applied ## Health report: - The project is super healthy, active and stays at a high level ## PMC changes: - Currently 33 PMC members. - Alex Dettinger is the last new PMC Member added since the last report - Last PMC was added on Mon Dec 17 2018 ## Committer base changes: - Currently 66 committers. - 3 additions since the last report - Ramu K was added as a committer on Fri Feb 22 2019 - Tadayoshi Sato was added as a committer on Mon Dec 10 2018 - Andrea Tarocchi was added as a committer on Sat Feb 23 2019 ## Releases: - Camel 2.21.4 was released on Thu Jan 10 2019 - Camel 2.21.5 was released on Sat Feb 09 2019 - Camel 2.22.3 was released on Fri Jan 25 2019 - Camel 2.23.1 was released on Fri Jan 18 2019 - Camel 3.0.0-M1 was released on Fri Feb 22 2019 - Camel-K 0.2.1 was released on Fri 22 2019 - Camel-K 0.3.0 was released on Mon Mar 04 2019 ## Mailing list activity: - users@camel.apache.org: - 1010 subscribers (up 19 in the last 3 months) - 358 emails sent to list (295 in previous quarter) - dev@camel.apache.org: - 349 subscribers (up 8 in the last 3 months) - 1450 emails sent to list (1104 in previous quarter) - issues@camel.apache.org: - 83 subscribers (down -1 in the last 3 months): - 2317 emails sent to list (1610 in previous quarter) - notifications@camel.apache.org: - 8 subscribers (up 0 in the last 3 months) ## JIRA activity: - 311 JIRA tickets created in the last 3 months - 247 JIRA tickets closed/resolved in the last 3 months
## Description: - Apache Camel is a powerful open source integration library based on Enterprise Integration Patterns. Rules for Camel's routing engine can be defined in either a Java based DSL or XML. ## Issues: - there are no issues requiring board attention at this time ## Activity: - We are working on a new website. We are continuously moving pages from confluence to github .adoc. We moved the security advisories and the release notes too. - We are continuing our work towards Apache Camel 3.0.0. We already have a new branch with updated code for that. - We announced the following vulnerability with the last releases: http://camel.apache.org/security-advisories.data/CVE-2018-8041.txt.asc?version=1&modificationDate=1536746339000&api=v2 - We are discussing possible new committers and PMC members. ## Health report: - The project is super healthy, active and stays at a high level ## PMC changes: - Currently 32 PMC members. - Nicola Ferraro is the last new PMC Member added since the last report - Last PMC was added on Mon Jul 16 2018 ## Committer base changes: - Currently 63 committers. - No new committers in the last 3 months. - Dmitry Volodin was added as a committer on Sat May 19 2018 ## Releases: - 2.21.3 was released on Sun Oct 28 2018 - 2.22.1 was released on Fri Sep 07 2018 - 2.22.2 was released on Thu Nov 01 2018 - 2.23.0 was released on Thu Nov 29 2018 ## Mailing list activity: - users@camel.apache.org: - 991 subscribers (down 15 in the last 3 months) - 315 emails sent to list (316 in previous quarter) - dev@camel.apache.org: - 341 subscribers (down 18 in the last 3 months) - 1155 emails sent to list (515 in previous quarter) - issues@camel.apache.org: - 84 subscribers (up 0 in the last 3 months): - 1748 emails sent to list (2410 in previous quarter) - notifications@camel.apache.org: - 8 subscribers (up 0 in the last 3 months) ## JIRA activity: - 204 JIRA tickets created in the last 3 months - 152 JIRA tickets closed/resolved in the last 3 months
## Description: - Apache Camel is a powerful open source integration library based on Enterprise Integration Patterns. Rules for Camel's routing engine can be defined in either a Java based DSL or XML. ## Issues: - there are no issues requiring board attention at this time ## Activity: - We are preparing for the next minor releases Apache Camel 2.22.1 expected for the beginning of September and 2.21.2. - We are working on a new website while the documentation has been totally migrated to Github to be able to control the documentation at code level. - We are continuing our work towards Apache Camel 3.0.0. - We announced the following vulnerability with the last releases: http://camel.apache.org/security-advisorie s.data/CVE-2018-8027.txt.asc?version=4&modificationDate=1533020841313&api=v2 ## Health report: - The project is super healthy, active and stays at a high level ## PMC changes: - Currently 32 PMC members. - Nicola Ferraro is the last new PMC Member added since the last report - Last PMC was added on Mon Jul 16 2018 ## Committer base changes: - Currently 63 committers. - No new committers in the last 3 months. - Dmitry Volodin was added as a committer on Sat May 19 2018 ## Releases: - 2.21.2 was released on Sat Jul 21 2018 - 2.22.0 was released on Tue Jul 03 2018 ## Mailing list activity: - users@camel.apache.org: - 1009 subscribers (up 14 in the last 3 months) - 325 emails sent to list (290 in previous quarter) - dev@camel.apache.org: - 360 subscribers (up 3 in the last 3 months) - 540 emails sent to list (501 in previous quarter) - issues@camel.apache.org: - 84 subscribers (down -2 in the last 3 months): - 2555 emails sent to list (2172 in previous quarter) - notifications@camel.apache.org: - 8 subscribers (up 0 in the last 3 months) ## JIRA activity: - 214 JIRA tickets created in the last 3 months - 234 JIRA tickets closed/resolved in the last 3 months
## Description: - Apache Camel is a powerful open source integration library based on Enterprise Integration Patterns. Rules for Camel's routing engine can be defined in either a Java based DSL or XML. ## Issues: - there are no issues requiring board attention at this time ## Activity: - We are preparing for the next minor release Apache Camel 2.22.0 expected for the end of June: we are working on the last touches to be prepared for release. - We are working on a new website while the documentation has been totally migrated to Github to be able to control the documentation at code level. - We are continuing our work towards Apache Camel 3.0.0. ## Health report: - The project is super healthy, active and stays at a high level ## PMC changes: - Currently 31 PMC members. - Onder Sezgin is the last new PMC Member added since the last report - Last PMC was added on Sun Apr 29 2018 ## Committer base changes: - Currently 63 committers. - 1 additions since the last report - Dmitry Volodin was added as a committer on Sat May 19 2018 ## Releases: - 2.20.3 was released on Fri Mar 30 2018 - 2.21.0 was released on Thu Mar 15 2018 - 2.21.1 was released on Fri May 04 2018 ## Mailing list activity: - users@camel.apache.org: - 995 subscribers (up 12 in the last 3 months) - 290 emails sent to list (403 in previous quarter) - dev@camel.apache.org: - 357 subscribers (down -1 in the last 3 months) - 508 emails sent to list (388 in previous quarter) - issues@camel.apache.org: - 86 subscribers (up 1 in the last 3 months): - 2226 emails sent to list (2172 in previous quarter) - notifications@camel.apache.org: - 8 subscribers (up 0 in the last 3 months) ## JIRA activity: - 248 JIRA tickets created in the last 3 months - 237 JIRA tickets closed/resolved in the last 3 months
WHEREAS, the Board of Directors heretofore appointed Christian Mueller (cmueller) to the office of Vice President, Apache Camel, and WHEREAS, the Board of Directors is in receipt of the resignation of Christian Mueller from the office of Vice President, Apache Camel, and WHEREAS, the Project Management Committee of the Apache Camel project has chosen by vote to recommend Andrea Cosentino (acosentino) as the successor to the post; NOW, THEREFORE, BE IT RESOLVED, that Christian Mueller is relieved and discharged from the duties and responsibilities of the office of Vice President, Apache Camel, and BE IT FURTHER RESOLVED, that Andrea Cosentino be and hereby is appointed to the office of Vice President, Apache Camel, to serve in accordance with and subject to the direction of the Board of Directors and the Bylaws of the Foundation until death, resignation, retirement, removal or disqualification, or until a successor is appointed. Special Order 7F, Change the Apache Camel Project Chair, was approved by Unanimous Vote of the directors present.
## Description: - Apache Camel is a powerful open source integration library based on Enterprise Integration Patterns. Rules for Camel's routing engine can be defined in either a Java based DSL or XML. ## Issues: - We apologize to have missed the previous board reports. PMC members stepped up and we are taking action to move forward. - We also asking the board to change the Apache Camel PMC chair and proposing Andrea Cosentino as the new PMC chair. ## Activity: - We are focusing the development of the next minor release Apache Camel 2.22.0 expected for the end of June. - Since the last report we released: Camel 2.21.0, 2.21.1, 2.20.2, 2.20.3 and 2.19.5 - We are working on a new website while the documentation has been totally migrated to Github to be able to control the documentation at code level. - We are continuing our work towards Apache Camel 3.0.0. ## Health report: - The project is super healthy, active and stays at a high level - We are discussing to rotate the PMC chair. ## PMC changes: - Currently 31 PMC members. - Onder Sezgin is the last new PMC Member added since the last report - Last PMC was added on Sun Apr 29 2018 ## Committer base changes: - Currently 62 committers. - 2 additions since the last report - James Netherton was added on Tue Dec 26 2017 - John Poth was added on Thu Dec 21 2017 ## Releases: - 2.20.2 was released on Tue Jan 23 2018 - 2.19.5 was released on Fri Mar 30 2018 - 2.20.3 was released on Fri Mar 30 2018 - 2.21.0 was released on Thu Mar 15 2018 - 2.21.1 was released on Fri May 04 2018 ## Mailing list activity: - users@camel.apache.org: - 995 subscribers (up 14 in the last 3 months): - 330 emails sent to list (417 in previous quarter) - dev@camel.apache.org: - 359 subscribers (up 2 in the last 3 months): - 519 emails sent to list (398 in previous quarter) - issues@camel.apache.org: - 86 subscribers (up 1 in the last 3 months): - 2257 emails sent to list (2090 in previous quarter) - notifications@camel.apache.org: - 8 subscribers (up 0 in the last 3 months) ## JIRA activity: - 254 JIRA tickets created in the last 3 months - 241 JIRA tickets closed/resolved in the last 3 months
No report was submitted.
No report was submitted.
@Brett: pursue a report for Camel
## Description: - Apache Camel is a powerful open source integration framework based on known Enterprise Integration Patterns. ## Issues: - there are no issues requiring board attention at this time ## Activity: - We are focusing the development of the next minor release Apache Camel 2.21.0 expected to be released in Q1 2017. - Discussed to use the Apache Gitbox service. No outcome so far. - Released Camel 2.18.5, which is our last planned 2.18.x maintenance release. - Continue our work towards Apache Camel 3.0.0. - No progress so far on carrying out the logo change. - fixed and reported the Castor marschaling issue: CVE-2017-12634 - fixed and reported the Hessian unmarshalling issue: CVE-2017-12633 ## Health report: - The project is super healthy, active and stays at a high level ## PMC changes: - Currently 30 PMC members. - No addition since the last report. - Last PMC was added on Sun Jul 02 2017 ## Committer base changes: - Currently 60 committers. - 2 additions since the last report - Alex Dettinger was added on Mon Oct 09 2017 - Pascal Schumacher was added on Fri Oct 13 2017 ## Releases: - 2.18.5 was released on Mon Sep 25 2017 - 2.19.4 was released on Sun Nov 05 2017 - 2.20.0 was released on Wed Oct 11 2017 - 2.20.1 was released on Tue Nov 14 2017 ## Mailing list activity: - Mailing list activity stays at a high level.
## Description: - Apache Camel is a powerful open source integration framework based on known Enterprise Integration Patterns. ## Issues: - there are no issues requiring board attention at this time ## Activity: - The spam mails we are receiving on Nabble and also on the moderate mail accounts are painful. - We are focusing the development of the next minor release Apache Camel 2.20.0 expected to be released at the end of September 2017. - Finalizing Camel 2.18.5, which will be our last planned 2.18.x maintenance release. - Some people started to work on some bigger changes for the next major release Apache Camel 3.0.0. - We have started to deprecate APIs and components that will be dropped for Camel 3.0 - No progress so far on carrying out the logo changet. ## Health report: - The project is super healthy, active and stays at a high level ## PMC changes: - Currently 30 PMC members. - No addition since the last report. - Last PMC was added on Sun Jul 02 2017 ## Committer base changes: - Currently 58 committers. - no addition since the last report - Last committer was added on Thu Jun 08 2017 ## Releases: - 2.19.3 was released on Sep 14 2017 ## Mailing list activity: - Mailing list activity stays at a high level.
Status report for the Apache Camel project - August 2017 ## Description: - Apache Camel is a powerful open source integration framework based on known Enterprise Integration Patterns. ## Issues: - there are no issues requiring board attention at this time ## Activity: - The spam mails we are receiving on Nabble and also on the moderate mail accounts are painful. - The Camel team created a Gitter chat at https://gitter.im/apache/apache-camel to provide more possibilities to our our community to get in touch with us. https://s.apache.org/9kwJ - We are receiving many contributions from our contributors (via GitHub pull requests). We have more than 1500 closed pull requests where 98% is from community contributors. - We are focusing the development of the next minor release Apache Camel 2.20.0 expected to be released in Q4 2017. - Some people started to work on some bigger changes for the next major release Apache Camel 3.0.0. - We have started to deprecate APIs and components that will be dropped for Camel 3.0 - We run a new logo proposal and our community has vote: https://s.apache.org/qWPW Now, the PMC decides how to carry on with the logo change. ## Health report: - The project is super healthy, active and stays at a high level - At ApacheCon Europe 2016, we had 5 presentations about Apache Camel from PMC's, committers and contributers/users. ## PMC changes: - Currently 30 PMC members. - Zoran Regvart was added to the PMC on Sun Jul 02 2017 ## Committer base changes: - Currently 58 committers. - Tomohisa Igarashi was added as a committer on Wed Jun 07 2017 - Onder Sezgin was added as a committer on Thu Jun 08 2017 - Quinn Stevenson was added as a committer on Wed Jun 07 2017 ## Releases: - 2.17.5 was released on Jan 22 2017 - 2.17.6 was released on March 8 2017 - 2.17.7 was released on May 18 2017 - 2.18.2 was released on Jan 30 2017 - 2.18.3 was released on Mar 12 2017 - 2.18.4 was released on May 25 2017 - 2.19.1 was released on Jun 15 2017 - 2.19.2 was released on Aug 1 2017 ## Mailing list activity: - Mailing list activity stays at a high level.
## Description: - Apache Camel is a powerful open source integration framework based on known Enterprise Integration Patterns. ## Issues: - there are no issues requiring board attention at this time ## Activity: - We are receiving many contributions from our contributors (via GitHub pull requests). We have more than 1500 closed pull requests where 98% is from community contributors. - A new releases is coming out soon: Camel 2.18.3 - We are focusing the development of the next minor release Apache Camel 2.19.0 expected to be released in April. - Some people started to work on some bigger changes for the next major release Apache Camel 3.0.0. - We have started to deprecate APIs and components that will be dropped for Camel 3.0 - We are running a new logo proposal that has a deadline at the end of March. We have receive about 6 different logo proposals. After the deadline we will have a vote about the logo which the PMC then ultimate decides whether to carry on with the logo change ## Health report: - The project is super healthy, active and stays at a high level - At ApacheCon Europe 2016, we had 5 presentations about Apache Camel from PMC's, committers and contributers/users. ## PMC changes: - Currently 30 PMC members. - Zoran Regvart was added to the PMC on Sun Jul 02 2017 ## Committer base changes: - Currently 58 committers. - Tomohisa Igarashi was added as a committer on Wed Jun 07 2017 - Onder Sezgin was added as a committer on Thu Jun 08 2017 - Quinn Stevenson was added as a committer on Wed Jun 07 2017 ## Releases: - 2.17.5 was released on Jan 22 2017 - 2.17.6 was released on March 8 2017 - 2.18.2 was released on Jan 30 2017 - 2.19.1 was released on Jun 15 2017 ## Mailing list activity: - Mailing list activity stays at a high level.
@Mark: ask for an improved report next month
No report was submitted.
## Description: - Apache Camel is a powerful open source integration framework based on known Enterprise Integration Patterns. ## Issues: - there are no issues requiring board attention at this time ## Activity: - We are receiving many contributions from our contributors (via GitHub pull requests). We have more than 1500 closed pull requests where 98% is from community contributors. - A new releases is coming out soon: Camel 2.18.3 - We are focusing the development of the next minor release Apache Camel 2.19.0 expected to be released in April. - Some people started to work on some bigger changes for the next major release Apache Camel 3.0.0. - We have started to deprecate APIs and components that will be dropped for Camel 3.0 - We are running a new logo proposal that has a deadline at the end of March. We have receive about 6 different logo proposals. After the deadline we will have a vote about the logo which the PMC then ultimate decides whether to carry on with the logo change ## Health report: - The project is super healthy, active and stays at a high level - At ApacheCon Europe 2016, we had 5 presentations about Apache Camel from PMC's, committers and contributers/users. ## PMC changes: - Currently 29 PMC members. - Luca Burgazzoli was added to the PMC on Thu Oct 06 2016 ## Committer base changes: - Currently 54 committers. - Last committer addition was Zoran Regvart at Feb 18 2017 ## Releases: - 2.17.5 was released on Jan 22 2017 - 2.17.6 was released on March 8 2017 - 2.18.2 was released on Jan 30 2017 ## Mailing list activity: - Mailing list activity stays at a high level.
## Description: - Apache Camel is a powerful open source integration framework based on known Enterprise Integration Patterns. ## Issues: - there are no issues requiring board attention at this time ## Activity: - We are receiving many contributions from our contributors (via GitHub pull requests). - We are focusing the development of the next minor release Apache Camel 2.19.0. - Some people started to work on some bigger changes for the next major release Apache Camel 3.0.0. - With the community, we are looking for a new logo for our project. ## Health report: - The project is super healthy, active and stays at a high level - At ApacheCon Europe 2016, we had 5 presentations about Apache Camel from PMC's, committers and contributers/users. ## PMC changes: - Currently 29 PMC members. - Luca Burgazzoli was added to the PMC on Thu Oct 06 2016 ## Committer base changes: - Currently 54 committers. - No new committers added in the last 3 months - Last committer addition was Nicola Ferraro at Mon Aug 22 2016 ## Releases: - 2.16.4 was released on Sun Sep 25 2016 - 2.17.4 was released on Wed Nov 30 2016 - 2.18.0 was released on Sun Oct 09 2016 - 2.18.1 was released on Fri Dec 02 2016 ## Mailing list activity: - Mailing list activity stays at a high level.
Apache Camel is a powerful open source integration framework based on known
Enterprise Integration Patterns.
Project Status
--------------
There are no issues requiring board attention at this time.
Community
---------
The project is healthy, active and stays at a high level. We got 3 new
contributors who signed the ICLA in this reporting periode.
Currently 28 PMC members. Last PMC addition:
Gregor Zurowski was added as a PMC on Fri Dec 04 2015
Currently 54 committers. Last committer addition:
Arno Noordover was added as a committer on Thu Jun 16 2016
Nicola Ferraro was added as a committer on Mon Aug 22 2016
Nicola Ferraro was added as a committer on Mon Aug 22 2016
Mailing list activity stays on a high level:
users@camel.apache.org:
913 subscribers (up 13 in the last 3 months)
1168 emails sent to list (1626 in previous quarter)
dev@camel.apache.org:
349 subscribers (up 4 in the last 3 months)
678 emails sent to list (798 in previous quarter)
issues@camel.apache.org:
83 subscribers (up 1 in the last 3 months)
2012 emails sent to list (2413 in previous quarter)
256 JIRA tickets created and 237 JIRA tickets closed/resolved in the last 3
months
Community Objectives
--------------------
We are receiving many contributions from our contributors (via GitHub pull
requests).
We are focusing the development of the next minor release Apache Camel
2.18.0.
Some people started to work on some bigger changes for the next major release
Apache Camel 3.0.0.
Releases
--------
2.17.2 was released on Fri Jul 01 2016
## Description:
- Apache Camel is a powerful open source integration framework based on
known Enterprise Integration Patterns.
## Issues:
- There are no issues requiring board attention at this time
## Activity:
- We resolved a trademark issue on GitHub with a project called Camel.Net.
- We are focusing the development of the next minor release Apache Camel
2.18.0.
## Health report:
- The project is healthy, active and stays at a high level.
- We got 10 new contributors who signed the ICLA in this reporting periode.
## PMC changes:
- Currently 28 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Gregor Zurowski on Fri Dec 04 2015
## Committer base changes:
- Currently 52 committers.
- New commmitters:
- Luca Burgazzoli was added as a committer on Thu Apr 07 2016
- Stephan Siano was added as a committer on Tue Apr 26 2016
## Releases:
- 2.15.6 was released on Thu Mar 31 2016
- 2.16.3 was released on Sat Apr 09 2016
- 2.17.0 was released on Sat Mar 26 2016
- 2.17.1 was released on Sun May 08 2016
## Mailing list activity:
- users@camel.apache.org:
- 903 subscribers (up 14 in the last 3 months):
- 1704 emails sent in the past 3 months (1349 in the previous cycle)
- dev@camel.apache.org:
- 346 subscribers (up 9 in the last 3 months):
- 842 emails sent in the past 3 months (634 in the previous cycle)
- commits@camel.apache.org:
- Currently: 63 subscribers (up 4 in the last 3 months):
- 2574 emails sent in the past 3 months (1938 in the previous cycle)
- issues@camel.apache.org:
- 82 subscribers (up 7 in the last 3 months):
- 2526 emails sent in the past 3 months (2088 in the previous cycle)
- notifications@camel.apache.org:
- 8 subscribers (up 1 in the last 3 months)
## JIRA activity:
- 346 JIRA tickets created in the last 3 months
- 411 JIRA tickets closed/resolved in the last 3 months
Apache Camel is a powerful open source integration framework based on
known Enterprise Integration Patterns.
## Issues:
- There are no issues requiring board attention at this time
## Activity:
- CVE-2015-5344 (Apache Camel's XStream usage is vulnerable to Remote Code
Execution attacks) is fixed, released and published.
- CVE-2015-5348 (Apache Camel's Jetty usage is vulnerable to Java object
de-serialisation vulnerability) is fixed, released and published.
- We are focusing the development of the next minor release Apache Camel
2.17.0.
## Health report:
- The project is healthy, active and stays at a high level.
- We got 2 new contributors who signed the ICLA in this reporting periode.
## PMC changes:
- Currently 28 PMC members.
- Gregor Zurowski was added to the PMC on Fri Dec 04 2015
## Committer base changes:
- Currently 50 committers.
- Antonin Stefanutti was added as a committer on Wed Mar 02 2016
## Releases:
- 2.15.5 was released on Mon Nov 30 2015
- 2.16.2 was released on Wed Jan 27 2016
## Mailing list activity:
- users@camel.apache.org:
- 889 subscribers (up 6 in the last 3 months):
- 1374 emails sent to list (1345 in previous quarter)
- dev@camel.apache.org:
- 334 subscribers (up 5 in the last 3 months):
- 679 emails sent to list (557 in previous quarter)
- issues@camel.apache.org:
- 74 subscribers (up 4 in the last 3 months):
- 2027 emails sent to list (1804 in previous quarter)
- notifications@camel.apache.org:
- 7 subscribers (up 1 in the last 3 months)
## JIRA activity:
- 277 JIRA tickets created in the last 3 months
- 286 JIRA tickets closed/resolved in the last 3 months
Apache Camel is a powerful open source integration framework based on known Enterprise Integration Patterns. Project Status -------------- * There are no issues that require the board attention. * The project is healthy, active and stays at a high level. Community --------- * Some of the current PMC expressed their wish to keep up with the current chair. Because there was no further discussion started who could be a good successor for the current chair, the current chair agreed to continue in his role. * We discovered a trademark issue, a GitHub project called camel.js (https://github.com/matthewcodes/camel.js). The project is now renamed to oneHumpOrTwo.js (https://github.com/matthewcodes/oneHumpOrTwo.js). Some of the content still needs to be updated. * We didn't got a new contributor who signed the ICLA in this reporting periode. * The community stays at a high level (328 subscribers at dev@; 883 subscribers at users@) * The community is active and questions being answered in short term. * Avg. 440 mails per month on the users mailing list in September 2015 - November 2015 * Avg. 199 mails per month on the dev mailing list in September 2015 - November 2015 * Avg. 298 committs per month in September 2015 - November 2015 Community Objectives -------------------- * The camel-extra project moved to GitHub [1]. * We are focusing the development of the next minor release Apache Camel 2.17.0. * The Camel PMC voted to allow Camel committers to update the Camel dist/release SVN repo which is necessary to publish a new release. Project Composition ------------------- * Sergey Beryozkin was added as new committer in this reporting period * Aki Yoshida, Andrea Cosentino, Jean-Baptiste Onofré and Gregor Zurowski were added as new PMC member in this reporting period Releases -------- * 2.15.5 (Nov 30 2015) * 2.16.1 (Nov 22 2015) * 2.14.4 (Nov 11 2015) * 2.15.4 (Oct 28 2015) * 2.16.0 (Oct 08 2015) [1] https://github.com/camel-extra/camel-extra
Apache Camel is a powerful open source integration framework based on known Enterprise Integration Patterns. Project Status -------------- * There are no issues that require the board attention. * The project is healthy, active and stays at a high level. Community --------- * The current PMC chair would like to resign and we are discussing who could take over this role. * On 15th July one of our PMC discovered a trademark issue, a GitHub project called camel-labs. Unfortunately, some of the Camel PMC's was involved in this project. On 31nd July the project was renamed and the issues was solved. * We got 1 new contributors who signed the ICLA. * The community stays at a high level (328 subscribers at dev@; 873 subscribers at users@) * The community is active and questions being answered in short term. * Avg. 355 mails per month on the users mailing list in June 2015 - August 2015 * Avg. 116 mails per month on the dev mailing list in June 2015 - August 2015 * Avg. 282 commits per month in June 2015 - August 2015 Community Objectives -------------------- * The camel-extra project [1] is now read-only. The people didn't received any information how to proceed to move to SF. This wasn't a good experience, also because all of the camel-extra committers want to move to GitHub. * We are focusing the development of the next minor release Apache Camel 2.16.0. Project Composition ------------------- * no new committer was added in this reporting period * the last committer was added at 19/05/2015 * no new PMC member was added in this reporting period * the last PMC member was added at 04/24/2014 Releases -------- * 2.15.3 (20/08/2015) [1] https://code.google.com/a/apache-extras.org/p/camel-extra/
Apache Camel is a powerful open source integration framework based on known Enterprise Integration Patterns. Project Status -------------- * There are no issues that require the board attention. * The project is healthy, active and stays at a high level. Community --------- * We got 7 new contributors who signed the ICLA. * The community stays at a high level (323 subscribers at dev@; 857 subscribers at users@) * The community is active and questions being answered in short term. * Avg. 578 mails per month on the users mailing list in March 2015 - May 2015 * Avg. 238 mails per month on the dev mailing list in March 2015 - May 2015 * Avg. 534 committs per month in March 2015 - May 2015 Community Objectives -------------------- * We are discussing the camel-extra move to GitHub, as Google-Code will shut down the service is a few month. We are missing the recommendation from com-dev where the apache-extra projects should move to [1]. Without a recommendation, we will move the camel-extra project to GitHub, because it's the preferred place for these committers. * We are focusing the development of the next minor release Apache Camel 2.16.0. * We handled the security issues CVE-2015-0263 and CVE-2015-0264. Thanks to Stephan Siano for reporting it to us. Project Composition ------------------- * Andrea Cosentino (22/04/2015) and Franz Forsthofer (19/05/2015) were added * the last committer was added at 11/06/2014 * no new PMC member was added in this reporting period * the last PMC member was added at 04/24/2014 Releases -------- * 2.14.3 (01/06/2015) * 2.15.2 (04/05/2015) * 2.15.1 (01/04/2015) [1] http://s.apache.org/Cej
Apache Camel is a powerful open source integration framework based on known Enterprise Integration Patterns. Project Status -------------- * There are no issues that require the board attention. * The project is healthy, active and stays at a high level. Community --------- * We got 4 new contributors who signed the ICLA. * The community stays at a high level (323 subscribers at dev@; 825 subscribers at users@) * The community is active and questions being answered in short term. * Avg. 432 mails per month on the users mailing list in December 2014 - February 2015 * Avg. 145 mails per month on the dev mailing list in December 2014 - February 2015 * Avg. 426 committs per month in December 2014 - February 2015 Community Objectives -------------------- * We finalized the Apache Camel 2.15.0 release * We are started the development of the next minor release Apache Camel 2.16.0. Project Composition ------------------- * no new committer was added in this reporting period * the last committer was added at 11/06/2014 * no new PMC member was added in this reporting period * the last PMC member was added at 04/24/2014 Releases -------- * 2.13.4 (03/10/2015) * 2.14.1 (12/16/2014) * 2.14.2 (03/10/2015) * 2.15.0 (03/10/2015)
Apache Camel is a powerful open source integration framework based on known Enterprise Integration Patterns. Project Status -------------- * There are no issues that require the board attention. * The project is healthy, active and stays at a high level. Community --------- * We got 5 new contributors who signed the ICLA. * The community stays at a high level (321 subscribers at dev@; 800 subscribers at users@) * The community is active and questions being answered in short term. * Avg. 552 mails per month on the users mailing list in September 2014 - November 2014 * Avg. 183 mails per month on the dev mailing list in September 2014 - November 2014 * Avg. 647 commits per month in September 2014 - November 2014 Community Objectives -------------------- * We are planning to release Apache Camel 2.14.1 in the next weeks. * Adding new features and improvements to Apache Camel in version 2.15.0. Project Composition ------------------- * One new committer was added in this reporting period * Colm O hEigeartaigh 11/06/2014 * no new PMC member was added in this reporting period * the last PMC member was added at 04/24/2014 Releases -------- * 2.12.5 (10/27/2014) * 2.13.3 (10/31/2014)
Apache Camel is a powerful open source integration framework based on known Enterprise Integration Patterns. Project Status -------------- * There are no issues that require the board attention. * The project is healthy, active and stays at a high level. Community --------- * We got 3 new contributors who signed the ICLA. * We have two talks scheduled at the next ApacheCon EU: * Using Websocket With CXF And Camel - Akitoshi Yoshida * Apache Camel In The Belly Of The Docker Whale - Henryk Konsek * The community stays at a high level (307 subscribers at dev@; 772 subscribers at users@) * The community is active and questions being answered in short term. * Avg. 618 mails per month on the users mailing list in June 2014 - August 2014 * Avg. 182 mails per month on the dev mailing list in June 2014 - August 2014 * Avg. 347 committs per month in June 2014 - August 2014 Community Objectives -------------------- * We finalized the Spring 4 and Java 8 support. * We are planning to release Apache Camel 2.14.0 next week. * Adding new features and improvements to Apache Camel in version 2.15.0. Project Composition ------------------- * no new committer was added in this reporting period * the last committer was added at 06/11/2014 * no new PMC member was added in this reporting period * the last PMC member was added at 04/24/2014 Releases -------- * 2.12.4 (07/06/2014) * 2.13.2 (07/06/2014)
Apache Camel is a powerful open source integration framework based on known Enterprise Integration Patterns. Project Status -------------- * There are no issues that require the board attention. * The project is healthy, active and stays at a high level. Community --------- * We got 5 new contributors who signed the ICLA. * The community stays at a high level (297 subscribers at dev@; 760 subscribers at users@) * The community is active and questions being answered in short term. * Avg. 607 mails per month on the users mailing list in March 2014 - May 2014 * Avg. 123 mails per month on the dev mailing list in March 2014 - May 2014 * Avg. 290 committs per month in March 2014 - May 2014 Community Objectives -------------------- * We are finalizing Apache Camel 2.14.0 to get it out of the door during the next reporting period. Project Composition ------------------- * Dhiraj Bokde was added as committer (04/23/2014) * Bilgin Ibryam was added as new PMC member (04/24/2014) * Grzegorz Grzybek was added as committer (06/11/2014) * Gregor Zurowski was added as committer (06/11/2014) Releases -------- * 2.13.0 (03/18/2014) * 2.13.1 (05/13/2014)
Apache Camel is a powerful open source integration framework based on known Enterprise Integration Patterns. Project Status -------------- * There are no issues that require the board attention. * The project is healthy, active and stays at a high level. Community --------- * Packtpub published one new book about Apache Camel: http://www.packtpub.com/apache-camel-developers-cookbook/book * The previous CamelOne conference is now part of RedHat's DevNation conference which is planned for 04/13/2014 - 04/17/2014 (http://www.devnation.org/#agenda) * We will have two talks at ApacheCon 2014 in Denver: * http://s.apache.org/8un * http://s.apache.org/TPG * We got 3 new contributors who signed the ICLA. * The community stays at a high level (289 subscribers at dev@; 732 subscribers at users@) * The community is active and questions being answered in short term. * Avg. 692 mails per month on the users mailing list in December 2013 - February 2014 * Avg. 142 mails per month on the dev mailing list in December 2013 - February 2014 * Avg. 275 commits per month in December 2013 - February 2014 Community Objectives -------------------- * We handled the security issues CVE-2014-0002 and CVE-2014-0003. Thanks to David Jorm for reporting it to us. * We are finalizing Apache Camel 2.13.0 to get it out of the door soon. * We are discussing new features for the next minor release Apache Camel 2.14.0. Project Composition ------------------- * No new committer in this reporting period (last one joined 10/16/2013) * No new PMC member in this reporting period (last one joined 10/05/2013) Releases -------- * 2.12.3 (02/21/14) * 2.11.4 (02/16/14) * 2.11.3 (01/13/14)
Apache Camel is a powerful open source integration framework based on known Enterprise Integration Patterns. Project Status -------------- * The project is active and stays at a high level. * There was a bit of community contention this period when a committer added a target to Camel's maven plugins to run a third party (but open source) console with all branding, marketing links, etc... intact and not allowing the Camel community any control over the display of the Camel portion. The PMC (in particular 4 PMC members had to issue specific vetos) did decide to revert this change, but discussion did degrade into various personal attacks, attacks against employers, etc... This seems to happen very often when there is a disagreement in Camel and has caused many people to not feel they can speak up and disagree or state their opinions. Community --------- * Packtpub published two new book about Apache Camel, one was written by one of our committers: http://www.packtpub.com/apache-camel-message-routing/book http://www.packtpub.com/apache-camel-messaging-system/book * JAX-Magazine published two article about Apache Camel which was written by one of our PMC member: http://jaxenter.com/jax-magazine/JAX-Magazine-2013-05 http://jaxenter.com/tutorial-integrating-with-apache-camel-48211.html * The community stays at a high level (276 subscribers at dev@; 711 subscribers at users@) * The community is active and questions being answered in short term. * Avg. 948 mails per month on the users mailing list in September 2013 - November 2013 * Avg. 177 mails per month on the dev mailing list in September 2013 - November 2013 * Avg. 453 committs per month in September 2013 - November 2013 Community Objectives -------------------- * We handled the security issue CVE-2013-4330. Thanks to security@ for their support. * Working on the Camel 2.13.0 release. Project Composition ------------------- * Christian Posta was added as committer (10/16/2013) * James Carman was added as committer (10/05/2013) * James Carman was added as new PMC member (10/05/2013) Releases -------- * 2.12.2 (11/27/2013) * 2.12.1 (09/22/2013) * 2.11.2 (09/24/2013) * 2.10.7 (09/19/2013) * 2.9.8 (09/20/2013)
There is a similar issue with ActiveMQ where a console was introduced with branding intact that made it appear that the console vendor "owned" the project. Shane notes that in general, pmcs must clearly separate apache project from downstream commercial products. It's fine if people add plugins when they use our stuff, or even if they re-ship their own product based on our stuff. But when the average user gets an Apache product, it should look like an Apache product, and not a third party. AI: Chris: will join discussion on camel-dev list
Apache Camel is a powerful open source integration framework based on known Enterprise Integration Patterns. Project Status -------------- * There are no issues that require the board attention. * The project is healthy, active and stays at a high level. Community --------- * We delivered our first releases coming from our new GIT repository. * Red Hat was organizing the CamelOne 2013 conference. The slides are available at http://camelone.com/apache-camel-conference-2013/camelone_agenda_2013/. * The community stays at a high level (183 subscribers at dev@; 503 subscribers at users@) * The community is active and questions being answered in short term. * Avg. 811 mails per month on the users mailing list in June 2013 - August 2013 * Avg. 154 mails per month on the dev mailing list in June 2013 - August 2013 * Avg. 339 commits per month in June 2013 - August 2013 Community Objectives -------------------- * Starting to work on Camel 2.13.0 * The interest on the new major version Camel 3.0.0 has decreased Project Composition ------------------- * Aki Yoshida was added as a new committer (07/08/2013) * Rich Newcomb was added as committer (07/08/2013) * Raul Kripalani was added as new PMC member (07/07/2013) Releases -------- * 2.12.0 (09/09/2013) * 2.11.1 (07/14/2013) * 2.9.7 (07/03/2013) * 2.9.6 (06/23/2013)
Apache Camel is a powerful open source integration framework based on known Enterprise Integration Patterns. Project Status -------------- * There are no issues that require the board attention. * The project is healthy, active and stays at a high level. Community --------- * We switched from SVN to GIT which was a bit bumpy because of the missing announcement from INFRA when the SVN repo was going read-only. But we are fine now and preparing our first release which comes from our new GIT repo. Thank's INFRA! * Red Hat is organizing the CamelOne 2013 conference in Boston on June 10th - 11th (http://camelone.com/). ConCom and the Camel PMC's were involved in the planning of this event. * The community stays at a high level (183 subscribers at dev@; 503 subscribers at users@) * The community is active and questions being answered in short term. * Avg. 958 mails per month on the users mailing list in March 2013 - May 2013 * Avg. 205 mails per month on the dev mailing list in March 2013 - May 2013 * Avg. 348 committs per month in March 2013 - May 2013 * No new committers in this reporting period (last one joined in Dec 2012) * No new PMC members in this reporting period (last one joined in Dec 2012) Community Objectives -------------------- * Working on Camel 2.12.0 which is our last planned 2.x release * Finalizing our "pre" Camel 3.0 work * Discussing and finalizing the Camel 3.0.0 road map Releases -------- * 2.11.0 (04/17/2013) * 2.9.7 (04/24/2013)
Apache Camel is a powerful open source integration framework based on known Enterprise Integration Patterns. Project Status -------------- * There are no issues that require the board attention. * The project is healthy, active and stays at a high level. Community --------- * At ApacheCon NA 2013 we had 4 talks about Apache Camel. * Red Hat planned (and will announce in short time) the CamelOne 2013 conference in Boston on June 10th - 11th (http://camelone.com/). Rob Davies (Camel PMC member and Red Hat employee), ConCom and the Apache Camel PMC are working together to ensure that this event will meet the ASF trademark and ConCom guidelines. Please find the relevant mail thread at http://s.apache.org/Hq1 * The community stays at a high level (183 subscribers at dev@; 503 subscribers at users@) * The community is active and questions being answered in short term. * Avg. 805 mails per month on the users mailing list in Dec 2012 - Feb 2013 * Avg. 244 mails per month on the dev mailing list in Dec 2012 - Feb 2013 * Avg. 299 committs per month in Dec 2012 - Feb 2013 * No new committers in this reporting period (last one joined in Dec 2012) * No new PMC members in this reporting period (last one joined in Dec 2012) Community Objectives -------------------- * Finalizing our working on Camel 2.11.0 * Discussing Camel 3.0.0 Releases -------- * 2.10.4 (02/22/2013) * 2.9.6 (03/07/2013)
Apache Camel is a powerful open source integration framework based on known Enterprise Integration Patterns. Project Status -------------- * There are no issues that require the board attention. * The project is healthy, active and stays at a high level. Community --------- * "Java aktuell - Das Magazin" and "Java Spektrum" published articles about Apache Camel. * At ApacheCon EU 2012 we had 4 talks about Apache Camel. * The community stays at a high level (183 subscribers at dev@; 503 subscribers at users@) * The community is active and questions being answered in short term. * Avg. 795 mails per month on the users mailing list in Sep 2011 - Nov 2012 * Avg. 247 mails per month on the dev mailing list in Sep 2011 - Nov 2012 * Avg. 402 commits per month in Sep 2011 - Nov 2012 * We welcome Henryk Konsek, Raul Kripalani and Scott England-Sullivan as new committer. * We welcome Babak Vahdat and Charles Moulliard in our PMC. * After acquiring FuseSource by RedHat and inviting two committers, our PMC of 21 is affiliated with 7 different unique organizations (13 of them are affiliated with a single company). * Our additional 17 committers belongs to 14 different unique organizations (4 of them are affiliated with the same single company mentioned above). Community Objectives -------------------- * Finalizing our working on Camel 2.11.0 * Plan the work for Camel 3.0.0 Releases -------- * 2.9.4 * 2.9.5 * 2.10.2 * 2.10.3
Apache Camel is a powerful open source integration framework based on known Enterprise Integration Patterns. Project Status -------------- * There are no issues that require the board attention. * The project is healthy, active and stays at a high level. Community --------- * Apache Camel in the news: * "Java aktuell - Das Magazin", "Java Magazin", "Heise Developer" and "h-online" published articles about Apache Camel * We celebrated our fifth birthday: http://s.apache.org/PZ7 * We will have 4 talks at ApacheCon EU 2012 and also a talk at JavaOne 2012 * The community stays at a high level * The community is active and questions being answered in short term. * Avg. 781 mails per month on the users mailing list in Jun 2011 - Aug 2012 * Avg. 239 mails per month on the dev mailing list in Jun 2011 - Aug 2012 * Avg. 275 commits per month in Jun 2011 - Aug 2012 * No new committer in this reporting period (last one joined in March 2012) * We are watching a few good candidates which we probably add in the next reporting period * No new PMC members in this reporting period (last one joined in November 2011) Community Objectives -------------------- * Working on Camel 2.11.0 * Concrete the Camel 3.0.0 road map Releases -------- * 2.10.1 * 2.10.0 * 2.9.3 * 2.8.6
Apache Camel is a powerful open source integration framework based on known
Enterprise Integration Patterns.
Project Status
--------------
* There are no issues that require the board attention.
* The project is healthy, active and stays at a high level.
Community
---------
* CamelOne 2012 was held from 5/15/2012 - 5/16/2012 in Boston, MA
(http://CamelOne.com)
* It was a great success and a really cool and fun conference.
* The attendance was a lot higher this year (~ +60%) which shows the
popularity of the Camel project.
* Apache Camel in the news:
* http://www.javacodegeeks.com/2012/03/integration-framework-comparison-spring.html?m=1
* The community stays at a high level:
* 503 subscribers to the users mailing list (+0 %)
* 183 subscribers to the dev mailing list (+0 %)
* The community is active
* Avg. 863 mails per month on the users mailing list in
Mar 2011 - Mai 2012 (+25 %)
* Avg. 167 mails per month on the dev mailing list in
Mar 2011 - Mai 2012 (-15 %)
* Avg. 308 commits per month in Mar 2011 - Mai 2012 (-17 %)
* No new committer in this reporting period (last one joined in March 2012)
* No new PMC members in this reporting period (last one joined in November
2011)
Community Objectives
--------------------
* Closing down the Camel 2.10.0 release which will resolve more than 400
issues
* 15 new components, support for Java 7, support for Spring 3.1, ...
* Start working on Camel 2.11.0
* Concrete the Camel 3.0.0 road map
Releases
--------
* 2.8.5
* 2.9.2
Apache Camel is a powerful open source integration framework based on known
Enterprise Integration Patterns.
Project Status
--------------
* There are no issues that require the board attention.
* The project is healthy and continues to grow.
* Progress has been made toward using the CXF developed export utility to
migrate the website from rsync to svnpubsub as per guidelines from the
Infrastructure team.
Community
---------
* The community grows:
* 503 subscribers to the users mailing list (+3 %)
* 183 subscribers to the dev mailing list (+2 %)
* The community is active
* Avg. 688 mails per month on the users mailing list in Dec 2011 - Feb 2012
* Avg. 196 mails per month on the dev mailing list in Dec 2011 - Feb 2012
* Avg. 507 commits per month in Dec 2011 - Feb 2012
* Babak Vahdat (bvahdat) joined the community as a new committer.
* Bilgin Ibryam (bibryam) joined the community as a new committer.
* No new PMC members since the last board report (December 2011)
* We are on track to increasing diversity.
* Our PMC of 19 is affiliated with 6 different unique organizations (11 of
them are affiliated with a single company).
* Our additional 16 committers belongs to 14 different unique organizations
(3 of them are affiliated with the same single company mentioned above).
* Fusesource planned and announced a CamelOne conference at May 15th - 16th
(http://fusesource.com/apache-camel-conference-2012/). ConCom approved to use
the name CamelOne for this event. The Camel PMC, especially Jeff Genender,
Rob Davies, Claus Ibsen and myself will make sure this event will meet the
ASF trademark and ConCom guidelines.
Community Objectives
--------------------
* Our first objective is to continue with the development for Camel 2.10.0.
* Beside this, we continues development with new features and fixes for the
camel-2.8.x and 2.9.x maintenance branches.
* In the next weeks we have to concrete our schedule for Camel 3.0.0 which
will be a bigger release.
Branding Status
---------------
* Project Naming And Descriptions : Compliant
* Website Navigation Links : Compliant
* Trademark Attributions : Compliant
* Logos and Graphics : Compliant
* Project Metadata : Compliant
Releases
--------
* 2.7.5 (the 2.7.x series continues to be maintained under a "security and
important fixes only" profile)
* 2.8.4
* 2.9.0
* 2.9.1
Apache Camel is a powerful open source integration framework based on known Enterprise Integration Patterns. Project Status -------------- * The project is healthy and continues to grow. * There are no issues that require the board attention. * We are still working on increasing diversity. Community --------- * The community grows: * 489 subscribers to the users mailing list * 179 subscribers to the dev mailing list * The community is active (909 mails on the users mailing list in November 2011 - 577 in the last board report for October 2011) * Apache Camel has been presented at ApacheCon in Vancouver by Hadrian Zbarcea and Daniel Kulp. * Set up back port guidelines for our maintenance branches. * We added a new mailing list issues@ to which all our JIRA notifications are forwarded to have less noise on dev@. * No new committers since the last board report (November 2011) * No new PMC members since the last board report (November 2011) Community Objectives -------------------- * Our current objective is to release Camel 2.9.0 soon. We did a few preparations for bigger refactorings which we plan for Camel 3.0.0, added new components, fixed issues and added new features and improvements. * Our second objective is to start with the development for Camel 2.10.0 in the next days. * Besides all this we continues development with new features and fixes for the camel-2.7.x and 2.8.x maintenance branches. Branding Status --------------- * Project Naming And Descriptions : Compliant * Website Navigation Links : Compliant * Trademark Attributions : Compliant * Logos and Graphics : Compliant * Project Metadata : Compliant Releases -------- * 2.8.3
WHEREAS, the Board of Directors heretofore appointed Hadrian Zbarcea to the office of Vice President, Apache Camel, and WHEREAS, the Board of Directors is in receipt of the resignation of Hadrian Zbarcea from the office of Vice President, Apache Camel, and WHEREAS, the Project Management Committee of the Apache Camel project has chosen by vote to recommend Christian Mueller as the Successor to the post; NOW, THEREFORE, BE IT RESOLVED, that Hadrian Zbarcea is relieved and discharged from the duties and responsibilities of the office of Vice President, Apache Camel, and BE IT FURTHER RESOLVED, that Christian Mueller be and hereby is appointed to the office of Vice President, Apache Camel, to serve in accordance with and subject to the direction of the Board of Directors and the Bylaws of the Foundation until death, resignation, retirement, removal or disqualification, or until a successor is appointed. Special Order 7A, Resolution to Change the Apache Camel Project Chair, was approved by Unanimous Vote of the directors present.
Apache Camel is a powerful open source integration framework based on known Enterprise Integration Patterns. Community: * There are a few issues that require the board attention and the PMC will continue to work to fix them. * The project is healthy and continues to grow * One committer added to the project: Ioannis Canellos (iocanel) * One member added to the PMC: Dan Kulp (dkulp) * A resolution to change the PMC Chair was submitted for the board consideration this month. Development: * Development continues with new features and fixes on trunk and the camel-2.7.x and 2.8.x maintenance branches * The number of issues fixed on trunk is rather large and we decided to issue a RC to allow for better testing in the community before the final 2.9.0 Releases: * 2.9.0-RC1
Jim reports that discussions have settled down and he is comfortable with how things are going. Shane plans to follow up. Dan reports that additional ASF members have been added to the PMC. With the change of chair, we will continue with (at least) one more month of monthly reporting.
Apache Camel is a powerful open source integration framework based on known Enterprise Integration Patterns. Community: * There are a few issues that require the board intervention * The project is healthy and continues to grow * Three more PMC members moved to emeritus status: nsandhu, ammulder and jlaskowski * One member added to the PMC: jgenender Development: * Development continues with new features and fixes on trunk and the camel-2.7.x and 2.8.x maintenance branches Releases: * 2.7.4 * 2.8.2
This report is approved, and the board would like a report from the new chair in November.
Apache Camel is a powerful open source integration framework based on known Enterprise Integration Patterns. Community: * There are a few issues that require the board intervention. * The project is healthy and continues to grow * Three PMC members moved to emeritus status: djencks, bsnyder and romkal Development: * Development continues with new features and fixes on trunk and the camel-2.7.x and 2.8.x maintenance branches * Brian Fox reported LGPL dependencies shipped with exactly 2 camel components (camel-web and camel-web-standalone) in version 2.4.0 released more than a year ago on 06/12/2010. I can confirm his findings, not sure what the right solution is though, will discuss this in the PMC. Releases: * 2.8.1
The Camel PMC might need help resolving their trademark issue. AI Jim: help PMC with the trademark issue. AI Hadrian: report again next month.
Apache Camel is a powerful open source integration framework based on known Enterprise Integration Patterns. Community: * There are a few issues that require the board intervention. * The project grows at the same intense pace. * Freeman Fang (fang) joined the community as a new committer. * We added an "Estimated Complexity" custom field to jira to encourage the community contributions. Development: * Development continues with new features and fixes on trunk and the camel-2.7.x and 2.8.x maintenance branches Releases: * None
Since the issues were not resolved during the slow vacation season, a report will be requested for next month.
AI Hadrian: report in more detail on the PMC issues.
Apache Camel is a powerful open source integration framework based on known Enterprise Integration Patterns. Community: * There are a few issues that require the board intervention. * The community continues to grow * Mailing lists continue to be very active. * diversity in the project is increasing * 3 new committers joined the project: dkulp, jbonofre, dvaleri Development: * Development continues with new features and fixes on trunk and the camel-2.7.x maintenance branch * We intend to continue the practice of issuing patch releases more frequently Releases: * Camel 2.7.3 (under vote) * Camel 2.8.0 (under vote) Issues: * The community needs more diversity.
Camel to produce an additional report next month.
AI: Jim to describe our expectations of a chair, and how to balance with commercial interests, and the need to avoid personal attacks on mailing lists.
Guillaume noted that the Branding policy "requests" rather than "requires" attribution. If necessary, Guillaume and Shane to follow up on trademark mailing list.
Apache Camel is a powerful open source integration framework based on known Enterprise Integration Patterns. Community: * No issues that require the board attention. * The community continues to grow at the fast paced rhythm we're used too * We increased the frequency of releases and issue more patch releases * We had a security vulnerability (XSS) reported against Camel which we resolved. * Mailing lists continue to be very active. * Fusesource hosted a CamelOne conference in May * diversity in the project is increasing * 2 more companies announced support offerings around Camel. * 1 new committer joined the project: boday * 1 committer joined the PMC: joed * The PMC is in the process of assessing the trademarks compliance and we'll have detailed answers in the next report. Development: * Development continues with new features and fixes on trunk * A Camel 2.8.0 release is planned for this month. Releases: * Camel 2.7.0 * Camel 2.7.1 * Camel 2.7.2
Apache Camel is a powerful open source integration framework based on known Enterprise Integration Patterns. Community: * No issues that require the board attention. * The community continues to grow and submit contributions. * Mailing lists continue to be very active. * 2 new committers joined the project: rickette, tjsnell * Fusesource planned and announced a CamelOne conference in May The Camel PMC contacted Fusesource and Rob Davies, Camel PMC member and Fusesource manager, ensured us that the CamelOne event sponsored by FuseSource will meet the ASF trademark guidelines as defined by the current draft posted online. Development: * Development continues with new features and fixes on trunk * A Camel 2.7.0 release is planned for this month. Releases: * Camel 2.6.0 released.
Apache Camel is a powerful open source integration framework based on known Enterprise Integration Patterns. Community: * No issues that require the board attention. * The project community is growing and becoming more diverse. * Community contributions increasing at a steady pace. * Mailing lists continue to be very active. * 5 committers joined the PMC: krasserm, slewis, akarpe, cschneider, cmueller * 1 new committer joined the project: joed Development: * Development continues with new features and fixes on trunk * Planning started for a new Camel 3.0 * The PMC ran a survey during the month of Oct on how camel is used * The last maintenance release of camel 1.x under voting, there will be no new development for camel 1.x * A Camel 2.6.0 release is planned for this month as well. Releases: * Camel 2.5.0 released. * Camel 1.6.4 is being released (under vote)
Community: * No issues that require the board attention. * The project community continue to grow at the same fast pace. * No new committers or changes in the PMC Development: * Development continues with new features and fixes on trunk * The community started a discussion about moving to a new major release Camel 3.0 * On the 1.x branch we discussed and agree to have one final release in Q4 and then discontinue development of that branch. * We corrected the few issues we had with xml files missing the AL2 license. There are only a few text test files that miss the license now, which I am working on fixing. * We are planning a new camel 2.5.0 release this week. Releases: * Camel 2.4.0 released.
Community: * No issues that require the board attention. * The community continues to grow and be very active. * We welcome Christian Schneider as a new committer (already a cxf committer) * We welcome Christian Mueller as a new committer (waiting for an account) * Other contributors submitted iclas and volunteer to help out with the wiki doc Development: * Development continues at an intense pace on trunk * Development on the 1.x release branch slowed down. Although still in use, most other projects we know of that use Camel migrated to 2.x. We are currently discussing when would be the right time to discontinue development for the 1.x version. * We are looking at the quality of our releases and found it in extremely good shape. The rat plugin revealed a few xml test data files that are missing the apache header and we are correcting that (camel has over 4700 unit tests). Releases: * Camel 2.3.0 released. * Camel 1.6.3. maintenance released.
Community: * No issues that require the board attention. * The community continues to be very active. * Two new committers added: Ashwin Karpe and Stanley Lewis * There are a few other very active contributors on our radar Development: * Development continues at the same intense pace on both trunk and maintenance 1.x * No plans to discontinue support for camel 1.x yet, but we may need to discuss that soon. * Most of the other projects using camel (we know of) already upgraded to camel 2.x Releases: * Camel 2.2.0 released.
Community: * No issues that require the board attention. * Another busy quarter with increased contributions from the community. * Mailing lists continue to be very active. * Martin Krasser accepted as new committer. * We are keeping an eye on a few other active contributors to become committers. Development: * Development continues on both 1.x maintenance branch and trunk. * Another maintenance release of the 1.x branch planned for next quarter. * Camel 2.2.0 planned for next quarter. Releases: * Camel 1.6.2 (maintenance) released. * Camel 2.1.0 released.
Community: * The new and improved Camel 2.0 was released. * Activity continues at the usual high pace. * Mailing lists keep their top 10 ranking at nabble. * No new committers. Development: * Development continues on both 1.x maintenance branch and trunk. * Community contributions keep coming in. * Maintenance release of the 1.x branch planned. Releases: * Camel 2.0-M3 released. * Camel 2.0.0 released.
Community: * We saw the usual level of intense activity this quarter. * The community continues to grow. * Charles Moulliard is a new committer. Development: * Development continues on both 1.x maintenance branch and trunk. * Camel continues to gain ground as an integration framework. * Final release of Camel 2.0 expected in a month or so. Releases: * Camel 1.6.1 maintenance release. * Camel 2.0-M2 just released.
Can the PRC help raise buzz/awareness for Camel 2.0? No action taken.
Community: * The Camel community continues to be very active. * Camel is participating in the Google SOC with 2 projects. * No new committers. Development: * Lots of contributions from committers and community on trunk. * New components proposed by the community are under evaluation. * Final release of Camel 2.0 and 1.x maintenance release planned for this quarter. Releases: * None this month.
Apache Camel PMC Board Report, March 2009 Community: * The Camel community continues to be very active and growing. * Increased traffic on the development and user lists indicate wider adoption of Camel. * No new committers. Development: * Lots of contributions from committers and community on trunk. * We just issued the first milestone release of Camel 2.0. * Final release of Camel 2.0 planned for next quarter. * Development on the camel 1.x is slowing down while the focus shifted to 2.0. * Camel 1.x will be still maintained for the foreseeable future. Releases: * Camel 2.0-M1 released.
Community: * TLP infrastructure transition is complete (INFRA-1830). * Community is very active on both camel-1.x branch and the trunk. * The development and user lists continue to be very active. * No new committers. Development: * Lots of contributions from committers and community on both camel-1.x branch and trunk. Releases: * Camel 1.6.0 released.
Community: * The Camel community is very excited about becoming a TLP. * We started the process of moving the infrastructure (INFRA-1830). * Community is vibrant and contributing new features, components and tutorials to Camel. * The development and user lists continue to be very active. * No new committers. * A privacy policy has been added to the website and wiki. Development: * Lots of development effort continues. Releases: * No new releases in the past month. * We plan a new Camel 1.6 release once we migrate the infrastructure.
WHEREAS, the Board of Directors deems it to be in the best interests of the Foundation and consistent with the Foundation's purpose to establish a Project Management Committee charged with the creation and maintenance of an open-source integration framework based on known Enterprise Integration Patterns for distribution at no charge to the public. NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC), to be known as the "Apache Camel PMC", be and hereby is established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that the Apache Camel Project be and hereby is responsible for the creation and maintenance of an open-source integration framework based on known Enterprise Integration Patterns; and be it further RESOLVED, that the office of "Vice President, Apache Camel" be and hereby is created, the person holding such office to serve at the direction of the Board of Directors as the chair of the Apache Camel Project, and to have primary responsibility for management of the projects within the scope of responsibility of the Apache Camel Project; and be it further RESOLVED, that the persons listed immediately below be and hereby are appointed to serve as the initial members of the Apache Camel Project: * Jonathan Anstey <janstey@apache.org> * Hiram Chirino <chirino@apache.org> * Rob Davies <rdavies@apache.org> * Claus Ibsen <davsclaus@apache.org> * David Jencks <djencks@apache.org> * Willem Jiang <ningjiang@apache.org> * Roman Kalukiewicz <romkal@apache.org> * Jacek Laskowski <jlaskowski@apache.org> * Aaron Mulder <ammulder@apache.org> * Guillaume Nodet <gnodet@apache.org> * Nicky Sandhu <nsandhu@apache.org> * Bruce Snyder <bsnyder@apache.org> * James Strachan <jstrachan@apache.org> * William Tam <wtam@apache.org> * Gary Tully <gtully@apache.org> * Gert Vanthienen <gertv@apache.org> * Hadrian Zbarcea <hadrian@apache.org> NOW, THEREFORE, BE IT FURTHER RESOLVED, that Hadrian Zbarcea be appointed to the office of Vice President, Apache Camel, to serve in accordance with and subject to the direction of the Board of Directors and the Bylaws of the Foundation until death, resignation, retirement, removal or disqualification, or until a successor is appointed; and be it further RESOLVED, that the initial Apache Camel PMC be and hereby is tasked with the creation of a set of bylaws intended to encourage open development and increased participation in the Apache Camel Project; and be it further RESOLVED, that the Apache ActiveMQ Project be and hereby is tasked with the migration and rationalization of the Apache ActiveMQ CAMEL sub-project; and be it further RESOLVED, that all responsibilities pertaining to the Apache ActiveMQ Camel sub-project encumbered upon the Apache ActiveMQ Project are hereafter discharged. Special Order 7B, Establish the Apache Camel Project, was approved by Unanimous Vote of the directors present.