Skip to content
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 2.2.0 #4991

Closed
squakez opened this issue Dec 18, 2023 · 6 comments
Closed

Release 2.2.0 #4991

squakez opened this issue Dec 18, 2023 · 6 comments
Assignees
Milestone

Comments

@squakez
Copy link
Contributor

squakez commented Dec 18, 2023

No description provided.

@squakez squakez added kind/feature New feature or request and removed kind/feature New feature or request labels Dec 18, 2023
@squakez squakez added this to the 2.2.0 milestone Dec 18, 2023
@squakez squakez self-assigned this Dec 18, 2023
@squakez
Copy link
Contributor Author

squakez commented Dec 18, 2023

#4738

@squakez
Copy link
Contributor Author

squakez commented Dec 18, 2023

I've just discovered that the latest default runtime (3.6.0) we've planned to use is not working as expected in native mode, due to the fact it is based on a jdk-17 image. It seems Quarkus 3.6.0 requires a jdk-21 based image. The fix is relatively easy and needs to be done in any case, but that means we need to postpone at least one week the release waiting for 3.6.1 to be out. We may even release keeping 3.2.0 as default since we do not have a strong dependency requirement, but probably it makes sense to wait for the fix.

@oscerd wdyt?

@oscerd
Copy link
Contributor

oscerd commented Dec 18, 2023

I guess it makes sense to wait.

@squakez
Copy link
Contributor Author

squakez commented Dec 18, 2023

I've done the change on the runtime. As soon as we publish the snapshot I'll test with https://github.com/apache/camel-k/actions/workflows/nightly-latest-runtime.yml and if all is fine I'll start a new release process for the runtime 3.6.1 before kicking off 2.2.

@squakez
Copy link
Contributor Author

squakez commented Dec 19, 2023

I may have found a way to solve the problem. Probably we won't need to wait for the runtime release and we can start the build today itself. Let's wait for the PR's check.

@squakez
Copy link
Contributor Author

squakez commented Dec 19, 2023

Vote started.

@squakez squakez modified the milestones: 2.2.0, 2.3.0 Jan 8, 2024
@squakez squakez closed this as completed Jan 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants