Hi,

as you all know, our community releases take a longer time to get out
currently. I would like to propose a discussion about a different release
model for our community. Here is the proposal, I am curious about your
feedback and what you think about it.

1. The community would follow a release process similar to OpenJDK. This
means, that the release would consists only from sources that can be used
to build the binaries and artifacts.
2. No binary builds would be published as part of Apache KIE community.
3. With the source code available, it would be up to vendors or anyone else
to decide, if they want to publish their own binaries built out of the
community sources. This would enable multiple various sets of binaries to
be available, similarly as with OpenJDK (e.g. there are Temurin builds, IBM
builds, Oracle builds, etc.).
4. No vendor can publish under existing Apache KIE groupIds and similar
artifact group names.

This would mean, we could regularly release the source code with new
functionalities and anyone who finds it beneficial to publish a set of
binaries from the sources, can do so. We may even have those binaries
vendors published on our Apache KIE website.

Looking forward to your feedback and discussion! I know it is a very
different to what we do now and I know that it would make it harder for
people that use the community binaries directly, however if enough vendors
of binaries jump on this, it shouldn't be a problem.

Best regards,
Tibor

Reply via email to