jameshilliard commented on pull request #4969: URL: https://github.com/apache/camel/pull/4969#issuecomment-770433295
> Quarkus 2 Is not released yet Oh, so if I'm understanding this correctly [quarkus](https://github.com/quarkusio/quarkus) and [camel](https://github.com/apache/camel/) are both dependencies of [camel quarkus](https://github.com/apache/camel-quarkus) and both need the vertx4 update before [camel quarkus](https://github.com/apache/camel-quarkus) can be updated to vertx4(got a bit confused there and hadn't realized quarkus was different from camel-quarkus)? I assume it's just finishing [this](https://github.com/quarkusio/quarkus/tree/vertx4) that's a blocker for updating [camel quarkus](https://github.com/apache/camel-quarkus) along with this PR updating [camel](https://github.com/apache/camel/)? I guess that the quarkus vertx4 update will be around march/april based on [this](https://github.com/quarkusio/quarkus/issues/13768#issuecomment-741648453)? Should we be trying to have vertx4 in a [camel](https://github.com/apache/camel/) release around the same time then? Would it make sense to merge this PR to [camel](https://github.com/apache/camel/) master or some other non-release branch like how they are doing the [vertx4 quarkus branch](https://github.com/quarkusio/quarkus/tree/vertx4) so that both are ready around the same time so that [camel quarkus](https://github.com/apache/camel-quarkus) can then be updated shortly after both? ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
