Jason, I think we’ll revamp jBPM, the same way SonataFlow has been.
With that being said, I think this will take a little longer until we properly manage to make the necessary readjustment in the codebase structure. Unless we want hold for a longer time to release, what I personally think is not a great idea :) On Tue, Oct 17, 2023 at 6:14 PM Jason Porter <[email protected]> wrote: > On 2023/10/17 13:18:59 Mario Fusco wrote: > > > Well, Kogito 1.x depends on Drools 8.x, so there was already some > disparity > > > in versions... > > > > Disparity in versions is incidental and doesn't imply a different > lifecycle in this case. Actually what we did so far is always releasing > Drools and Kogito in parallel every 3 weeks at the end of each sprint. Now > we are at Drools 8.44 and Kogito 1.44 and the minor release numbers are not > aligned by coincidence. > > Does this also hold true for jBPM? I know we have not done a release of > jBPM for some time. Maybe the release at Apache would signify enough of a > change for people to take notice again? > > > > > Given this premise I like the idea of a fresh start for versions > numbering and having exactly the same version numbers for both Drools and > Kogito will help to get rid of any ambiguity and underline the relationship > between the 2. > > > > Mario > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [email protected] > > For additional commands, e-mail: [email protected] > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
