-
Notifications
You must be signed in to change notification settings - Fork 345
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Release 1.11.0 #3837
Comments
Good for me. I don't have any pending issue that requires particular attention ATM. |
It seems that the latest Camel K runtime snapshot is not liked by Camel K. The nightly release failed (I guess because of that): https://github.com/apache/camel-k/actions/runs/3536364281/jobs/5935327675#step:50:1499 |
Claudio is working on the build failures at #3838. Once it's merged it should be fixed. |
Please add here what is still pending. I'm going to cut the release for the runtime. |
I've collected the issues/PR required in https://github.com/apache/camel-k/milestone/36 |
I think most of the PR needs to be rebased now. |
Exactly, I am on it. |
Camel-K-runtime 1.16.0 staged: https://repository.apache.org/content/repositories/orgapachecamel-1499/ |
The pending PRs were rebased. I think we have just one test failing that may require some attention though: ❌ TestGlobalOperator (22.78s) Let's see the execution check on the last commits I've done after merging #3858 |
Some tests are failing, see #3861. Altough it looks like they are flaky, we may dedicate some effort to strengthen them and understand why randomly fails. |
Camel Kamelets 0.10.0 staged: https://repository.apache.org/content/repositories/orgapachecamel-1500/ |
What is still missing to release? |
Nothing from my side. I am working on some minor fix but nothing urgent to release. |
@claudio4j is there something missing for this one: #3871 I would like to have it included. There is already a Backport for 1.10.x (#3870) do we need this somewhere else to have it in 1.11.0? |
Nothing missing, the reviewers approved it.
I will cherry-pick the changes into 1.10 branch and will let you know shortly. |
#3870 is merged. |
Do we need to merge something else? I'm going to start the release process this morning. |
Let's wait some minute for #3881 checks to finish. As soon as it is merged I'll notify here. |
Merged, the check failing was a known transient issue. |
The make fails now with
|
Release 1.11.0 on vote. |
Release completed |
We have aligned camel-k-runtime here: apache/camel-k-runtime#927
Camel-kamelets is almost completed, there is only one issue related to milestone 0.10.0 (the other is for the release itself): https://github.com/apache/camel-kamelets/milestone/5
Let's see how it goes with the camel-k-runtime just updated, but I think we could release a 1.11.0 next week. It won't be an LTS, but at least we could have a feedback about some stuff we moved between runtime and camel quarkus.
@squakez @lburgazzoli
The text was updated successfully, but these errors were encountered: