I would argue that making any more changes beyond the ongoing work for
fixing the circular deps in kie-tools for the next release should be
moved afterwards; otherwise this will never happen.
As far as my concern goes it is ok as this is fulfilled.
Regarding the discussion itself, this is the first time I saw this in
the mailing list (official channel); So I would say to create a HEADS
UP or proper PROPOSAL dependending on the size
or the scope of this would be nice for giving the chance to everyone
to get involved in the discussion and clarify what, when and the risk
involved.

El lun, 29 abr 2024 a las 16:09, Mark Proctor (<[email protected]>) escribió:
>
> Does this work for other people too? Any concerns?
>
> Mark
>
> On Mon, 29 Apr 2024 at 12:25, Walter Medvedeo <[email protected]> wrote:
>
> > Hello team,
> >
> > Regarding the topic discussed in Friday's meeting, about a potential
> > circular dependency kn-plugin-workflow -> kogito-swf-builder -> operator ->
> > kn-plugin-workflow introduced by:
> > https://github.com/apache/incubator-kie-kogito-images/issues/1739, I think
> > the concern is valid, however, I believe we should consider this:
> >
> > 1) After release 10 we have programmed work (already discussed) for
> > refactoring code from kie-tools back to the operator repository, which
> > includes the kn-plugin-workflow, etc.
> >
> > 2) https://github.com/apache/incubator-kie-kogito-images/issues/1739 is a
> > kind of "feature" request, that AFAIK is not a compromise for release 10
> >
> > So, in my opinion, we shouldn't block the release 10 because of
> > https://github.com/apache/incubator-kie-kogito-images/issues/1739.
> > Instead,
> > this should be tackled as part of 1).
> >
> > Regards,
> > Walter.
> >

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to