Yes. Main priority should be to have a flow of releases. Then in those releases we can work towards graduation. No releases = dead project.
Toni On Sat, Jan 11, 2025 at 12:03 AM Tiago Bento <tiagobe...@apache.org> wrote: > Hi all, > > I've started the Release Procedure document for 10.1: > > https://docs.google.com/document/d/15V-1e62bmmWeOdFUnSJHymPYoeb0TTwp0bhxPuJn4zo/edit?usp=sharing > . > > Anyone with the link can comment and if you'd like to gain Editor > access please reach out to me. > > I'd also like to point out that I created the `target:10.1.0` label in > the 5 repos that are currently part of the Release Procedure for 10.1, > plus the apache/incubator-kie-issues repo. > > I took the liberty to also add the label to some of the issues I > consider blockers for this release, and I suggest everyone does the > same for whatever they want to include in 10.1.0. After a while (not > sure how long), we can discuss each issue individually and reassess if > they should be considered blockers for 10.1.0 or not. > > We currently don't have any consensus on how to proceed regarding > Documentation, Websites, or Examples, and therefore I didn't include > those in the Release Procedure for 10.1 yet, except for some soft > mentions in the artifacts list annotated with "TODO", "TBD", or > something similar. > > Taking also the opportunity to mention that moving Documentation, > Websites, and/or Examples to `kie-tools` remains a viable option for a > long-term solution that doesn't involve tinkering with "the CI" and > its outdated/black-box systems that no one really wants to take > ownership of (namely `build-chain` or "the Kogito framework" on Apache > Jenkins). I make myself available to do ALL the work necessary to make > those artifacts be permanently part of `kie-tools` and released as > part of Apache KIE, provided we get everyone on board. I personally > think this is a wonderful opportunity to provide an immense amount of > value and material to our users, who have already manifested their > confusion in regards to Documentation, Websites, and Examples in some > of our communication channels. > > Links for issues containing the `target:10.1.0` label for all relevant > repos: > https://github.com/apache/incubator-kie-issues/labels/target%3A10.1.0 > https://github.com/apache/incubator-kie-drools/labels/target%3A10.1.0 > https://github.com/apache/incubator-kie-optaplanner/labels/target%3A10.1.0 > > https://github.com/apache/incubator-kie-kogito-runtimes/labels/target%3A10.1.0 > https://github.com/apache/incubator-kie-kogito-apps/labels/target%3A10.1.0 > https://github.com/apache/incubator-kie-tools/labels/target%3A10.1.0 > > Regards, > > Tiago Bento > > On Fri, Jan 10, 2025 at 3:45 PM Tibor Zimányi <tzima...@apache.org> wrote: > > > > +1 for starting work on the next release. > > > > Best regards, > > Tibor > > > > Dňa pi 10. 1. 2025, 19:36 Alex Porcelli <porce...@apache.org> > napísal(a): > > > > > I’d like to propose we begin the Apache KIE 10.1.0 release process as > > > soon as possible. > > > > > > The primary goal is to refine the release process and deliver a more > > > up-to-date version, as 10.0.0—branched in July 2024—reflects a > > > codebase that’s now over six months old. A refreshed release would > > > bring the latest fixes and improvements to our users and align with > > > recent contributions. > > > > > > The only ongoing work that might be included is the Quarkus LTS > > > upgrade to 3.15.x, but I wouldn’t consider this a blocker for the > > > release. > > > > > > Note: After this release, as in discussion in this thread [1], I > > > propose introducing milestones as blocker in each release to address > > > issues identified for graduation [2], ensuring a structured path > > > forward. > > > > > > Looking forward to your feedback and input to make this release a > success. > > > > > > [1] https://lists.apache.org/thread/1923vybp0p675c6pjk7bgx45pmj716xm > > > [2] https://github.com/apache/incubator-kie-issues/issues/1707 > > > > > > - > > > Alex > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: dev-unsubscr...@kie.apache.org > > > For additional commands, e-mail: dev-h...@kie.apache.org > > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@kie.apache.org > For additional commands, e-mail: dev-h...@kie.apache.org > >
