Hello Guys, 

Sorry for not sending a more elaborated response, but for me guys, I see it so 
clear as this:

1) kogito-examples is the repository where we have about 150+ projects, with, 
all the combinations of usage you can even imagine, and more. Simple java 
projects, docker compose stuff, sonataflow examples that refers o minikube or 
kind, and yes, there we also like to do setups that use the images that we 
produce from kie-tools, etc, etc, etc.

To move all this to kie-tools, for me, is a suicide. Please believe me.

2) Then, independently of the fact that we should release them, kogito-examples 
should be the last repositorty in the build chain.

So, we basically produce all what our stack wants/needs to produce, and 
finally, we build the examples. The the place where we want to play with 
absolutely everything we produce, by having no restrictions.

Regards,
Walter.



On 2025/01/06 10:00:00 Alex Porcelli wrote:
> Happy new 2025, everyone!
> 
> As we discussed when we started the 10.0.0 release process, the
> kogito-examples repository was neither included in the release nor fully
> integrated into CI. Although some PR checks consider kogito-examples, this
> gap ultimately led to absent examples for the 10.0.0 release.
> 
> Currently:
> 
> - The stable branch remains on versions 1.44 and 8.44
> - The main branch is on 999-SNAPSHOT
> 
> Given that many of the kogito-examples rely on container images and Dev UI,
> we'd need to incorporate the repository into our CI system to improve the
> current situation, which might take some time and will likely impact the
> upcoming releases.
> 
> Alternatively, we could move the examples to kie-tools (a repo that already
> hosts all images and DevUI) so no CI changes would be required.
> 
> I would love to hear your thoughts, alternative ideas, or concerns so we
> can have an actionable plan to do better in the next release.
> 
> Regards,
> Alex
> 

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

Reply via email to