You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@camel.apache.org by Andrea Cosentino <an...@gmail.com> on 2023/09/05 05:00:49 UTC
Draft Camel Board Report for September 2023
Hello all,
I prepare the draft for September 2023, I'm planning to submit it tomorrow.
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:
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.
- For Camel-Kamelets releases
- We released Camel Kameletes 3.20.6
- We released Camel Kameletes 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.
Re: Draft Camel Board Report for September 2023
Posted by Andrea Cosentino <an...@gmail.com>.
I submitted it, with the suggested stuff this morning.
Thanks for the feedback
Il giorno mer 6 set 2023 alle ore 15:57 Otavio Rodolfo Piske <
angusyoung@gmail.com> ha scritto:
> Looks good to me as well.
>
> Thanks Andrea!
>
> On Tue, Sep 5, 2023 at 11:41 AM Nicolas Filotto <nf...@talend.com>
> wrote:
>
> > It looks good to me too, thanks Andrea
> > ________________________________
> > From: Jean-Baptiste Onofré <jb...@nanthrax.net>
> > Sent: Tuesday, September 5, 2023 11:24
> > To: dev@camel.apache.org <de...@camel.apache.org>
> > Subject: Re: Draft Camel Board Report for September 2023
> >
> > It looks good to me.
> >
> > Thanks !
> > Regards
> > JB
> >
> > On Tue, Sep 5, 2023 at 7:00 AM Andrea Cosentino <an...@gmail.com>
> wrote:
> > >
> > > Hello all,
> > >
> > > I prepare the draft for September 2023, I'm planning to submit it
> > tomorrow.
> > > 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:
> > > 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.
> > > - For Camel-Kamelets releases
> > > - We released Camel Kameletes 3.20.6
> > > - We released Camel Kameletes 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.
> >
> > As a recipient of an email from the Talend Group, your personal data will
> > be processed by our systems. Please see our Privacy Notice <
> > https://www.talend.com/privacy-policy/> for more information about our
> > collection and use of your personal information, our security practices,
> > and your data protection rights, including any rights you may have to
> > object to automated-decision making or profiling we use to analyze
> support
> > or marketing related communications. To manage or discontinue promotional
> > communications, use the communication preferences portal<
> > https://pages.qlik.com/Unsubscribe_Page.html>. To exercise your data
> > protection rights, use the privacy request form<
> >
> https://talend.my.onetrust.com/webform/ef906c5a-de41-4ea0-ba73-96c079cdd15a/b191c71d-f3cb-4a42-9815-0c3ca021704cl
> >.
> > Contact us here <https://www.talend.com/contact/> or by mail to either
> of
> > our co-headquarters: Talend, Inc.: 400 South El Camino Real, Ste 1400,
> San
> > Mateo, CA 94402; Talend SAS: 5/7 rue Salomon De Rothschild, 92150
> Suresnes,
> > France
> >
>
>
> --
> Otavio R. Piske
> http://orpiske.net
>
Re: Draft Camel Board Report for September 2023
Posted by Otavio Rodolfo Piske <an...@gmail.com>.
Looks good to me as well.
Thanks Andrea!
On Tue, Sep 5, 2023 at 11:41 AM Nicolas Filotto <nf...@talend.com> wrote:
> It looks good to me too, thanks Andrea
> ________________________________
> From: Jean-Baptiste Onofré <jb...@nanthrax.net>
> Sent: Tuesday, September 5, 2023 11:24
> To: dev@camel.apache.org <de...@camel.apache.org>
> Subject: Re: Draft Camel Board Report for September 2023
>
> It looks good to me.
>
> Thanks !
> Regards
> JB
>
> On Tue, Sep 5, 2023 at 7:00 AM Andrea Cosentino <an...@gmail.com> wrote:
> >
> > Hello all,
> >
> > I prepare the draft for September 2023, I'm planning to submit it
> tomorrow.
> > 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:
> > 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.
> > - For Camel-Kamelets releases
> > - We released Camel Kameletes 3.20.6
> > - We released Camel Kameletes 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.
>
> As a recipient of an email from the Talend Group, your personal data will
> be processed by our systems. Please see our Privacy Notice <
> https://www.talend.com/privacy-policy/> for more information about our
> collection and use of your personal information, our security practices,
> and your data protection rights, including any rights you may have to
> object to automated-decision making or profiling we use to analyze support
> or marketing related communications. To manage or discontinue promotional
> communications, use the communication preferences portal<
> https://pages.qlik.com/Unsubscribe_Page.html>. To exercise your data
> protection rights, use the privacy request form<
> https://talend.my.onetrust.com/webform/ef906c5a-de41-4ea0-ba73-96c079cdd15a/b191c71d-f3cb-4a42-9815-0c3ca021704cl>.
> Contact us here <https://www.talend.com/contact/> or by mail to either of
> our co-headquarters: Talend, Inc.: 400 South El Camino Real, Ste 1400, San
> Mateo, CA 94402; Talend SAS: 5/7 rue Salomon De Rothschild, 92150 Suresnes,
> France
>
--
Otavio R. Piske
http://orpiske.net
Re: Draft Camel Board Report for September 2023
Posted by Nicolas Filotto <nf...@talend.com>.
It looks good to me too, thanks Andrea
________________________________
From: Jean-Baptiste Onofré <jb...@nanthrax.net>
Sent: Tuesday, September 5, 2023 11:24
To: dev@camel.apache.org <de...@camel.apache.org>
Subject: Re: Draft Camel Board Report for September 2023
It looks good to me.
Thanks !
Regards
JB
On Tue, Sep 5, 2023 at 7:00 AM Andrea Cosentino <an...@gmail.com> wrote:
>
> Hello all,
>
> I prepare the draft for September 2023, I'm planning to submit it tomorrow.
> 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:
> 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.
> - For Camel-Kamelets releases
> - We released Camel Kameletes 3.20.6
> - We released Camel Kameletes 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.
As a recipient of an email from the Talend Group, your personal data will be processed by our systems. Please see our Privacy Notice <https://www.talend.com/privacy-policy/> for more information about our collection and use of your personal information, our security practices, and your data protection rights, including any rights you may have to object to automated-decision making or profiling we use to analyze support or marketing related communications. To manage or discontinue promotional communications, use the communication preferences portal<https://pages.qlik.com/Unsubscribe_Page.html>. To exercise your data protection rights, use the privacy request form<https://talend.my.onetrust.com/webform/ef906c5a-de41-4ea0-ba73-96c079cdd15a/b191c71d-f3cb-4a42-9815-0c3ca021704cl>. Contact us here <https://www.talend.com/contact/> or by mail to either of our co-headquarters: Talend, Inc.: 400 South El Camino Real, Ste 1400, San Mateo, CA 94402; Talend SAS: 5/7 rue Salomon De Rothschild, 92150 Suresnes, France
Re: Draft Camel Board Report for September 2023
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
It looks good to me.
Thanks !
Regards
JB
On Tue, Sep 5, 2023 at 7:00 AM Andrea Cosentino <an...@gmail.com> wrote:
>
> Hello all,
>
> I prepare the draft for September 2023, I'm planning to submit it tomorrow.
> 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:
> 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.
> - For Camel-Kamelets releases
> - We released Camel Kameletes 3.20.6
> - We released Camel Kameletes 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.
Re: Draft Camel Board Report for September 2023
Posted by Andrea Cosentino <an...@gmail.com>.
I will add that too.
Thanks for the reminder.
Il giorno mar 5 set 2023 alle ore 09:53 Pasquale Congiusti <
pasquale.congiusti@gmail.com> ha scritto:
> Thanks Andrea.
> Not sure if you want to mention Camel K Runtime dependency as well, as we
> are now matching the release cycle with Camel Quarkus. Also we may mention
> Camel K 2.0 has no coupled dependency from the runtime and its release
> cycle will be decoupled from the core/runtime release cycle.
>
> Pasquale.
>
> On Tue, Sep 5, 2023 at 7:01 AM Andrea Cosentino <an...@gmail.com> wrote:
>
> > Hello all,
> >
> > I prepare the draft for September 2023, I'm planning to submit it
> tomorrow.
> > 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:
> > 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.
> > - For Camel-Kamelets releases
> > - We released Camel Kameletes 3.20.6
> > - We released Camel Kameletes 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.
> >
>
Re: Draft Camel Board Report for September 2023
Posted by Pasquale Congiusti <pa...@gmail.com>.
Thanks Andrea.
Not sure if you want to mention Camel K Runtime dependency as well, as we
are now matching the release cycle with Camel Quarkus. Also we may mention
Camel K 2.0 has no coupled dependency from the runtime and its release
cycle will be decoupled from the core/runtime release cycle.
Pasquale.
On Tue, Sep 5, 2023 at 7:01 AM Andrea Cosentino <an...@gmail.com> wrote:
> Hello all,
>
> I prepare the draft for September 2023, I'm planning to submit it tomorrow.
> 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:
> 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.
> - For Camel-Kamelets releases
> - We released Camel Kameletes 3.20.6
> - We released Camel Kameletes 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.
>
Re: Draft Camel Board Report for September 2023
Posted by Andrea Cosentino <an...@gmail.com>.
Hello Karen,
Thanks for noticing.
Fixed in the draft to submit.
Thanks.
Il giorno mar 5 set 2023 alle ore 09:18 Karen Lease <ka...@gmail.com>
ha scritto:
> Thanks Andrea,
>
> I only noticed an extra "e" for these releases:
> - We released Camel Kameletes 3.20.6
> - We released Camel Kameletes 3.21.0
>
> Ciao,
> Karen
>
> Le 05/09/2023 à 07:00, Andrea Cosentino a écrit :
> > Hello all,
> >
> > I prepare the draft for September 2023, I'm planning to submit it
> tomorrow.
> > 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:
> > 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.
> > - For Camel-Kamelets releases
> > - We released Camel Kameletes 3.20.6
> > - We released Camel Kameletes 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.
> >
>
Re: Draft Camel Board Report for September 2023
Posted by Karen Lease <ka...@gmail.com>.
Thanks Andrea,
I only noticed an extra "e" for these releases:
- We released Camel Kameletes 3.20.6
- We released Camel Kameletes 3.21.0
Ciao,
Karen
Le 05/09/2023 à 07:00, Andrea Cosentino a écrit :
> Hello all,
>
> I prepare the draft for September 2023, I'm planning to submit it tomorrow.
> 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:
> 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.
> - For Camel-Kamelets releases
> - We released Camel Kameletes 3.20.6
> - We released Camel Kameletes 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.
>