I'm fine with reworking PR 173, we could merge after 3.20.0 release.
Thanks for this.
Il giorno lun 28 nov 2022 alle ore 15:05 Jean-Baptiste Onofré <
j...@nanthrax.net> ha scritto:
> Hi,
>
> I agree with François. I'm still volunteering to help there, but we
> need at least some "help" from the
Hi,
I agree with François. I'm still volunteering to help there, but we
need at least some "help" from the other members of the Camel
community.
I think that reworking camel-karaf would give us more flexibility and
easier to maintain.
I can rework on PR #173 (rebasing and improving), including
Hi,
I think camel-karaf make sense to continue to exist and it could be nice
to be more simple to manage.
There is a PR thanks to JB (https://github.com/apache/camel-karaf/pull/173)
May be it could be nice if camel-karaf has it's own version and release
flow.
Mainly we have :
-
+1 (binding)
On Mon, Nov 28, 2022 at 11:14 AM Gregor Zurowski
wrote:
> Hi Everyone:
>
> This is a vote to release Apache Camel 3.18.4, a new patch release
> with 27 improvements and fixes.
>
> Release notes:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12352409=12311211
>
>
+1 (binding)
Thanks Gregor.
Il giorno lun 28 nov 2022 alle ore 11:14 Gregor Zurowski <
gre...@list.zurowski.org> ha scritto:
> Hi Everyone:
>
> This is a vote to release Apache Camel 3.18.4, a new patch release
> with 27 improvements and fixes.
>
> Release notes:
>
+1 (non-binding)
On Mon, Nov 28, 2022 at 6:20 PM Gregor Zurowski
wrote:
> Hi Everyone:
>
> This is a vote to release Apache Camel 3.18.4, a new patch release
> with 27 improvements and fixes.
>
> Release notes:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12352409=12311211
>
Hi,
+1 (non binding)
Regards,
Nicolas
From: Jean-Baptiste Onofr?
Sent: Monday, November 28, 2022 11:31
To: dev@camel.apache.org
Subject: Re: [VOTE] Release Apache Camel 3.18.4 (LTS)
+1 (binding)
Regards
JB
On Mon, Nov 28, 2022 at 11:13 AM Gregor Zurowski
+1 (binding)
Regards
JB
On Mon, Nov 28, 2022 at 11:13 AM Gregor Zurowski
wrote:
>
> Hi Everyone:
>
> This is a vote to release Apache Camel 3.18.4, a new patch release
> with 27 improvements and fixes.
>
> Release notes:
>
It's just my point of view. There are a lot of active contributors on Camel
and we need to gather more opinions as possible.
Let's see.
Il giorno lun 28 nov 2022 alle ore 11:18 Jean-Baptiste Onofré <
j...@nanthrax.net> ha scritto:
> Hi Andrea,
>
> Fair comment. Then, if your proposal is just to
Hi Andrea,
Fair comment. Then, if your proposal is just to retire camel-karaf, go
for it and start a vote. I agree with you and I will support this.
Maybe, we can just propose to maintain as best effort, but without
strong commitment in terms of releases, etc (like we do on
camel-extra).
Regards
Hi Everyone:
This is a vote to release Apache Camel 3.18.4, a new patch release
with 27 improvements and fixes.
Release notes:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12352409=12311211
== Apache Camel 3.18.4 ==
Staging repository:
Hello,
I could be wrong, but it seems to me that even on the Karaf project side
we're going to have exactly the same problem.
- It will be hard to maintain
- It will need to be aligned to the Camel core side
- If possible on Karaf community there are far less active contributors
than on the
Hi Jean-Baptiste,
Thank you very much for proposing to support camel-karaf directly in the Karaf
project, it is a wonderful idea, I was really worried about the future of the
components of camel-karaf, especially knowing that I plan to re-add some
components.
So it is definitely a +1 from my
Hi guys,
I understand that Karaf/OSGi is not in the Camel community target
anymore, and it makes sense.
I proposed a time ago to refactor the approach of Camel components for
Karaf, using special packaging (embedded the deps as private to avoid
to have bunch of SMX bundles deps), etc.
Even at
Hello,
So, creating this is no big trouble ... but, if we can merge it soon after
3.20, then I think it may be OK to wait. That way we can reuse the
automation we already have in place/
IMHO, I think the most important bit is to avoid a sudden huge spike in
failed tests. As we'll have a lot of
15 matches
Mail list logo
