Update runtime to Camel 3.10 and Camel Quarkus 2.x
Closed this issue · 17 comments
We need camel Quarkus released first
Indeed! Let me add list of items so we can keep track of that
@oscerd I wonder if we should create a branch to keep the runtime aligned w/ Camel Quarkus devel. Similarly to what we used to have with camel-master on CKC, but without any automation (as it seems to me the changes are quite extensive).
I have some initial changes to do that - not sure to what extent it is functional - but could be a starting point.
Wdyt?
Also mentioning @nicolaferraro @squakez @lburgazzoli @astefanutti and everyone else for insights.
I think it makes sense to notice problem earlier
once upon a time there were a ci-build-camel-master workflow that was supposed to do something similar
@oscerd @lburgazzoli Thanks guys. So, I guess we can create branch "camel-main" and kick that work in there. Alright? I volunteer to kick off that work.
@oscerd do you know if we can create branches or do we have to request infra?
You can simply push a new branch. No need for infra
There is a camel-master branch we could either remove or rename
@oscerd fantastic.
@oscerd @lburgazzoli what do you guys prefer? Move or new? It doesn't matter to me.
Hm, nevermind, I think it doesn't matter. I'll take a look and try to move it. Otherwise I'll create a new one.
I think it makes sense to remove it and create a new one maybe
We must verify also this issue is no longer standing #625. You may edit the issue description and add also this one not to forget about it (you can assign it to me as well).