Thank you, Alex. I'm looking at the drools test failure and filed a fix PR : https://github.com/apache/incubator-kie-drools/pull/6328
Toshiya On Wed, Apr 30, 2025 at 6:13 AM Alex Porcelli <a...@porcelli.me> wrote: > Since yesterday a new attempt to release is in progress. > > The good news: after fighting with pipelines, the 10.1.x branches are > correctly created and with the proper version in place. > > However, I suspect there's a build failure in Drools and looks like a > legitimate issue, this came up during the docs removal PR [1]. I'd > appreciate it if any Drools SME could double check before proceeding > with the release. > > [1] - https://github.com/apache/incubator-kie-drools/pull/6327 > > On Thu, Mar 27, 2025 at 8:29 PM Alex Porcelli <a...@porcelli.me> wrote: > > > > Hi Team, > > > > Just a quick update - unfortunately, I discovered today that the > > branching pipelines for Kogito have failed, resulting in the 10.1.x > > branches being created with the 999-SNAPSHOT version in a few > > repositories (runtimes and apps) > > > > I attempted to re-run the pipeline, but unfortunately, that didn’t > > resolve the issue. At this point, I'm considering manually pushing the > > version update. The alternative would be to ask Apache Infra to delete > > the branches across all repositories so we can create a new weekly > > build, sync with KIE Tools, and restart the branching process from > > scratch. > > > > I’ll revisit this on Monday, as I have a planned day off tomorrow. > > > > - > > Alex > > > > On Wed, Mar 26, 2025 at 11:26 AM Alex Porcelli <a...@porcelli.me> wrote: > > > > > > Hi all, > > > > > > Just a quick update: all Jenkins release pipelines are currently > > > outdated and non-functional. During the 10.0.0 release, several > > > changes were made to the pipelines that were never fully brought back > > > to main. Additionally, some modifications exist only on main and were > > > not applied consistently across the different release branches. > > > > > > As a result, I'm currently working through each pipeline, resolving a > > > number of conflicts and inconsistencies to bring them back into sync. > > > This has proven to be quite time-consuming. > > > > > > Full transparency: I'm doing some direct commits/pushes for those > > > isolated CI-related changes to the 10.1.x branch. Much of this work > > > involves trial and error due to the lack of a local Jenkins > > > environment that mirrors Apache's setup. Requiring PR reviews for > > > every small change would significantly slow down progress and make an > > > already complex task even harder. > > > > > > I’ll keep you posted as things evolve. > > > > > > On Tue, Mar 25, 2025 at 11:38 AM ricardo zanini fernandes > > > <ricardozan...@gmail.com> wrote: > > > > > > > > +1 > > > > > > > > On Thu, Mar 20, 2025 at 8:52 AM Alex Porcelli <a...@porcelli.me> > wrote: > > > > > > > > > Quick update, the release repositories have been branched. > > > > > > > > > > For more dynamic updates, we have a topic [1] in Zulip. > > > > > > > > > > [1] - > > > > > > https://kie.zulipchat.com/#narrow/channel/386449-kie-dev/topic/10.2E1.20release.20megathread > > > > > > > > > > On Tue, Mar 18, 2025 at 3:53 AM Paolo Bizzarri <pibi...@gmail.com> > wrote: > > > > > > > > > > > > As said by others, happy to learn and help here. > > > > > > > > > > > > Regards > > > > > > > > > > > > P. > > > > > > > > > > > > On Fri, Mar 14, 2025 at 2:07 PM Alex Porcelli <a...@porcelli.me> > wrote: > > > > > > > > > > > > > In light of recent discussions and the challenges we've faced > as a > > > > > > > community, I propose a pragmatic step forward: a short-term > 10.1.0 > > > > > > > release cut directly from the main. > > > > > > > > > > > > > > While 10.0.0 was officially released in December, the branch > for that > > > > > > > release was cut mid-last year, meaning that our current > codebase has > > > > > > > significantly evolved since then. Given the substantial > improvements > > > > > > > and fixes accumulated over the past months, I believe an > immediate > > > > > > > 10.1.0 release would provide tangible value to our user base. > > > > > > > > > > > > > > This proposal puts our users first by ensuring they receive an > updated > > > > > > > and more stable version without further delay. > > > > > > > > > > > > > > With this in mind, I propose the following: > > > > > > > > > > > > > > - Temporarily pausing the implementation of previously voted > proposals > > > > > > > to allow time for a proper discussion on our bylaws and to > give the > > > > > > > community space to heal from recent escalations. > > > > > > > - Focusing on delivering 10.1.0 as an incremental update that > brings > > > > > > > our latest work to users sooner rather than later. > > > > > > > - Cutting the release branch early next week, assuming there is > > > > > consensus. > > > > > > > > > > > > > > I’m happy to take the lead in managing the release process and > would > > > > > > > appreciate feedback on the proposal and the timing for > branching. > > > > > > > > > > > > > > I'm looking forward to hearing your thoughts. > > > > > > > > > > > > > > - > > > > > > > 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 > > > > > > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@kie.apache.org > For additional commands, e-mail: dev-h...@kie.apache.org > >
