Just closed the thread, I'm planning to kick the build tomorrow morning.

@Kennedy, let me know if you're around so we can sync and make sure we
don't step on each other's toes.

-
Alex

On Thu, Mar 26, 2026 at 2:32 PM Alex Porcelli <[email protected]> wrote:

> I used the voting thread to communicate.. but here is my suggestion:
>
> Keep it open for the expected 72h, because in practice we only had Toshyia
> doing some verification work. It gives the "regular" expected time to keep
> it open.
>
> Once past 72h, the voting is closed, and we move forward.
>
> On Thu, Mar 26, 2026 at 2:17 PM Thiago Lugli <[email protected]> wrote:
>
>> Thanks, Alex and Kennedy!
>>
>> +1 to start running the pipelines once the pending PRs are merged.
>>
>> On Thu, Mar 26, 2026 at 3:12 PM Tiago Bento <[email protected]>
>> wrote:
>> >
>> > Thanks Alex, Kennedy, Yeser and Thiago for helping us move forward with
>> the
>> > release!
>> >
>> > I can vouch for
>> > https://github.com/apache/incubator-kie-tools/pull/3516 so I merged it.
>> >
>> > I don’t know about these, though:
>> >
>> > - https://github.com/apache/incubator-kie-kogito-runtimes/pull/4228
>> > - https://github.com/apache/incubator-kie-kogito- runtimes/pull/4228
>> > - https://github.com/apache/incubator-kie-kogito-apps/pull/2311
>> >
>> > As they’re all red.
>> >
>> > +1 to trigger an RC2 build once those are in!
>> >
>> >
>> >
>> > On Thu, Mar 26, 2026 at 14:00 Kennedy Bowers <[email protected]>
>> wrote:
>> >
>> > > Hi everyone,
>> > >
>> > > Thanks again to Alex for helping us clear the final hurdles and
>> releasing
>> > > v10.2.0-rc1.
>> > >
>> > > To keep up that momentum, I think it makes sense to begin work on RC2
>> as
>> > > soon as possible. We’re already aware of issues in RC1 that will
>> prevent
>> > > approval, and the PRs currently merged or pending against the 10.2.x
>> > > branches are expected to address these. Many thanks to Thiago and
>> Yeser for
>> > > tackling these so promptly.
>> > >
>> > > Once all PRs have been merged, I propose to start running the
>> pipelines
>> > > tomorrow, with the goal of having RC2 ready for a vote by Monday.
>> > >
>> > > Best regards,
>> > > Kennedy
>> > >
>> > > On 2026/03/24 17:40:09 Alex Porcelli wrote:
>> > > >  Hi Kennedy,
>> > > >
>> > > > I don't see any failure. Could you share link where exactly you are
>> > > looking
>> > > > at?
>> > > >
>> > > > What happened early today, during last component build, it timed
>> out (3h
>> > > > limit of that pipeline).
>> > > >
>> > > > However I triggered the build of the individual component and I
>> believe
>> > > > we'll have a RC1 sometime later today.
>> > > >
>> > > > -
>> > > > Alex
>> > > >
>> > > >
>> > > >
>> > > > On Tue, Mar 24, 2026 at 1:21 PM, Kennedy Bowers <[email protected]
>> >
>> > > wrote:
>> > > >
>> > > > > Hi Alex,
>> > > > >
>> > > > > Thanks a lot for stepping in and pushing things forward over the
>> > > weekend;
>> > > > > I really appreciate the extra time you put in.
>> > > > >
>> > > > > I see the latest kie-tools build is still failing, so I’ll check
>> out
>> > > your
>> > > > > latest update in my morning, go through the build, and fix any
>> > > additional
>> > > > > errors that may come up before rerunning the pipeline. If
>> everything
>> > > looks
>> > > > > good, I’ll continue with the next steps for the release so we can
>> keep
>> > > > > momentum across time zones, and we can sync up in your morning.
>> > > > >
>> > > > > Thanks again for jumping in and helping to accelerate this.
>> > > > >
>> > > > > Regards,
>> > > > > Kennedy
>> > > > >
>> > > > > On 2026/03/24 13:44:10 Alex Porcelli wrote:
>> > > > >
>> > > > > Thiago,
>> > > > >
>> > > > > First of all, thank you for bringing this up on the mailing list.
>> > > > >
>> > > > > Please go ahead and open the PR against 10.2.x branch. I am
>> currently
>> > > > > building the last remaining component for RC1, and the RC should
>> be
>> > > > > available within the next few hours.
>> > > > >
>> > > > > At this point, I suggest we document this as a known issue for the
>> > > current
>> > > > > RC, proceed with verification as usual (as we know, there are many
>> > > other
>> > > > > components in the release), and incorporate the fix into RC2.
>> > > > > -
>> > > > > Alex
>> > > > >
>> > > > > On Tue, Mar 24, 2026 at 9:27 AM Thiago Lugli <
>> [email protected]>
>> > > > > wrote:
>> > > > >
>> > > > > > Alex and Kennedy,
>> > > > > >
>> > > > > > While testing a few things on the KIE Tools main branch, I
>> noticed
>> > > > > > that both the jBPM Quarkus Dev UI and the Management Console
>> were
>> > > > > > broken. jBPM Quarkus Dev UI was not properly reaching the
>> GraphQL
>> > > > > > endpoints, and both were unable to load Process and Task forms.
>> > > > > > I double-checked on the 10.2.x branch, and the issue is the
>> same.
>> > > > > >
>> > > > > > I have raised a PR for main with the fixes [1], but I can also
>> > > > > > cherry-pick it for the 10.2.x branch if you're willing to run
>> the
>> > > > > > build again (at least for the jBPM Quarkus Dev UI module +
>> Management
>> > > > > > Console image).
>> > > > > >
>> > > > > >
>> > > > > > [1] https://github.com/apache/incubator-kie-tools/pull/3510
>> > > > > >
>> > > > > > On Mon, Mar 23, 2026 at 8:23 PM Alex Porcelli <
>> [email protected]>
>> > > > > wrote:
>> > > > > > >
>> > > > > > > Quick update on the KIE Tools release progress.
>> > > > > > >
>> > > > > > > The SVN file size limit issue for the swf-builder-image
>> (1.1GB) has
>> > > > > been
>> > > > > > > resolved. ASF Infra increased the limit after I reached out on
>> > > Slack.
>> > > > > The
>> > > > > > > artifact uploaded successfully.
>> > > > > > >
>> > > > > > > Also found and fixed a bug in the kogito-db-migrator-tool
>> pipeline
>> > > > > where
>> > > > > > > the PNPM filter was pointing to the wrong package, causing the
>> > > Docker
>> > > > > > image
>> > > > > > > to never be built. The corrupt artifacts were cleaned from
>> SVN, and
>> > > > > the
>> > > > > > > corrected build produced a proper 154MB image.
>> > > > > > >
>> > > > > > > 36 artifacts are now in SVN. Build #11 is currently running
>> with
>> > > the
>> > > > > > > remaining components (kogito-serverless-operator,
>> dev-deployment
>> > > > > images,
>> > > > > > > online-editor, chrome-extensions, standalone-editors-cdn,
>> > > > > > > kn-plugin-workflow).
>> > > > > > >
>> > > > > > > Will send another update once the build completes.
>> > > > > > >
>> > > > > > > -
>> > > > > > > Alex
>> > > > > > >
>> > > > > > > On Mon, Mar 23, 2026 at 1:49 PM Alex Porcelli <
>> [email protected]
>> > > >
>> > > > > > wrote:
>> > > > > > >
>> > > > > > > > Another update. Most components are now building and
>> publishing
>> > > > > > > > successfully to SVN staging.
>> > > > > > > >
>> > > > > > > > The remaining blocker is the
>> > > > > > > > `serverless-logic-web-tools-swf-builder-image`, which grew
>> from
>> > > > > ~900MB
>> > > > > > > > (10.1.0) to ~1.1GB, exceeding the ASF SVN 1GB file size
>> limit.
>> > > I've
>> > > > > > opened
>> > > > > > > > INFRA-27763 [1] and reached out to the ASF Infra team on
>> Slack.
>> > > > > They're
>> > > > > > > > already helping with the limit increase.
>> > > > > > > >
>> > > > > > > > In the meantime, I've triggered another build with the
>> remaining
>> > > ~15
>> > > > > > > > components while we wait for the limit to be raised.
>> > > > > > > >
>> > > > > > > > [1] https://issues.apache.org/jira/browse/INFRA-27763
>> > > > > > > >
>> > > > > > > > -
>> > > > > > > > Alex
>> > > > > > > >
>> > > > > > > >
>> > > > > > > >
>> > > > > > > > On Mon, Mar 23, 2026 at 5:23 AM Alex Porcelli <
>> > > [email protected]>
>> > > > > > wrote:
>> > > > > > > >
>> > > > > > > >> Another update. Made further progress with a handful of
>> > > additional
>> > > > > > > >> components, now building and publishing to SVN
>> successfully.
>> > > Still
>> > > > > > working
>> > > > > > > >> through pipeline issues and making adjustments along the
>> way.
>> > > > > > > >>
>> > > > > > > >> Two new issues were found and fixed this round:
>> > > > > > > >>
>> > > > > > > >> 1. The release-build orchestrator was trying to connect to
>> an
>> > > IP (
>> > > > > > > >> 169.61.187.58:30741) that is refusing connections,
>> blocking
>> > > > > dependent
>> > > > > > > >> jobs. Skipped those calls, as they seemed not needed for
>> the
>> > > > > release.
>> > > > > > > >>
>> > > > > > > >> 2. The `serverless-logic-web-tools-swf-builder-image`
>> built and
>> > > > > signed
>> > > > > > > >> successfully but failed during SVN upload, likely due to
>> image
>> > > > > size.
>> > > > > > > >> Retrying now, but if it fails again, we may need the SME
>> for
>> > > that
>> > > > > > image to
>> > > > > > > >> take a closer look.
>> > > > > > > >>
>> > > > > > > >> Kicked off a new build with the remaining ~21 components.
>> > > > > > > >>
>> > > > > > > >> -
>> > > > > > > >> Alex
>> > > > > > > >>
>> > > > > > > >> On Sun, Mar 22, 2026 at 10:39 PM Alex Porcelli <
>> > > [email protected]>
>> > > > >
>> > > > > > > >> wrote:
>> > > > > > > >>
>> > > > > > > >>> Quick update on KIE Tools. After several build rounds,
>> I've
>> > > > > > identified
>> > > > > > > >>> and fixed a number of pipeline issues, including stale
>> > > references
>> > > > > to
>> > > > > > > >>> removed packages, missing repo configurations, incomplete
>> RC
>> > > > > artifact
>> > > > > > > >>> flows, and misconfigured Jenkins jobs.
>> > > > > > > >>>
>> > > > > > > >>> A handful of components have already been built
>> successfully
>> > > and
>> > > > > are
>> > > > > > > >>> uploaded to staging. I just triggered another round, and
>> > > hopefully
>> > > > > > it will
>> > > > > > > >>> unlock ~25 additional components.
>> > > > > > > >>>
>> > > > > > > >>> -
>> > > > > > > >>> Alex
>> > > > > > > >>>
>> > > > > > > >>> On Sun, Mar 22, 2026 at 12:07 PM Alex Porcelli <
>> > > > > [email protected]>
>> > > > > > > >>> wrote:
>> > > > > > > >>>
>> > > > > > > >>>> Thank you.
>> > > > > > > >>>>
>> > > > > > > >>>> Now it's a waiting game while keeping an eye on the
>> Jenkins
>> > > > > > console. I
>> > > > > > > >>>> just had to retrigger the build because it failed - I
>> forgot
>> > > to
>> > > > > > manually
>> > > > > > > >>>> remove the tag from the previous run.
>> > > > > > > >>>>
>> > > > > > > >>>> I'll keep you posted.
>> > > > > > > >>>>
>> > > > > > > >>>> -
>> > > > > > > >>>> Alex
>> > > > > > > >>>>
>> > > > > > > >>>>
>> > > > > > > >>>> On Sun, Mar 22, 2026 at 11:48 AM Thiago Lugli <
>> > > > > [email protected]>
>> > > > > > > >>>> wrote:
>> > > > > > > >>>>
>> > > > > > > >>>>> Thanks, Alex!
>> > > > > > > >>>>> Let me know if you need any help with the KIE Tools
>> build
>> > > today.
>> > > > > > > >>>>>
>> > > > > > > >>>>> Em dom., 22 de mar. de 2026, 12:37, Alex Porcelli <
>> > > > > > [email protected]
>> > > > > > > >>>>> >
>> > > > > > > >>>>> escreveu:
>> > > > > > > >>>>>
>> > > > > > > >>>>> > KIE Tools release build is now running. This is the
>> longest
>> > > > > step
>> > > > > > - it
>> > > > > > > >>>>> > contains about 40 different release artifacts (other
>> repos
>> > > had
>> > > > > > only 1
>> > > > > > > >>>>> > artifact - maven jars).
>> > > > > > > >>>>> >
>> > > > > > > >>>>> > The first trigger failed, and while investigating, I
>> found
>> > > and
>> > > > > > fixed
>> > > > > > > >>>>> the
>> > > > > > > >>>>> > following:
>> > > > > > > >>>>> >
>> > > > > > > >>>>> > - Default parameters still referenced
>> `10.1.x`/`10.1.0`
>> > > > > instead
>> > > > > > of
>> > > > > > > >>>>> > `10.2.x`/`10.2.0`
>> > > > > > > >>>>> > - The release-candidate pipeline passed the branch
>> name
>> > > > > instead
>> > > > > > of
>> > > > > > > >>>>> the tag
>> > > > > > > >>>>> > name to downstream jobs, preventing SCM checkout
>> > > > > > > >>>>> > - A result variable bug in the sandbox accelerator job
>> > > could
>> > > > > > cause
>> > > > > > > >>>>> > incorrect pipeline gating
>> > > > > > > >>>>> > - Several individual release artifact jobs were
>> missing
>> > > from
>> > > > > the
>> > > > > > > >>>>> 10.2.x
>> > > > > > > >>>>> > Jenkins folder
>> > > > > > > >>>>> >
>> > > > > > > >>>>> > I'll post again once we have an update.
>> > > > > > > >>>>> >
>> > > > > > > >>>>> > -
>> > > > > > > >>>>> > Alex
>> > > > > > > >>>>> >
>> > > > > > > >>>>> > On Sat, Mar 21, 2026 at 10:26 PM Alex Porcelli <
>> > > > > > [email protected]>
>> > > > > > > >>>>> > wrote:
>> > > > > > > >>>>> >
>> > > > > > > >>>>> > > Kogito Apps has finished, no issues.
>> > > > > > > >>>>> > >
>> > > > > > > >>>>> > > Triggering KIE Tools, we'll be back tomorrow to
>> check.
>> > > > > > > >>>>> > >
>> > > > > > > >>>>> > >
>> > > > > > > >>>>> > > On Sat, Mar 21, 2026 at 9:12 PM Alex Porcelli <
>> > > > > > [email protected]
>> > > > > > > >>>>> >
>> > > > > > > >>>>> > wrote:
>> > > > > > > >>>>> > >
>> > > > > > > >>>>> > >> Another update on the 10.2 release:
>> > > > > > > >>>>> > >>
>> > > > > > > >>>>> > >> The build for the last runtime repository, Kogito
>> Apps,
>> > > has
>> > > > > > now
>> > > > > > > >>>>> started.
>> > > > > > > >>>>> > >>
>> > > > > > > >>>>> > >> Regarding Kogito Runtime, we encountered another
>> issue
>> > > > > where
>> > > > > > a new
>> > > > > > > >>>>> > Gradle
>> > > > > > > >>>>> > >> test module broke the javadoc release build. I have
>> > > > > disabled
>> > > > > > it
>> > > > > > > >>>>> to move
>> > > > > > > >>>>> > >> forward and created the following ticket to track
>> the
>> > > fix:
>> > > > > > > >>>>> > >>
>> > > https://github.com/apache/incubator-kie-issues/issues/2274
>> > > > > > > >>>>> > >>
>> > > > > > > >>>>> > >> -
>> > > > > > > >>>>> > >> Alex
>> > > > > > > >>>>> > >>
>> > > > > > > >>>>> > >>
>> > > > > > > >>>>> > >> On Sat, Mar 21, 2026 at 6:08 PM Alex Porcelli <
>> > > > > > > >>>>> [email protected]>
>> > > > > > > >>>>> > >> wrote:
>> > > > > > > >>>>> > >>
>> > > > > > > >>>>> > >>> Quick update on the 10.2 release progress:
>> > > > > > > >>>>> > >>>
>> > > > > > > >>>>> > >>> The OptaPlanner build had some failures due to
>> changes
>> > > in
>> > > > > the
>> > > > > > > >>>>> > repository
>> > > > > > > >>>>> > >>> structure since the 10.1.0 release, specifically
>> > > related
>> > > > > to
>> > > > > > > >>>>> relocated
>> > > > > > > >>>>> > >>> documentation. I've fixed the issues, and the
>> build is
>> > > now
>> > > > > > > >>>>> complete.
>> > > > > > > >>>>> > >>>
>> > > > > > > >>>>> > >>> I am now starting the kogito-runtime build.
>> > > > > > > >>>>> > >>>
>> > > > > > > >>>>> > >>> -
>> > > > > > > >>>>> > >>> Alex
>> > > > > > > >>>>> > >>>
>> > > > > > > >>>>> > >>> On Fri, Mar 20, 2026 at 5:54 PM Alex Porcelli <
>> > > > > > > >>>>> [email protected]>
>> > > > > > > >>>>> > >>> wrote:
>> > > > > > > >>>>> > >>>
>> > > > > > > >>>>> > >>>> Thanks for the quick support.
>> > > > > > > >>>>> > >>>>
>> > > > > > > >>>>> > >>>> Based on this initial feedback, and to help keep
>> > > things
>> > > > > > moving,
>> > > > > > > >>>>> I’ll
>> > > > > > > >>>>> > >>>> go ahead and start working on the release over
>> the
>> > > > > weekend.
>> > > > > > > >>>>> > >>>>
>> > > > > > > >>>>> > >>>> I’ll share progress as I go, and we can continue
>> > > > > > coordinating
>> > > > > > > >>>>> together
>> > > > > > > >>>>> > >>>> early next week on the remaining pieces.
>> > > > > > > >>>>> > >>>>
>> > > > > > > >>>>> > >>>> On Fri, Mar 20, 2026 at 1:05 PM Fabrizio
>> Antonangeli
>> > > > > > > >>>>> > >>>> <[email protected]> wrote:
>> > > > > > > >>>>> > >>>> >
>> > > > > > > >>>>> > >>>> > +1 from me as well
>> > > > > > > >>>>> > >>>> >
>> > > > > > > >>>>> > >>>> > On Fri, 2026-03-20 at 16:57 +0200, Toni Rikkola
>> > > wrote:
>> > > > > > > >>>>> > >>>> > > I will +1 adding Alex in. He has worked on
>> this
>> > > > > before
>> > > > > > and
>> > > > > > > >>>>> can
>> > > > > > > >>>>> > help.
>> > > > > > > >>>>> > >>>> > >
>> > > > > > > >>>>> > >>>> > > Toni
>> > > > > > > >>>>> > >>>> > >
>> > > > > > > >>>>> > >>>> > > On 20/03/2026 16.54, Alex Porcelli wrote:
>> > > > > > > >>>>> > >>>> > > > Hi everyone,
>> > > > > > > >>>>> > >>>> > > >
>> > > > > > > >>>>> > >>>> > > > I’d like to propose stepping in as an
>> additional
>> > > > > > release
>> > > > > > > >>>>> manager
>> > > > > > > >>>>> > >>>> > > > for the
>> > > > > > > >>>>> > >>>> > > > 10.2 release so we can help move things
>> forward.
>> > > > > > > >>>>> > >>>> > > >
>> > > > > > > >>>>> > >>>> > > > It looks like progress has slowed a bit,
>> and
>> > > rather
>> > > > > > than
>> > > > > > > >>>>> let the
>> > > > > > > >>>>> > >>>> > > > release
>> > > > > > > >>>>> > >>>> > > > sit any longer, I’m happy to help push
>> things
>> > > along
>> > > > > > this
>> > > > > > > >>>>> weekend
>> > > > > > > >>>>> > >>>> on
>> > > > > > > >>>>> > >>>> > > > the
>> > > > > > > >>>>> > >>>> > > > backend repositories where I can contribute
>> > > > > directly.
>> > > > > > > >>>>> Then, at
>> > > > > > > >>>>> > the
>> > > > > > > >>>>> > >>>> > > > beginning of next week, we can continue the
>> > > effort
>> > > > > > > >>>>> together and
>> > > > > > > >>>>> > >>>> > > > coordinate
>> > > > > > > >>>>> > >>>> > > > on the remaining pieces.
>> > > > > > > >>>>> > >>>> > > >
>> > > > > > > >>>>> > >>>> > > > My goal here is simply to help accelerate
>> the
>> > > > > release
>> > > > > > and
>> > > > > > > >>>>> get us
>> > > > > > > >>>>> > >>>> to
>> > > > > > > >>>>> > >>>> > > > an RC
>> > > > > > > >>>>> > >>>> > > > as smoothly as possible.
>> > > > > > > >>>>> > >>>> > > >
>> > > > > > > >>>>> > >>>> > > > If there are no objections, I’m ready to
>> jump in
>> > > > > and
>> > > > > > > >>>>> assist with
>> > > > > > > >>>>> > >>>> > > > the
>> > > > > > > >>>>> > >>>> > > > release work.
>> > > > > > > >>>>> > >>>> > > >
>> > > > > > > >>>>> > >>>> > > > -
>> > > > > > > >>>>> > >>>> > > > Alex
>> > > > > > > >>>>> > >>>> > > >
>> > > > > > > >>>>> > >>>> > > > On Sun, Mar 15, 2026 at 4:07 PM, Alex
>> Porcelli <
>> > > > > > > >>>>> > [email protected]>
>> > > > > > > >>>>> > >>>> > > > wrote:
>> > > > > > > >>>>> > >>>> > > >
>> > > > > > > >>>>> > >>>> > > > > Hi Kennedy,
>> > > > > > > >>>>> > >>>> > > > >
>> > > > > > > >>>>> > >>>> > > > > Looks like you didn't close the Drools
>> nexus
>> > > > > > repository
>> > > > > > > >>>>> as
>> > > > > > > >>>>> > >>>> > > > > documented in
>> > > > > > > >>>>> > >>>> > > > > the release document.
>> > > > > > > >>>>> > >>>> > > > >
>> > > > > > > >>>>> > >>>> > > > > Let me know if you need additional help
>> to
>> > > speed
>> > > > > up
>> > > > > > this
>> > > > > > > >>>>> > >>>> release,
>> > > > > > > >>>>> > >>>> > > > > I'm more
>> > > > > > > >>>>> > >>>> > > > > than happy to work on this release with
>> you.
>> > > > > > > >>>>> > >>>> > > > >
>> > > > > > > >>>>> > >>>> > > > > -
>> > > > > > > >>>>> > >>>> > > > > Alex
>> > > > > > > >>>>> > >>>> > > > >
>> > > > > > > >>>>> > >>>> > > > >
>> > > > > > > >>>>> > >>>> > > > > On Fri, Mar 13, 2026 at 9:03 AM, Kennedy
>> > > Bowers
>> > > > > > > >>>>> > >>>> > > > > <[email protected]>
>> > > > > > > >>>>> > >>>> > > > > wrote:
>> > > > > > > >>>>> > >>>> > > > >
>> > > > > > > >>>>> > >>>> > > > > > Hi Alex,
>> > > > > > > >>>>> > >>>> > > > > >
>> > > > > > > >>>>> > >>>> > > > > > Thanks, I appreciate it.
>> > > > > > > >>>>> > >>>> > > > > >
>> > > > > > > >>>>> > >>>> > > > > > I've managed to fix the issues and
>> > > successfully
>> > > > > > > >>>>> branched all
>> > > > > > > >>>>> > >>>> > > > > > repositories
>> > > > > > > >>>>> > >>>> > > > > > to 10.2. They have all now been
>> updated to
>> > > > > version
>> > > > > > > >>>>> 10.2.999-
>> > > > > > > >>>>> > >>>> > > > > > SNAPSHOT.
>> > > > > > > >>>>> > >>>> > > > > >
>> > > > > > > >>>>> > >>>> > > > > > I continued the release process by
>> running
>> > > the
>> > > > > > Drools
>> > > > > > > >>>>> > release
>> > > > > > > >>>>> > >>>> > > > > > job and it
>> > > > > > > >>>>> > >>>> > > > > > completed successfully. However, when
>> > > running
>> > > > > the
>> > > > > > > >>>>> > OptaPlanner
>> > > > > > > >>>>> > >>>> > > > > > job, I’m
>> > > > > > > >>>>> > >>>> > > > > > getting an error that appears to be
>> related
>> > > to
>> > > > > > invalid
>> > > > > > > >>>>> > >>>> > > > > > credentials, as it
>> > > > > > > >>>>> > >>>> > > > > > cannot access the staging repository.
>> > > > > > > >>>>> > >>>> > > > > >
>> > > > > > > >>>>> > >>>> > > > > > Do you have any ideas on how this
>> could be
>> > > > > > resolved?
>> > > > > > > >>>>> > >>>> > > > > >
>> > > > > > > >>>>> > >>>> > > > > > Many thanks,
>> > > > > > > >>>>> > >>>> > > > > > Kennedy
>> > > > > > > >>>>> > >>>> > > > > >
>> > > > > > > >>>>> > >>>> > > > > > On 2026/03/06 16:48:59 Alex Porcelli
>> wrote:
>> > > > > > > >>>>> > >>>> > > > > >
>> > > > > > > >>>>> > >>>> > > > > > Kennedy,
>> > > > > > > >>>>> > >>>> > > > > >
>> > > > > > > >>>>> > >>>> > > > > > I can help and work on this, the
>> sooner we
>> > > have
>> > > > > > the
>> > > > > > > >>>>> release
>> > > > > > > >>>>> > >>>> the
>> > > > > > > >>>>> > >>>> > > > > > better.
>> > > > > > > >>>>> > >>>> > > > > >
>> > > > > > > >>>>> > >>>> > > > > > -
>> > > > > > > >>>>> > >>>> > > > > > Alex
>> > > > > > > >>>>> > >>>> > > > > >
>> > > > > > > >>>>> > >>>> > > > > > On Thu, Mar 05, 2026 at 2:46 PM,
>> Kennedy <
>> > > > > > > >>>>> > [email protected]>
>> > > > > > > >>>>> > >>>> > > > > > wrote:
>> > > > > > > >>>>> > >>>> > > > > >
>> > > > > > > >>>>> > >>>> > > > > > Hi Alex,
>> > > > > > > >>>>> > >>>> > > > > >
>> > > > > > > >>>>> > >>>> > > > > > The Drools CI ran successfully and
>> updated
>> > > the
>> > > > > > > >>>>> 999-SNAPSHOT
>> > > > > > > >>>>> > >>>> > > > > > versions as
>> > > > > > > >>>>> > >>>> > > > > > expected. However, the OptaPlanner and
>> > > Kogito
>> > > > > > builds
>> > > > > > > >>>>> were
>> > > > > > > >>>>> > >>>> > > > > > unstable and
>> > > > > > > >>>>> > >>>> > > > > > didn't correctly update the
>> 999-SNAPSHOT
>> > > > > version,
>> > > > > > so
>> > > > > > > >>>>> I'm
>> > > > > > > >>>>> > >>>> > > > > > currently
>> > > > > > > >>>>> > >>>> > > > > > investigating those issues before
>> proceeding
>> > > > > with
>> > > > > > the
>> > > > > > > >>>>> > >>>> kie-tools
>> > > > > > > >>>>> > >>>> > > > > > build. I
>> > > > > > > >>>>> > >>>> > > > > > plan on branching the kie-tools repo
>> next
>> > > week
>> > > > > > once
>> > > > > > > >>>>> that's
>> > > > > > > >>>>> > >>>> > > > > > resolved.
>> > > > > > > >>>>> > >>>> > > > > >
>> > > > > > > >>>>> > >>>> > > > > > I'll update the Zulip thread as I make
>> > > > > progress.
>> > > > > > > >>>>> > >>>> > > > > >
>> > > > > > > >>>>> > >>>> > > > > > Best regards,
>> > > > > > > >>>>> > >>>> > > > > > Kennedy
>> > > > > > > >>>>> > >>>> > > > > >
>> > > > > > > >>>>> > >>>> > > > > > On Tue, Mar 3, 2026 at 5:03 PM Alex
>> Porcelli
>> > > > > > > >>>>> > >>>> > > > > > <[email protected]>
>> > > > > > > >>>>> > >>>> > > > > > wrote:
>> > > > > > > >>>>> > >>>> > > > > >
>> > > > > > > >>>>> > >>>> > > > > > Hi Kennedy,
>> > > > > > > >>>>> > >>>> > > > > >
>> > > > > > > >>>>> > >>>> > > > > > I wanted to follow up and see if you
>> could
>> > > > > share
>> > > > > > an
>> > > > > > > >>>>> update
>> > > > > > > >>>>> > on
>> > > > > > > >>>>> > >>>> > > > > > the release
>> > > > > > > >>>>> > >>>> > > > > > status. I took a look at the
>> repositories,
>> > > and
>> > > > > > while
>> > > > > > > >>>>> some
>> > > > > > > >>>>> > now
>> > > > > > > >>>>> > >>>> > > > > > have 10.2.x
>> > > > > > > >>>>> > >>>> > > > > > branches, I noticed the versions are
>> still
>> > > set
>> > > > > to
>> > > > > > > >>>>> > >>>> 999-SNAPSHOT,
>> > > > > > > >>>>> > >>>> > > > > > which
>> > > > > > > >>>>> > >>>> > > > > > suggests the automation may not have
>> > > completed
>> > > > > > > >>>>> successfully.
>> > > > > > > >>>>> > >>>> > > > > >
>> > > > > > > >>>>> > >>>> > > > > > I also noticed that kie-tools doesn't
>> > > appear to
>> > > > > > have
>> > > > > > > >>>>> been
>> > > > > > > >>>>> > >>>> > > > > > branched yet,
>> > > > > > > >>>>> > >>>> > > > > > which could put us at risk of getting
>> out of
>> > > > > sync
>> > > > > > > >>>>> with the
>> > > > > > > >>>>> > >>>> rest
>> > > > > > > >>>>> > >>>> > > > > > of the
>> > > > > > > >>>>> > >>>> > > > > > release.
>> > > > > > > >>>>> > >>>> > > > > >
>> > > > > > > >>>>> > >>>> > > > > > Could you provide some clarity on the
>> > > current
>> > > > > > state
>> > > > > > > >>>>> and next
>> > > > > > > >>>>> > >>>> > > > > > steps?
>> > > > > > > >>>>> > >>>> > > > > >
>> > > > > > > >>>>> > >>>> > > > > > Thanks,
>> > > > > > > >>>>> > >>>> > > > > > Alex
>> > > > > > > >>>>> > >>>> > > > > >
>> > > > > > > >>>>> > >>>> > > > > > On Tue, Feb 24, 2026 at 3:44 AM,
>> Dominik
>> > > Hanak
>> > > > > > > >>>>> > >>>> > > > > > <[email protected]>
>> > > > > > > >>>>> > >>>> > > > > > wrote:
>> > > > > > > >>>>> > >>>> > > > > >
>> > > > > > > >>>>> > >>>> > > > > > Good news!
>> > > > > > > >>>>> > >>>> > > > > >
>> > > > > > > >>>>> > >>>> > > > > > Thank you Kennedy!
>> > > > > > > >>>>> > >>>> > > > > >
>> > > > > > > >>>>> > >>>> > > > > > Following our past practice I have
>> created a
>> > > > > zulip
>> > > > > > > >>>>> topic[1]
>> > > > > > > >>>>> > to
>> > > > > > > >>>>> > >>>> > > > > > facilitate
>> > > > > > > >>>>> > >>>> > > > > > collaboration on the release.
>> > > > > > > >>>>> > >>>> > > > > >
>> > > > > > > >>>>> > >>>> > > > > > [1]
>> > > > > > > >>>>> > >>>> > > > > >
>> > > > > > > >>>>> > >>>> > > > > >
>> > > > > > > >>>>> > >>>>
>> > > > > > > >>>>> >
>> > > > > > > >>>>>
>> > > > > >
>> > > > >
>> > >
>> https://kie.zulipchat.com/#narrow/channel/386449-kie-dev/topic/10.2E2.2E0
>> > > > > > > >>>>> > >>>> > > > > > .
>> > > > > > > >>>>> > >>>> > > > > >
>> > > > > > > >>>>> > >>>> > > > > >
>> > > > > > > >>>>> > >>>> > > > > > 20Release.20Thread/with/575482378
>> > > > > > > >>>>> > >>>> > > > > >
>> > > > > > > >>>>> > >>>> > > > > > Dominik
>> > > > > > > >>>>> > >>>> > > > > >
>> > > > > > > >>>>> > >>>> > > > > > On Mon, 23 Feb 2026 at 15:35, Kennedy <
>> > > > > > > >>>>> [email protected]>
>> > > > > > > >>>>> > >>>> > > > > > wrote:
>> > > > > > > >>>>> > >>>> > > > > >
>> > > > > > > >>>>> > >>>> > > > > > Hi everyone,
>> > > > > > > >>>>> > >>>> > > > > >
>> > > > > > > >>>>> > >>>> > > > > > Thank you for your patience as we
>> finalize
>> > > > > > > >>>>> preparations for
>> > > > > > > >>>>> > >>>> the
>> > > > > > > >>>>> > >>>> > > > > > 10.2
>> > > > > > > >>>>> > >>>> > > > > > release. I appreciate everyone
>> pitching in
>> > > with
>> > > > > > PRs
>> > > > > > > >>>>> and
>> > > > > > > >>>>> > >>>> reviews
>> > > > > > > >>>>> > >>>> > > > > > to keep
>> > > > > > > >>>>> > >>>> > > > > >
>> > > > > > > >>>>> > >>>> > > > > > the
>> > > > > > > >>>>> > >>>> > > > > >
>> > > > > > > >>>>> > >>>> > > > > > momentum going.
>> > > > > > > >>>>> > >>>> > > > > >
>> > > > > > > >>>>> > >>>> > > > > > I’m pleased to share that the final PR
>> > > related
>> > > > > to
>> > > > > > the
>> > > > > > > >>>>> new
>> > > > > > > >>>>> > BPMN
>> > > > > > > >>>>> > >>>> > > > > > Editor,
>> > > > > > > >>>>> > >>>> > > > > > first announced here [1], has now been
>> > > merged
>> > > > > > [2]. A
>> > > > > > > >>>>> big
>> > > > > > > >>>>> > thank
>> > > > > > > >>>>> > >>>> > > > > > you to
>> > > > > > > >>>>> > >>>> > > > > >
>> > > > > > > >>>>> > >>>> > > > > > Tiago
>> > > > > > > >>>>> > >>>> > > > > >
>> > > > > > > >>>>> > >>>> > > > > > Bento for the significant work behind
>> this
>> > > > > > > >>>>> modernization
>> > > > > > > >>>>> > >>>> > > > > > effort, which
>> > > > > > > >>>>> > >>>> > > > > > allows us to move away from our GWT
>> > > dependency
>> > > > > and
>> > > > > > > >>>>> brings us
>> > > > > > > >>>>> > >>>> > > > > > further into
>> > > > > > > >>>>> > >>>> > > > > > compliance with Apache guidelines.
>> > > > > > > >>>>> > >>>> > > > > >
>> > > > > > > >>>>> > >>>> > > > > > Additionally, all Quarkus and Spring
>> Boot
>> > > > > upgrades
>> > > > > > > >>>>> have been
>> > > > > > > >>>>> > >>>> > > > > > successfully
>> > > > > > > >>>>> > >>>> > > > > > merged. Many thanks to Jijo Thomas K
>> and
>> > > Nithin
>> > > > > R
>> > > > > > > >>>>> Krishnan
>> > > > > > > >>>>> > for
>> > > > > > > >>>>> > >>>> > > > > > your work
>> > > > > > > >>>>> > >>>> > > > > >
>> > > > > > > >>>>> > >>>> > > > > > on
>> > > > > > > >>>>> > >>>> > > > > >
>> > > > > > > >>>>> > >>>> > > > > > these updates [3].
>> > > > > > > >>>>> > >>>> > > > > >
>> > > > > > > >>>>> > >>>> > > > > > Our original plan for the 10.2 release
>> was
>> > > to
>> > > > > > remove
>> > > > > > > >>>>> the
>> > > > > > > >>>>> > GWT-
>> > > > > > > >>>>> > >>>> > > > > > based
>> > > > > > > >>>>> > >>>> > > > > > BPMN/DMN/SceSim Editors from the
>> codebase,
>> > > with
>> > > > > > the
>> > > > > > > >>>>> Quarkus
>> > > > > > > >>>>> > >>>> and
>> > > > > > > >>>>> > >>>> > > > > > Spring
>> > > > > > > >>>>> > >>>> > > > > >
>> > > > > > > >>>>> > >>>> > > > > > Boot
>> > > > > > > >>>>> > >>>> > > > > >
>> > > > > > > >>>>> > >>>> > > > > > upgrades scheduled for the following
>> > > release.
>> > > > > > Because
>> > > > > > > >>>>> the
>> > > > > > > >>>>> > GWT
>> > > > > > > >>>>> > >>>> > > > > > work took
>> > > > > > > >>>>> > >>>> > > > > > longer than anticipated, it’s great
>> that we
>> > > are
>> > > > > > now
>> > > > > > > >>>>> able to
>> > > > > > > >>>>> > >>>> > > > > > include these
>> > > > > > > >>>>> > >>>> > > > > > upgrades in 10.2 as well.
>> > > > > > > >>>>> > >>>> > > > > >
>> > > > > > > >>>>> > >>>> > > > > > I will begin running the CI pipelines
>> > > tomorrow
>> > > > > > > >>>>> morning (CET)
>> > > > > > > >>>>> > >>>> > > > > > which will
>> > > > > > > >>>>> > >>>> > > > > > create the new 10.2.x branches. If you
>> have
>> > > any
>> > > > > > PRs
>> > > > > > > >>>>> that you
>> > > > > > > >>>>> > >>>> > > > > > believe
>> > > > > > > >>>>> > >>>> > > > > >
>> > > > > > > >>>>> > >>>> > > > > > should
>> > > > > > > >>>>> > >>>> > > > > >
>> > > > > > > >>>>> > >>>> > > > > > be included in this release and would
>> > > justify a
>> > > > > > short
>> > > > > > > >>>>> delay,
>> > > > > > > >>>>> > >>>> > > > > > please
>> > > > > > > >>>>> > >>>> > > > > >
>> > > > > > > >>>>> > >>>> > > > > > respond
>> > > > > > > >>>>> > >>>> > > > > >
>> > > > > > > >>>>> > >>>> > > > > > here. That said, given the time since
>> 10.1,
>> > > I
>> > > > > > believe
>> > > > > > > >>>>> it’s
>> > > > > > > >>>>> > >>>> > > > > > important that
>> > > > > > > >>>>> > >>>> > > > > > we move forward and publish this
>> release
>> > > soon
>> > > > > to
>> > > > > > > >>>>> > re-establish
>> > > > > > > >>>>> > >>>> a
>> > > > > > > >>>>> > >>>> > > > > >
>> > > > > > > >>>>> > >>>> > > > > > consistent
>> > > > > > > >>>>> > >>>> > > > > >
>> > > > > > > >>>>> > >>>> > > > > > and reliable release cadence.
>> > > > > > > >>>>> > >>>> > > > > >
>> > > > > > > >>>>> > >>>> > > > > > Kind regards,
>> > > > > > > >>>>> > >>>> > > > > >
>> > > > > > > >>>>> > >>>> > > > > > Kennedy
>> > > > > > > >>>>> > >>>> > > > > >
>> > > > > > > >>>>> > >>>> > > > > > [1]
>> > > > > > > >>>>> > >>>> > > > > >
>> > > > > > > >>>>> > >>>>
>> > > > > > > >>>>>
>> > > https://lists.apache.org/thread/87863y10qxm564cc76svvonslponv2f9
>> > > > > > > >>>>> > >>>> > > > > > [2]
>> > > > > > > >>>>> https://github.com/apache/incubator-kie-tools/pull/3448
>> > > > > > > >>>>> > >>>> > > > > > [3]
>> > > > > > > >>>>> > >>>> > > > > >
>> > > > > > > >>>>> > >>>>
>> > > > > > > >>>>>
>> > > https://lists.apache.org/thread/314vb9wxt22r0t4rh6xqlcf78yz66wv5
>> > > > > > > >>>>> > >>>> > > > > >
>> > > > > > > >>>>> > >>>> > > > > >
>> > > > > > > >>>>> > >>>>
>> > > > > > ---------------------------------------------------------------
>> > > > > > > >>>>> > >>>> > > > > > ------ To
>> > > > > > > >>>>> > >>>> > > > > > unsubscribe, e-mail:
>> > > > > > [email protected]
>> > > > > > > >>>>> For
>> > > > > > > >>>>> > >>>> > > > > > additional
>> > > > > > > >>>>> > >>>> > > > > > commands, e-mail:
>> [email protected]
>> > > > > > > >>>>> > >>>> > > > > >
>> > > > > > > >>>>> > >>>> > > > >
>> > > > > > > >>>>> > >>>> > > > >
>> > > > > > > >>>>> > >>>> > >
>> > > > > > > >>>>> > >>>> > >
>> > > > > > > >>>>> > >>>>
>> > > > > > > >>>>>
>> > > > > >
>> ---------------------------------------------------------------------
>> > > > > > > >>>>> > >>>> > > To unsubscribe, e-mail:
>> > > > > [email protected]
>> > > > > > > >>>>> > >>>> > > For additional commands, e-mail:
>> > > > > > [email protected]
>> > > > > > > >>>>> > >>>> > >
>> > > > > > > >>>>> > >>>>
>> > > > > > > >>>>> > >>>
>> > > > > > > >>>>> >
>> > > > > > > >>>>>
>> > > > > > > >>>>
>> > > > > >
>> > > > > >
>> ---------------------------------------------------------------------
>> > > > > > To unsubscribe, e-mail: [email protected]
>> > > > > > For additional commands, e-mail: [email protected]
>> > > > > >
>> > > > > >
>> > > > >
>> > > > >
>> ---------------------------------------------------------------------
>> > > To
>> > > > > unsubscribe, e-mail: [email protected] For
>> additional
>> > > > > commands, e-mail: [email protected]
>> > > > >
>> > > >
>> > >
>> > > ---------------------------------------------------------------------
>> > > To unsubscribe, e-mail: [email protected]
>> > > For additional commands, e-mail: [email protected]
>> > >
>> > >
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [email protected]
>> For additional commands, e-mail: [email protected]
>>
>>

Reply via email to