tiagobento commented on issue #2090: URL: https://github.com/apache/incubator-kie-tools/issues/2090#issuecomment-1850677984
Hi @aburdiak, thanks a lot for reaching out and also for evaluating the new DMN Editor. We're confident that we're making a lot of improvements compared to the current one, and it looks like you and your team already found these improvements to help in your use case. Glad to hear that, and thanks for sharing. As for your questions: > - What is needed to publish the existing state of the package to NPM to enable it to be pulled into a React UI? Right now, we're finalizing the big PR that will introduce the new DMN Editor to the `main` branch. We expect that this PR will be merged this week. After that, we're gonna have to wait for the next release of Apache KIE to happen, so the packages will finally land on NPM. Unfortunately, we're not be able to provide an exact date yet, as there's a lot of conversations going on and also there's a lot of people working on making the release automations stable enough for a big release after we moved the KIE community to Apache. What I can tell you is that we expect this release will happen in January 2024. > - Would it be possible to publish it in its current state as an Alpha build given it is not yet complete? From our side, no. In the past we used to run KIE Tools as a separate stream compared to other KIE projects, but after the migration to Apache, we won't do that anymore. Apache KIE will have a single release stream, and KIE Tools is the "last piece of the puzzle". As of now, we don't have "dev"/"daily" releases, unfortunately, but it is definitely something we're going to look at in the future, as our users might want to be able to assess ongoing experimental modules such as the new DMN Editor. > - Would you accept contributions to enable the package to be published in the near term? At this moment, given the complexity of the entire ecosystem and also because we are also learning how we can achieve this first release in as an Apache project, I think contributing might be very hard. What I would suggest is that you stay in the loop. Asking questions, making suggestions, or even requesting information are all things that add a lot of value to the community. Sometimes we end up not documenting parts of the process and the operation of the projects that might be relevant to people depending on it, like you. ---- I'm sorry if those answers are not what you were expecting to hear, but I'm certain the Apache KIE community will gradually evolve to reaching a state where users can have a very good understanding of its release strategy as well as making it possible for people to participate in a more active way. Including experimental components/modules. In the mean time, if you really can't wait for the next release to be out, my suggestion to you would be publishing your own build of the DMN Editor, with a different scope/name and a `pre-release` version discriminator. Like `@your-org/[email protected]` or something along these lines :) Of course, once we do release it to NPM you can drop this temporary workaround and start depending on the Apache KIE package. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
