wmedvede commented on PR #2472:
URL:
https://github.com/apache/incubator-kie-tools/pull/2472#issuecomment-2236404040
> @wmedvede I'm not sure what needs to be coordinated... this PR will only
accomplish what has been long time decided.
>
> AFAIK, the original repos from where the content had to be moved never
stop the development... so I can't see why hold this change
@porcelli
It must be coordinated because, for example the build of
incubator-kie-sonataflow-builder image will disappear from one repo
(incubator/kie-tools), and a new build of the same image, will appear, but form
a different repo (incubator/incubator-kie-kogito-serverless-operator)
But, for example incubator-kie-sonataflow-builder, is based on bits from
kie-kogito-runtimes.
If we stop producing incubator-kie-sonataflow-builder from one day to the
other, we'll have that image outdated with reference to kie-kogito-runtimes.
This represent something no good for the us. (example, if we need to do a fix
in kogito-runtimes, we won't have this fix reflected in
incubator-kie-sonataflow-builder)
On the other hand, considering that the CI for
incubator-kie-sonataflow-builder is already set, and this image is already
being being produced regularly, I don't think this represents a problem nor any
extra work.
We just keep all the CI as is, that is already working, and we remove the
production for these images "coordinated".
This will help us.
If we don't do this "coordinated", operator images like
incubator-kie-sonataflow-builder, that relies on bits for example form
kogito-runtimes,
--
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]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
