3.15 LTS Release Planning

Warning

We are experimenting with a new regular release cadence for our next LTS releases.

These dates are for now indicative as we make progress on the experiment and tighten up the process.

Note

Definitions

Date	Action
Backport meetings	Meetings during which we decide which PRs will get backported to the next LTS micro. Platform updates have to be pushed then also.
Upstream branches freeze	We freeze both the Core branch and the Platform branch at this date. After that only compatibility fixes can be pushed, both to the Core branch and the Platform branch
Upstream core release	When we release Quarkus Core. If Platform changes are necessary for compatibility, they can update to this version, release and create a Platform pull request
Upstream platform release	When we release the Platform and announce the new micro.

General process

Backport meetings begin

We send an email to [email protected] (Google Groups) with the schedule. We start the backport meetings with the idea to get everything merged by branches freeze.

We keep an eye on https://status.quarkus.io/ and in particular the [CI] - Quarkus Platform 3.15 + Quarkus 3.15 item.

Also check Platform pull requests.

Upstream branches freeze

From this date, both the Core and Platform branches are frozen.

• Do a final check on the Platform pull requests early morning.
• Send an email to [email protected] (Google Groups) to announce the branch freeze.

If people have issues with what's in the Core branch, they will have to react and we might have to adjust the Core if a big compatibility issue is found (CI on [CI] - Quarkus Platform 3.15 + Quarkus 3.15 should reduce this risk).

Upstream core release

• We release Quarkus Core and only the Core.
• We update the Platform branch with the new Core release
• We send an announcement to [email protected] once done

Warning

Only compatibility fixes should go in after this release as the branches have been frozen earlier.

Upstream platform release

We release the Platform and we announce it.

3.15.3 LTS

Note

The dates for 3.15.3 LTS are very conservative with a lot of buffers. We will adjust to reduce the buffers once we have more feedback about this new process.

Date	Action
Dec 9, 2024	Backport meetings begin
Jan 7, 2025	Upstream branches freeze (Platform can begin compatibility testing)
Jan 14, 2025	Upstream core release
Jan 21, 2025	Upstream platform release

3.15.4 LTS

Warning

These dates are for now indicative as we might change them as the process improves.

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

3.15.5 LTS

Warning

These dates are for now indicative as we might change them as the process improves.

Date	Action
Apr 14	Backport meetings begin
May 6	Upstream branch freeze (Platform can begin compatibility testing)
May 13	Upstream core release
May 20	Upstream platform release