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
I had the opportunity to represent KIE at Community Over Code earlier this
month. I wrote a blog post available at
https://cwiki.apache.org/confluence/display/KIE/2023/10/17/Apache+Community+Over+Code+2023+Recap
-
To
On 2023/10/17 19:19:25 ricardo zanini fernandes wrote:
> Opened https://issues.apache.org/jira/browse/INFRA-25091 to track this
> request. Not sure if it's gonna work, at least we will know the
> restrictions we might have.
>
> --
> Ricardo Zanini Fernandes
> Vida longa e próspera.
You can also
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
Opened https://issues.apache.org/jira/browse/INFRA-25091 to track this
request. Not sure if it's gonna work, at least we will know the
restrictions we might have.
--
Ricardo Zanini Fernandes
Vida longa e próspera.
On Tue, Oct 17, 2023 at 4:10 PM ricardo zanini fernandes <
Hi Jozef! No, that was in kie-docs [1]
[1] https://github.com/apache/incubator-kie-docs
--
Ricardo Zanini Fernandes
Vida longa e próspera.
On Mon, Oct 16, 2023 at 7:20 AM Jozef Marko
wrote:
> Can be this related somehow to contributing `main` branch vs
> `main-kogito`? I had this issue in
> 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
Tristan,
If different components have their own release cycles, and their own LTS
versioning, it’ll require a lot of effort to build and maintain a support
matrix among components. I’d argue this would go against the initial Apache
KIE proposal of the unified family of technology.
There’s also
Well, Kogito 1.x depends on Drools 8.x, so there was already some disparity
in versions...
On Tue, Oct 17, 2023 at 9:44 AM Enrique Gonzalez Martinez <
egonza...@apache.org> wrote:
> Releasing with the same version have been the norm in the community and all
> versions were align, to the point
Releasing with the same version have been the norm in the community and all
versions were align, to the point that all projects were depending on
snapshots. If we are changing this philosophy now, we will need to depend
on final versions and will bring a bunch if ci changes.
El mar, 17 oct 2023,
My 2 cents here:
Drools, SonataFlow, jBPM, Kogito are "different" components of the KIE
project and so you may have different release needs there.
Having one version for all would mean that you release everything each
time. This is quite huge ... Or you release differently but then your
version
11 matches
Mail list logo
