+1
Le lun. 5 août 2024 à 09:07, James Netherton a
écrit :
> Thanks Pasquale for the explanation!
>
> > I'd suggest parking the work done so far in a branch that could be taken
> over in the future if needed
>
> We could keep it in for CQ 3.14.0 and then remove for 3.15.0 which will
> (hopefully)
On Mon, Aug 5, 2024 at 9:07 AM James Netherton
wrote:
> Thanks Pasquale for the explanation!
>
> > I'd suggest parking the work done so far in a branch that could be taken
> over in the future if needed
>
> We could keep it in for CQ 3.14.0 and then remove for 3.15.0 which will
> (hopefully) be a
Thanks Pasquale for the explanation!
> I'd suggest parking the work done so far in a branch that could be taken
over in the future if needed
We could keep it in for CQ 3.14.0 and then remove for 3.15.0 which will
(hopefully) be an LTS release. I can also cut a branch and document it
somewhere too
Hi James,
I don't know if somebody is going to continue that work. However, let me
add some context that may help with making the decision.
At the beginning of the year I was working on some development with the
goal to eventually remove the runtime at all [1]. However the work was
stopped as we d
Hi everyone,
I wanted to open a discussion about the camel-k extension module and Maven
plugins that live in the Camel Quarkus project:
https://github.com/apache/camel-quarkus/tree/main/extensions/camel-k
https://github.com/apache/camel-quarkus/tree/main/tooling/camel-k-catalog-model
https://gith
