squakez commented on PR #954: URL: https://github.com/apache/camel-k-runtime/pull/954#issuecomment-1405331870
> @squakez is it good enough for you now? Can we merge it? I'd prefer not, but let me elaborate the reason why :) We're about to release Camel K 1.12 and with it the related runtime (based on `main`). If we have unreliable metadata in the catalog, we may screw up Camel K or any other tooling that is using the catalog (there are tools based on Camel K that makes use of the catalog). The approach I was proposing hence is to reduce the uncertainty. I'd be happy to have PR both on Camel K and Camel K runtime before being able to merge on both side. That's the reason why I was proposing to make a work local to ensure you have both bits prepared and later issue the PRs so we can review and validate on both sides. Once they are both reviewed and accepted, the Camel K Runtime would be merged as first, so that we publish the related snapshot dependency. Once that is done we'd re-run Camel K PR checks and make sure the feature is really complete. I'd suggest to switch each DSL separately along you do the related development in Camel K for that reason. I know it's a bit cumbersome tuning the local development environment, but it's something we use to do frequently when there are changes on both side of the moon. Feel free to reach out if you need any support with that. -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
