Hi, Thanks for laying this out — the proposal makes sense to me. The more we work with the current structure and development model, the clearer it becomes that we need a unified approach moving forward. A leaner 10.3.x+ stream and a simplified repository structure will definitely help contributors be more effective. Count me in for supporting this direction. I’m available to help with any difficulties we might encounter along the way and to surface and address any potential issues as we move through the process.
Yeser On 2026/03/19 18:53:32 Tiago Bento wrote: > Hi all, > > As we make progress towards the 10.2 release, I’d like to propose a > refreshed development > stream focused on Drools, jBPM, and Kogito — 10.3.x+. > > This leaner stream would be developed in the `main` branch but giving it a > distinct name > (10.3.x+) marks it as a milestone in Apache KIE. > > Borrowing ideas from the original proposal for a duo-repo structure, here’s > what it would look > like: > > - A “new” `kie` repository from renaming `drools` (gotta keep the 6k > stars!), incorporating > `drools`, `optaplanner`, `kogito-runtimes`, and `kogito-apps`, minus > SonataFlow modules > - `kie-tools` continue as is, minus DashBuilder, YaRD, and SonataFlow > packages > - `kie-examples` from a renamed `kogito-examples`, with a development cycle > detached from > `kie` and `kie-tools` > - `kie-website` unchanged > - `kie-docs` unchanged > - PR checks and release automations re-written for a click-button release > process and a local- > first development setup > > The community would continue to have access to DashBuilder, YaRD, and > SonataFlow via the > 10.2.x branch. > > The 10.3.x+ stream would bring a refreshed structure to Apache KIE, reduce > barriers for new > contributors, and allow for existing contributors to collaborate more > efficiently. > > Regards, > > Tiago Bento > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
