Hi
Any last minute feedback on the blog post before we post it?
https://github.com/apache/camel-website/pull/943
On Fri, Nov 25, 2022 at 11:42 AM Claus Ibsen wrote:
> Hi
>
> This is a proposal for a plan for Apache Camel 4 and how this can affect
> Camel 3.
>
> Summary
>
> ===
>
> The
at 2:09 PM Siano, Stephan
> > > > wrote:
> > > >
> > > >> Hi,
> > > >>
> > > >> Actually removing the OSGi manifests from the bundles coming from
> the
> > > >> general camel build would mean that we have to
Hi
I created a draft post for a blog announcement for Camel v4 to make this
more widespread known.
The PR is in draft, so feedback, comments, and changes is welcome in the PR
https://github.com/apache/camel-website/pull/943
--
Claus Ibsen
-
@davsclaus
Camel in Action 2:
On Fri, Dec 9, 2022 at 2:06 PM Otavio Rodolfo Piske
wrote:
> Hi,
>
> I'm wondering if it wouldn't be better to position the 3.20 LTS release
> along with JDK 17 as a better stopgap for them ... What do you think?
>
> The JDK 17 is such a great release with so many interesting features. I am
>
Hi,
I'm wondering if it wouldn't be better to position the 3.20 LTS release
along with JDK 17 as a better stopgap for them ... What do you think?
The JDK 17 is such a great release with so many interesting features. I am
afraid that by still focusing on JDK 11 with Camel 4 we may limit ourselves
Hi
We have received some feedback by Camel users that ask whether Camel v4
could initially also support JDK 11, and then at a later stage drop JDK11.
This will help migrate as otherwise its a "big jump" to both upgrade JDKs,
Camel, javax -> jakarta and what else.
It would still mean JDK17 can be
Fully agree with "communities are the most important"
On 01/12/2022 09:14, Jean-Baptiste Onofré wrote:
communities are the most
important
--
--
François
2022 14:01
To: dev@camel.apache.org
Subject: Re: Camel 4 roadmap and affect on Camel 3
Ok so we will have a camel-core.jar and camel-core-with-manifest-osgi.jar
just with the manifest file add-in for each camel core jar.
On 30/11/2022 13:53, Andrea Cosentino wrote:
This would become something
every jar coming out of the general build, which
> > >> looks
> > >> like a lot of maintenance effort to me.
> > >>
> > >> Best regards
> > >> Stephan
> > >>
> > >> -Original Message-
> > >>
from the bundles coming from the
> >> general camel build would mean that we have to create an OSGi wrapper
> >> bundle for each and every jar coming out of the general build, which looks
> >> like a lot of maintenance effort to me.
> >>
> >> Best regards
&
jar coming out of the general build, which looks
like a lot of maintenance effort to me.
Best regards
Stephan
-Original Message-
From: fpapon
Sent: Wednesday, 30 November 2022 14:01
To: dev@camel.apache.org
Subject: Re: Camel 4 roadmap and affect on Camel 3
Ok so we will have a camel
the Camel users that only 3.19 is an LTS
version as
all
final versions would then be LTS versions.
What do you think of it?
Regards,
Nicolas
From: Claus Ibsen
Sent: Friday, November 25, 2022 11:42
To: dev
Subject: Camel 4 roadmap and affect on C
ds
> > Stephan
> >
> > -Original Message-----
> > From: fpapon
> > Sent: Wednesday, 30 November 2022 14:01
> > To: dev@camel.apache.org
> > Subject: Re: Camel 4 roadmap and affect on Camel 3
> >
> > Ok so we will have a camel-
* If camel-karaf is released independently, when will it be
> >>>> released?
> >>>>>> My fear is that it will be desynchronized with Camel very quickly.
> >>>>>> *
> >>>>>>
> >>>>>> With 2 LTS
is an LTS version as all
final versions would then be LTS versions.
What do you think of it?
Regards,
Nicolas
From: Claus Ibsen
Sent: Friday, November 25, 2022 11:42
To: dev
Subject: Camel 4 roadmap and affect on Camel 3
Hi
This is a proposal for a plan
every jar coming out of the general build, which looks
> like a lot of maintenance effort to me.
> >
> > Best regards
> > Stephan
> >
> > -Original Message-
> > From: fpapon
> > Sent: Wednesday, 30 November 2022 14:01
> > To: dev@camel
, which looks like a lot of
> maintenance effort to me.
>
> Best regards
> Stephan
>
> -Original Message-
> From: fpapon
> Sent: Wednesday, 30 November 2022 14:01
> To: dev@camel.apache.org
> Subject: Re: Camel 4 roadmap and affect on Camel 3
>
> Ok s
of
maintenance effort to me.
Best regards
Stephan
-Original Message-
From: fpapon
Sent: Wednesday, 30 November 2022 14:01
To: dev@camel.apache.org
Subject: Re: Camel 4 roadmap and affect on Camel 3
Ok so we will have a camel-core.jar and camel-core-with-manifest-osgi.jar just
with the manifest file
-Original Message-
From: fpapon
Sent: Wednesday, 30 November 2022 14:01
To: dev@camel.apache.org
Subject: Re: Camel 4 roadmap and affect on Camel 3
Ok so we will have a camel-core.jar and camel-core-with-manifest-osgi.jar just
with the manifest file add-in for each camel core jar.
On 30/11/2022 13
that only 3.19 is an LTS version as
all
final versions would then be LTS versions.
What do you think of it?
Regards,
Nicolas
From: Claus Ibsen
Sent: Friday, November 25, 2022 11:42
To: dev
Subject: Camel 4 roadmap and affect on Camel 3
Hi
This is a proposal
e decided to have this policy
> >> (2
> >>>> LTS versions per year supported for one year)?
> >>>>
> >>>> I would personally prefer to have:
> >>>>
> >>>>* only one LTS version per year (or 2 if we keep on releasing
on as
all
final versions would then be LTS versions.
What do you think of it?
Regards,
Nicolas
From: Claus Ibsen
Sent: Friday, November 25, 2022 11:42
To: dev
Subject: Camel 4 roadmap and affect on Camel 3
Hi
This is a proposal for a plan for Apache Camel
ity on which versions are LTS.
> Indeed,
> > > for example, the next LTS version will be 3.20 while we could expect
> 3.22
> > > to be the next one after 3.14 and 3.18. With this logic, instead of
> > > releasing 3.19 and 3.20, we could have released 3.19
Hello Claus,
+1 for this plan.
As an active member of the camel-quarkus project, I'm excited to start
working towards Quarkus 3.
I think it's a good plan to maintain LTS releases of Camel 3 at least for
2023 and maybe a part of 2024, to give time for users to move from Java 11
and Spring 5.
ersions of
> > >> Camel 3?
> > >>>>>>* Why not simply consider 3.20 as the last LTS version of
> > >> Camel 3
> > >>>> and
> > >>>>>> only maintain it?
> > >>>>>>* What kind of featur
af is released independently, when will it be
> >>>> released?
> >>>>>> My fear is that it will be desynchronized with Camel very quickly.
> >>>>>>*
> >>>>>>
> >>>>>> With 2 LTS of Camel 3 and 2 LTS of Camel 4 per year, it w
Ibsen
Sent: Friday, November 25, 2022 11:42
To: dev
Subject: Camel 4 roadmap and affect on Camel 3
Hi
This is a proposal for a plan for Apache Camel 4 and how this can
affect
Camel 3.
Summary
===
The overall scope is that the leap from Camel 3 to 4 is a lot less
than
going from
ted for one year)?
> > > > >
> > > > > I would personally prefer to have:
> > > > >
> > > > > * only one LTS version per year (or 2 if we keep on releasing
> LTS
> > > > > versions of Camel 3) but supported for at least 2 years inste
> > otherwise Camel users are less inclined to migrate to the latest LTS
> > > > version because 1 year of support doesn't really worth the migration
> > > > effort, especially for big projects where the migration takes several
> > > > months.
> > > > *
propose milestone versions or equivalent between 2 LTS
> versions
> > > for early adopters to add more clarity on which versions are LTS.
> Indeed,
> > > for example, the next LTS version will be 3.20 while we could expect
> 3.22
> > > to be the next one after 3.14 and 3.18
side.
Thank you again,
BR,
Regards,
Nicolas
From: Jean-Baptiste Onofr?
Sent: Monday, November 28, 2022 10:39
To: dev@camel.apache.org
Subject: Re: Camel 4 roadmap and affect on Camel 3
Hi guys,
I understand that Karaf/OSGi is not in the Camel community target
> > for example, the next LTS version will be 3.20 while we could expect 3.22
> > to be the next one after 3.14 and 3.18. With this logic, instead of
> > releasing 3.19 and 3.20, we could have released 3.19 M1 and 3.19, it would
> > then be obvious to the Camel users that on
el users that only 3.19 is an LTS version as all
> final versions would then be LTS versions.
>
> What do you think of it?
>
> Regards,
> Nicolas
> ________
> From: Claus Ibsen
> Sent: Friday, November 25, 2022 11:42
> To: dev
> Su
Hi Claus,
I like the plan and I think we have something doable for Camel 4. IMHO, I
think it's important for us to get ready for several upcoming releases of
projects that are important to our community (Spring Boot 6, Quarkus 3,
Jakarta 10).
In my wish list I also have a few internal
Hi
There is an early start on Camel v4 work in this PR
https://github.com/apache/camel/pull/8579
After the Camel 3.20 LTS release, then we should likely switch over the
"main" branch to become the work branch for v4.
And then have a camel-3.x branch for ongoing v3 work.
When that time comes
s also
how Java does it.
It has worked really well for Camel v3.
We only use Milestone releases for big new versions like v2, v3 and v4, ...
> What do you think of it?
>
>
Thanks for the feedback
> Regards,
> Nicolas
> ____
> From: Claus Ibsen
&
From: Claus Ibsen
Sent: Friday, November 25, 2022 11:42
To: dev
Subject: Camel 4 roadmap and affect on Camel 3
Hi
This is a proposal for a plan for Apache Camel 4 and how this can affect
Camel 3.
Summary
===
The overall scope is that the leap from Camel 3 to 4 is a lot less than
Hi
I think after a period of review and feedback on this subject, then we
should post an official blog post on the website about the roadmap and
timelines.
On Fri, Nov 25, 2022 at 11:42 AM Claus Ibsen wrote:
> Hi
>
> This is a proposal for a plan for Apache Camel 4 and how this can affect
>
Hi
This is a proposal for a plan for Apache Camel 4 and how this can affect
Camel 3.
Summary
===
The overall scope is that the leap from Camel 3 to 4 is a lot less than
going from Camel 2 to 3.
And that we have a timebox approach where we aim for a 6 month period of
work.
The need for
39 matches
Mail list logo
