Just added this line

- 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.

Il giorno gio 15 dic 2022 alle ore 14:03 Claus Ibsen <claus.ib...@gmail.com>
ha scritto:

> Hi
>
> You can maybe add something about the Came 4 roadmap that is currently
> being drafted and to be posted on the website later this month, or early
> next month.
>
>
>
> On Thu, Dec 15, 2022 at 9:33 AM Andrea Cosentino <anco...@gmail.com>
> wrote:
>
> > Hello all,
> >
> > I prepared the draft for December 2022, I'm planning to submit it today
> in
> > the afternoon, since they send the reminder really later this time, so we
> > need to submit before tomorrow Fri Dec 16th. 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 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 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.
> > - iss...@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)
> > - us...@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.
> >
>
>
> --
> Claus Ibsen
> -----------------
> @davsclaus
> Camel in Action 2: https://www.manning.com/ibsen2
>

Reply via email to