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 2022/09/12 04:51:00 UTC
Draft Camel Board Report for September 2022
Hello all,
I prepared the draft for September 2022, I'm planning to submit it tomorrow
in the afternoon. Feedback are welcome.
## 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 integration 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.
Re: Draft Camel Board Report for September 2022
Posted by Andrea Cosentino <an...@gmail.com>.
Thanks for the heads up, I'll update the draft about this.
Il giorno lun 12 set 2022 alle ore 14:30 Zoran Regvart <zo...@regvart.com>
ha scritto:
> Hi Andrea,
> There is no Integration track at ApacheCon NA, there are four talks
> mentioning Camel on Cloud, Groovy and Libraries, frameworks and tools
> tracks.
>
> --
> Sent from mobile
>
> > On 12. Sep 2022, at 06:51, Andrea Cosentino <an...@gmail.com> wrote:
> >
> > Hello all,
> >
> > I prepared the draft for September 2022, I'm planning to submit it
> tomorrow
> > in the afternoon. Feedback are welcome.
> >
> > ## 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 integration 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.
>
Re: Draft Camel Board Report for September 2022
Posted by Zoran Regvart <zo...@regvart.com>.
Hi Andrea,
There is no Integration track at ApacheCon NA, there are four talks mentioning Camel on Cloud, Groovy and Libraries, frameworks and tools tracks.
--
Sent from mobile
> On 12. Sep 2022, at 06:51, Andrea Cosentino <an...@gmail.com> wrote:
>
> Hello all,
>
> I prepared the draft for September 2022, I'm planning to submit it tomorrow
> in the afternoon. Feedback are welcome.
>
> ## 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 integration 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.