camel-k
                                
                                 camel-k copied to clipboard
                                
                                    camel-k copied to clipboard
                            
                            
                            
                        Release 1.10.1
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?
We have some troubles with vertx and knative at the moment: https://github.com/apache/camel-k-runtime/pull/886
would be good to include #3657 in 1.10.1
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:
- #3657 is merged
- I'd like to add support for vault on GCP and Azure
- What else?
@tadayosi @astefanutti @phantomjinx @squakez
#3671 should be included. I'll open a backport PR
Edit: Backport PR https://github.com/apache/camel-k/pull/3692
I'll go ahead with the runtime for the moment and maybe with camel-kamelets so we should be ready.
Camel-K-runtime 1.15.0 Staged: https://repository.apache.org/content/repositories/orgapachecamel-1472/
Camel-Kamelets 0.9.1 staged: https://repository.apache.org/content/repositories/orgapachecamel-1478/
If we're not in a hurry, I'd like to fix and backport #3674
No rush. The runtime and kamelets was more or less prepared, for camel-k we can have a release next week.
Do we need something else to merge in 1.10.x or only #3674 ?
https://github.com/apache/camel-k/pull/3692 is also standing
I think we are in good shape, when everything is in place I'll start the release process.
What is still missing for starting release process?
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.
ok, perfect.
Thanks.
Just created #3721 if it can make it.
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.
I think this one too should go in 1.10.x https://github.com/apache/camel-k/pull/3723
I'll start the release on Monday. Just give me green light.
@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.
Backport at #3724
All changes are merged now. We will have to review the suite of native test: follow up issue in #3726
:green_circle: for me
I'm starting the release process.
on vote.