Hi Alex,

Thanks for creating this thread. As a first step I believe we need to bring
all the work that was done in Jenkins regarding our release automation in
the 10.1.x branches into the main branch, so we don’t have to redo all the
fixes that we did for 10.1.

I created the Release Procedure document for 10.2 [1] (a direct copy from
10.1). I added a few people as Editors already, but anyone who’s a
committer can be added as editor, just let me know.

Regards,

Tiago Bento

[1]
https://docs.google.com/document/d/1wp9WWDJb6K5gyFddgC--7TSgIRpvxL7NrZgS4wAzGoE/edit?usp=drivesdk


On Sat, Sep 27, 2025 at 09:44 Alex Porcelli <[email protected]> wrote:

> Hi all,
>
> I want to start a thread so we can organize around a 10.2.0 release.
> At the moment we are still blocked [1], but there has been some
> important movement in the ecosystem.
>
> The new Quarkus LTS just landed [2], already with Hibernate 7 (under
> ASL license). On the other hand, Spring Boot 3.x is still on Hibernate
> 6 [3], so there is a potential clash to keep in mind. Spring Boot 4 is
> close to release [4] and will align with Hibernate 7, which might open
> a good path forward.
>
> If we address the current blockers together with Hibernate 7, we are
> in a strong position. At that point the remaining issues are minimal
> and could be targeted right after 10.2.0, helping us finally move
> toward graduation.
>
> I would love to hear thoughts from the community and start shaping an
> execution plan.
>
> (thank you Jason for sparking the release topic on a private email
> exchange!)
>
> [1] - https://github.com/apache/incubator-kie-tools/issues/3196
> [2] - https://quarkus.io/blog/quarkus-3-27-released/
> [3] - https://github.com/spring-projects/spring-boot/releases/tag/v3.4.10
> and https://github.com/spring-projects/spring-boot/releases/tag/v3.5.6
> [4] -
> https://github.com/spring-projects/spring-boot/releases/tag/v4.0.0-M3
>
> -
> Alex
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>

Reply via email to