Quarkus 3.15.4 LTS release preparation + branch freeze

10 views
Skip to first unread message

Jan Martiška

unread,
Mar 4, 2025, 9:41:08 AMMar 4
to quarkus-platfo...@googlegroups.com
Hi,
as we are now starting the preparations for the 3.15.4 LTS release, effective now, both the Quarkus core and Quarkus Platform branches for 3.15 are considered frozen. This is to give a buffer for platform members to do their compatibility testing. The general process is explained here: https://github.com/quarkusio/quarkus/wiki/3.15-LTS-Release-Planning

The current schedule for 3.15.4 LTS is the following:

Date       Action
Feb 10   Backport meetings begin
Mar 4     Upstream branches freeze (Platform can begin compatibility testing)
Mar 11   Upstream core release
Mar 18        Upstream platform release

Let us know if you have any questions or comments.
Thanks
Jan

James Netherton

unread,
Mar 4, 2025, 10:25:40 AMMar 4
to Jan Martiška, quarkus-platfo...@googlegroups.com
How 'frozen' is the platform branch at this point?

There's a new Camel 4.8.4 patch release out today and I was considering doing a Camel Quarkus 3.15.3 release.

Could I get that merged in the platform for 3.15.4 or not?

--
James

--
You received this message because you are subscribed to the Google Groups "Quarkus Platform Coordination" group.
To unsubscribe from this group and stop receiving emails from it, send an email to quarkus-platform-coo...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/quarkus-platform-coordination/CAD8__OEiFyG0my01NQeGL0tHDkVZKOde9xfqQeJGpk4cD71A9Q%40mail.gmail.com.

Jan Martiška

unread,
Mar 4, 2025, 11:08:52 AMMar 4
to James Netherton, quarkus-platfo...@googlegroups.com
That would be against the process. The freeze date was posted on the release planning page for a long time.
Is that necessary to fix a compatibility problem? If not, we should postpone it to 3.15.5.

James Netherton

unread,
Mar 5, 2025, 2:07:38 AMMar 5
to Jan Martiška, quarkus-platfo...@googlegroups.com
It's not addressing any compatibility issues. It's just general fixes & improvements from the Camel 4.8.x LTS stream. There's also an otel fix in CQ.

If we have to wait for 3.15.5, then that's fair enough.
Reply all
Reply to author
Forward
0 new messages