Thanks JB, I'm updating it. Il giorno gio 30 mag 2024 alle ore 11:52 Jean-Baptiste Onofré < j...@nanthrax.net> ha scritto:
> Hi Andrea, > > Maybe we can mention that camel-karaf main branch has been updated and > now works with Camel 4.6.0 and Karaf 4.4.6+. > We are working on new good features, heading to the first camel-karaf > 4.x release. > > It looks good to me anyway :) > > Regards > JB > > On Thu, May 30, 2024 at 9:56 AM Andrea Cosentino <anco...@gmail.com> > wrote: > > > > Hello all, > > > > I prepare the draft for June 2024, I'm planning to submit tomorrow > > afternoon to avoid any delay. Feedback is welcome. > > > > ## 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 93 committers and 47 PMC members in this project. > > The Committer-to-PMC ratio is roughly 2:1. > > > > Community changes, past quarter: > > - Colm O hEigeartaigh was added to the PMC on 2024-03-11 > > - Marat Gubaidullin was added to the PMC on 2024-03-11 > > - Gaelle Fournier was added as committer on 2024-03-06 > > - Ivan Kulaga was added as committer on 2024-03-12 > > > > ## Project Activity: > > Apache Camel: > > - We released Camel 3.22.2 > > - We released Camel 4.0.5 > > - We released Camel 4.4.1 > > - We released Camel 4.4.2 > > - We released Camel 4.5.0 > > - We released Camel 4.6.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. > > - The 4.4.x release is our LTS release train and we are already release > two > > patch releases 4.4.1 and 4.4.2 > > - We are working torward our next LTS release 4.8.0, we released two > > development releases 4.5.0 and 4.6.0 > > - We continued the release train for 3.22.x LTS > > - The 3.22.x release train is the LTS for 3.x > > - The situation is really healthy and the community is super. We are > > introducing many new features and working on engaging the community > more. > > > > Apache Camel K: > > - For Camel K we released a 2.3.0, 2.3.1 and 2.3.2 (on vote) with a lot > of > > good stuff. > > - For Camel-K-runtime we released 3.8.0, for 2.3.x work. > > - Camel K is in good shape and the community is expading with new > > contributors > > and many new good idea. > > > > Apache Camel Kamelets: > > - We released Camel Kamelets 4.4.1 > > - We released Camel Kamelets 4.4.2 > > - We released Camel Kamelets 4.5.0 > > - We released Camel Kamelets 4.6.0 > > - The 4.4.x release train is matching the LTS release from Camel core and > > it's > > an important building block for starting with routes > > - We introduced a lot of new Kamelets and we are improving the > documentation > > by focusing on much more examples > > > > Apache Camel Quarkus: > > - The Camel-Quarkus work is going ahead following the main camel releases > > with > > multiple releases > > - We released Camel-quarkus 3.8.1 > > - We released Camel-quarkus 3.8.2 > > - We released Camel-quarkus 3.9.0 > > - We released Camel-quarkus 3.10.0 > > - We released Camel-quarkus 3.11.0 > > - The 3.8.x release train is matching the 4.4.x release from Camel core > and > > it > > will be an LTS > > - A lot of work has been done on testing side and we are working on > > supporting > > more extensions for vector databases and AI > > > > Apache Camel-Karavan: > > - Camel-Karavan is improving and the community around the project is > > increasing in number of features and new issues reporting > > - We released the 4.4.0 > > - We released the 4.4.1 > > - We released the 4.5.0 > > - We released the 4.6.0 > > - We released also the 4.4.x patch releases matching the LTS version from > > Camel core > > > > Camel-Kafka-Connector: > > - We plan to release a 4.4.2 to match the LTS release from camel core, > the > > release process is on-going > > - The community is active and we receive a lot of feedback and requests > > > > Overall: > > - The Camel project and all the subprojects are in a really good shape > and > > all > > of them are growing in terms of community involvement and > contributions. > > > > ## Community Health: > > - 339 issues opened on GitHub, past quarter (11% increase) and 339 issues > > closed on GitHub, past quarter (12% increase): Some of the subproject > are > > using github issues, but Camel core is still on JIRA. We are seeing > > increase > > in Camel K and Camel Quarkus. > > - 4248 commits in the past quarter (17% decrease) and 115 code > contributors > > in > > the past quarter (10% increase): We are consolidating the codebase and > > that > > explains the decrease in commits and we are seeing increase in terms of > > contributors > > - 1706 PRs opened on GitHub, past quarter (5% decrease) and 1699 PRs > closed > > on > > GitHub, past quarter (6% decrease): Here we are more or less in line > with > > the last quarter. The situation is really good and we are observing > more > > engagement in open PRs. > > - dev@camel.apache.org had a 10% increase in traffic in the past quarter > > (363 > > emails compared to 328): The discussion are moving much more on Zulip > but > > still there was an increase. > > - iss...@camel.apache.org had a 10% increase in traffic in the past > quarter > > (2122 emails compared to 1915): We are opening more new issues related > to > > possible improvements and developments > > - us...@camel.apache.org had a 17% increase in traffic in the past > quarter > > (218 emails compared to 185): Users are starting to move and ask > questions > > on Zulip, like the discussion for development, but we have some more > > discussions related to Karaf and to release scheduling. > > - Jira Activity: 133 issues opened in JIRA, past quarter (-60% change) > and > > 164 > > issues closed in JIRA, past quarter (-46% change). Those numbers seems > > innacurate, but only Camel and Camel-Spring-Boot are still using JIRA > > instead of gh issues, so it is somewhat justified. >
