You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We need to improve the way the project is released as as today we have two competing tools when doing a release:
maven
make/bash
And of course they do not play very well (i.e. both are supposed to tag and changes versions).
I think we need to separate operator and runtime release cycles and versions and/or move the runtime to a different repo (waiting to be mature enough to be moved to camel itself).
Agreed. I would use a git submodule to replace the runtime directory if that eases transitioning so we can externalise without touching the current build for the catalogs and images.
We need to improve the way the project is released as as today we have two competing tools when doing a release:
And of course they do not play very well (i.e. both are supposed to tag and changes versions).
I think we need to separate operator and runtime release cycles and versions and/or move the runtime to a different repo (waiting to be mature enough to be moved to camel itself).
@nicolaferraro @oscerd @astefanutti thoughts ?
The text was updated successfully, but these errors were encountered: