Hello,
This looks cool. Please let me know if you would like some help setting up
the github actions. We have some of them that you can use as a starting
point and maybe you can tweak them for that.
If you believe these branches are going to be active for a while, there's
another thing you might
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 refactoring
Hi Andrea,
I think those are good ideas and I believe it would be beneficial for the
project to make the Kamelets a more prominent concept within our projects.
I believe we can reach a larger audience by doing so. In particular, I like
the idea of the Kamelets marketplace.
All in all, it's +1 fro
I've begun working on the Jakarta 10 migration.
I tried with a 4.x branch [1], but it's difficult to maintain with the
number of commits in the main branch. So I decided to switch to a
different mechanism.
I've created several branches upstream :
* jakarta-rewrite [2] : contains a migration shell
Already started on it.
On Fri, Nov 25, 2022 at 10:18 AM Claus Ibsen wrote:
>
> Hi
>
> Okay so I have checked the 3.18.x branches and they all pass CS and RAT
> checks.
> Also I backported some camel-karaf OSGi fixes and checked that the
> features.xml validate and works.
>
> Gregor, we are ready
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 then
I think the first point to address is about the Kamelet API [1]. Right now
this is living (and evolving) as part of Camel K. If we decide to spin off
something different, then we need a new project (or reuse the catalog) to
take care of the API maintenance (also the CRD part). As an alternative, we
On Fri, Nov 25, 2022 at 3:05 PM Nicolas Filotto wrote:
> Hi Claus,
>
> That sounds like a good plan, here are the first questions that I have in
> mind:
>
> * Why do we need to keep on releasing new LTS versions of Camel 3?
> * Why not simply consider 3.20 as the last LTS version of Camel
Hi Claus,
That sounds like a good plan, here are the first questions that I have in mind:
* Why do we need to keep on releasing new LTS versions of Camel 3?
* Why not simply consider 3.20 as the last LTS version of Camel 3 and only
maintain it?
* What kind of features/improvements do
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
> Ca
Hi
Thanks for starting this important topic.
I will come back with more thoughts later.
But one thing that stood out to me is that the kamelets documentation today
is tied into knative [1] and kamelet bindings.
it looks a bit like the documentation is auto generated for that part.
There's a lot o
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 Cam
Hi
Okay so I have checked the 3.18.x branches and they all pass CS and RAT
checks.
Also I backported some camel-karaf OSGi fixes and checked that the
features.xml validate and works.
Gregor, we are ready for the release.
On Thu, Nov 24, 2022 at 8:14 PM Claus Ibsen wrote:
> Hi
>
> We have upgr
Hello,
Kamelets are becoming an important and universal higher-level components /
building-blocks of Apache Camel; that are universal usable in all of Camels
runtimes and projects, whether its Camel on Spring Boot, Camel Standalone,
Camel Kafka Connector, Camel Quarkus, Camel JBang and Camel K as
14 matches
Mail list logo