Release 1.10.1

[oscerd]

We already have Camel Quarkus 2.12.0 released, we should a quick release for 1.10.1 and camel-k-runtime 1.15.0, so we could leverage 3.18.1 release, there is also 3.18.2 on vote, but we don't have the related camel quarkus released for it, so I'd like to have a camel-k release for each LTS 3.18.x release. Thoughts?

[oscerd]

We have some troubles with vertx and knative at the moment: apache/camel-k-runtime#886

[christophd]

would be good to include #3657 in 1.10.1

[oscerd]

I think we should start a new release. The baseline is:

• Camel-k-runtime 1.15.0
• Camel-Kamelets 0.9.1

on the runtime we are already aligned.

Please list here what is missing on release-1.10.x branch so we can track:

• OLM installtion needs to set KAMEL_OPERATOR_ID EnvVar #3657 is merged
• I'd like to add support for vault on GCP and Azure
• What else?

@tadayosi @astefanutti @phantomjinx @squakez

[christophd]

#3671 should be included. I'll open a backport PR

Edit: Backport PR #3692

[oscerd]

I'll go ahead with the runtime for the moment and maybe with camel-kamelets so we should be ready.

[oscerd]

Camel-K-runtime 1.15.0 Staged: https://repository.apache.org/content/repositories/orgapachecamel-1472/

[oscerd]

Camel-Kamelets 0.9.1 staged: https://repository.apache.org/content/repositories/orgapachecamel-1478/

[squakez]

If we're not in a hurry, I'd like to fix and backport #3674

[oscerd]

No rush. The runtime and kamelets was more or less prepared, for camel-k we can have a release next week.

[oscerd]

Do we need something else to merge in 1.10.x or only #3674 ?

[squakez]

#3692 is also standing

[oscerd]

I think we are in good shape, when everything is in place I'll start the release process.

[oscerd]

What is still missing for starting release process?

[squakez]

I've merged #3692. We may want to rebase #3718 to make sure that the fix is correct. Then, I think we're ready to go.

[oscerd]

ok, perfect.

[oscerd]

Thanks.

[astefanutti]

Just created #3721 if it can make it.

[squakez]

Just created #3721 if it can make it.

Yeah, it would be a good one to fix on 1.10.1 as well. Let's wait for it to complete the checks and be merged.

[oscerd]

I think this one too should go in 1.10.x #3723

I'll start the release on Monday. Just give me green light.

[squakez]

@oscerd I am going to backport that one as well.

I've merged all the other standings PRs. We should be good to go. We eventually need to have a deeper look at the native tests as they are not stable.

[squakez]

Backport at #3724

[squakez]

All changes are merged now. We will have to review the suite of native test: follow up issue in #3726

🟢 for me

[oscerd]

I'm starting the release process.

[oscerd]

on vote.