You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@camel.apache.org by GitBox <gi...@apache.org> on 2022/03/28 11:04:23 UTC

[GitHub] [camel-k] oscerd opened a new issue #3138: Prepare for releasing Camel-K with Camel 3.16.0

oscerd opened a new issue #3138:
URL: https://github.com/apache/camel-k/issues/3138


   First we'll need a new Camel Quarkus release I suppose. 
   
   But it's better to check, we moved some components from camel-k-runtime to Camel and we need to double check.
   
   @astefanutti @lburgazzoli @squakez 


-- 
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.

To unsubscribe, e-mail: commits-unsubscribe@camel.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

[GitHub] [camel-k] squakez commented on issue #3138: Prepare for releasing Camel-K with Camel 3.16.0

Posted by GitBox <gi...@apache.org>.

squakez commented on issue #3138:
URL: https://github.com/apache/camel-k/issues/3138#issuecomment-1080509771


   Yes, likely we need camel->camel-quarkus->camel-k-runtime train released before applying the changes to camel-k.


-- 
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.

To unsubscribe, e-mail: commits-unsubscribe@camel.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org