Working Groups

Driving the future of Quarkus.

A working group is a small team of contributors collaborating on a specific topic or initiative within the Quarkus ecosystem. Each group drives progress in a focused area, such as new features, tools, or long-term improvements.

Joining a working group is a great way to get involved and help shape the future of Quarkus. If you're interested in participating, check the group's board or contact its point of contact.

You can also propose a new working group by opening a design discussion using the working group proposal template.

Active working groups

Quarkus Data

Status: on track

Description: The primary objective of this working group is to develop the next version of Panache, now known as Quarkus Data.

Last Activity: 2026-11-04

Point of Contact: @FroMage (@Stephane Epardaud on Zulip)

Graceful Shutdown

Status: on track

Description: Make Quarkus shutdown truly graceful by providing two complementary capabilities: (1) a mechanism for extensions to block incoming traffic and drain in-flight work to reach a quiescent state, integrated with readiness health checks, and (2) a well-ordered, phased shutdown API that gives extension de

Last Activity: 2026-11-03

Quarkus 4

Status: on track

Description: The Quarkus 4 working group aims to coordinate and track all Quarkus 4-related development in a long-running effort.

Last Activity: 2026-11-03

Observability.Next

Status: on track

Description: Observability.Next is a strategic initiative to modernize the observability stack within the Quarkus framework, aiming to streamline and enhance its ability to monitor and manage distributed systems.

Last Activity: 2026-11-03

Point of Contact: @brunobat

Dev Star

Status: on track

Description: Decompose and modernize the Quarkus developer tooling runtime (Dev UI, Dev MCP, Dev Shell, Dev Assistant) so that each component can operate independently, without requiring the full `vertx-http` web stack. This enables AI-powered developer assistance (via MCP) and terminal-based tooling (Dev Shell)

Last Activity: 2026-11-02

Point of Contact: @phillip-kruger

Modularity (JPMS) and JLink

Status: on track

Description: Make Quarkus applications fully modular using JPMS (Java Platform Module System) and enable jlink as a first-class packaging strategy, producing smaller, faster, self-contained application images, with the long-term goal of making modular packaging the default and phasing out the legacy fast-jar lay

Last Activity: 2026-10-30

Point of Contact: @dmlloyd

Quarkus AI Coordination

Status: on track

Description: The main objective of this working group is to revamp the Quarkus AI message and to coordinate work for Quarkus AI during the 2026/27 timeframe.

Last Activity: 2026-10-27

Point of Contact: @patriot1burke

Dev Services Lifecycle

Status: on track

Description: This working group will define and implement a consistent and configurable lifecycle model for Dev Services. It will shift the startup to the correct phase, enable optional reuse across dev and test modes, and clarify teardown and sharing behavior. The goal is to improve the developer experience.

Last Activity: 2026-10-26

Point of Contact: @holly-cummins (@Holly Cummins on Zulip), @ozangunalp (@Ozan Günalp on Zulip )

Java 25 support

Status: on track

Description: The objective of this working group is to enable Quarkus applications to run cleanly across dev/test/production modes on Java 25, with no requirement to adopt Java 25 as a baseline.

Last Activity: 2026-10-26

Point of Contact: @Sanne (@Sanne on Zulip) and @gsmet (@_Guillaume Smet on Zulip)

Unified Saga implementation

Status: on track

Description: The main objective of this working group is to unify Quarkus's story about Saga-based transactions.

Last Activity: 2026-10-26

Point of Contact: @xstefank (@Martin Stefanko|448453 on Zulip)

AOT Support

Status: on track

Description: The main objective of this working group is to consolidate, enhance, and modernize Quarkus's Ahead-of-Time (AOT) and runtime efficiency (in JVM mode) capabilities. We aim to leverage OpenJDK's Project Leyden, IBM Semeru's advanced features, and JLink to provide a unified, "native-like" startup exper

Last Activity: 2026-08-31

Point of Contact: Guillaume Smet (@gmset) / Georgios Andrianakis (@geoand)

Staled or at risk working groups

These working groups either lack recent activity (i.e., have gone stale), are approaching a time-sensitive deadline, or are facing a technical blocker.

Test classloading

Status: staled

Description: The goal of this working group is to rewrite Quarkus's test classloading, so that tests are run in the same classloader as the application under tests, and Quarkus extensions can do "Quarkus-y" manipulations of test classes.

Last Activity: 2026-10-28

Point of Contact: @holly-cummins (@Holly Cummins on Zulip)

Unified Event Bus

Status: staled

Description: Design and implement a new Quarkus-native event API that is type-safe, supports multiple messaging patterns (pub/sub, point-to-point, request-response), automatically propagates context, and works without a Vert.x (HTTP) dependency, providing a unified programming model for decoupled component inter

Last Activity: 2026-09-15

Point of Contact: @mkouba, @ozangunalp

Spring-Style Testing

Status: staled

Description: Enable Spring developers to migrate to Quarkus with minimal friction by exploring and providing compatibility layers for the most common Spring testing patterns. So they don’t need to rewrite their existing tests.

Last Activity: 2026-07-20

Point of Contact: @edeandrea, @aureamunoz , @mkouba

Binary Reproducibility

Status: staled

Description: Ensure that Quarkus application builds are binary reproducible. That is, building the same source with the same toolchain produces bit-for-bit identical output.

Last Activity: 2026-07-10

Point of Contact: @reaver585, @gsmet

LTS versions

Quarkus LTS versions are managed as long-running working group to track releases and issues selection.

Quarkus 3.33 LTS

Status: paused

Description: This working group aims to track the effort around the Quarkus 3.33 LTS version.

Quarkus 3.27 LTS

Status: on track

Description: This working group aims to track the effort around the Quarkus 3.27 LTS version.

Branch

Quarkus 3.20 LTS

Status: on track

Description: This working group aims to track the effort around the Quarkus 3.20 LTS version.

Paused working groups

These working groups have been paused (lack of bandwidth). If you are interested, feel free to reach out!

Quarkus Config and IDEs

Status: paused

Description: Let's define a format for the files containing the config model we will include in the jars for IDE consumption.

Last Activity: 2026-10-26

Quarkus Terminal

Status: paused

Description: The main objective of this working group is to establish a cohesive foundation for terminal-based experiences in Quarkus. Spanning console I/O, TUIs, CLI parsing, and startup/lifecycle integration. Enable Quarkus itself and applications built on it to have a consistent, lightweight stack to build.

Last Activity: 2026-06-15

Point of Contact: @maxandersen

Quarkus 3.33 LTS

Status: paused

Description: This working group aims to track the effort around the Quarkus 3.33 LTS version.

Last Activity: 2026-06-11

Docker file generation

Status: paused

Description: A working group focusing on the generation of Dockerfile / ContainerFile

Last Activity: 2024-10-31

Completed working groups

These working groups have completed their work and are no longer active:

OIDC improvements

Description: The goal of this working group is to improve quarkus-oidc by: implementing crucial new security features, continuing with improving the way OIDC requests can be intercepted, prioritizing some other open issues, such as using JWT bearer client authentication to complete the authorization code flow

Completed on: 2026-03-23

View the OIDC improvements Board

Gizmo 2

Description: Gizmo 2 related tasks

Completed on: 2025-11-03

Deliverable: Blog

View the Gizmo 2 Board

Agentic Foundation and LangChain4j Next

Description: This working group will explore and define the foundation of the next generation of AI-Infused and Agentic applications built with LangChain4j and Quarkus LangChain4j. The group will investigate core changes to the current programming model, improve dev exp, build stronger interoperability.

Completed on: 2026-09-11

View the Agentic Foundation and LangChain4j Next Board

Convert quarkus.io to Roq

Description: The main objective of this working group is to convert our Jekyll-based website to one built on Roq. A side-effect may be a more generalised set of tools and docs for others to use to convert their sites.

Completed on:

View the Convert quarkus.io to Roq Board

Quarkus 3.15 LTS

Description: This WG focuses on defining the issues we would like to have in the next-to-be LTS (Quarkus 3.14/3.15)

Completed on: 2025-11-03

View the Quarkus 3.15 LTS Board

Roq :: Quarkus SSG

Description: Allow Static Site Generation with Quarkus.

Completed on: 2024-11-18

Deliverable: Quarkus Insight

View the Roq :: Quarkus SSG Board

Offering Metadata and Tooling Integration

Description: Track and coordinate the introduction of offering-level support metadata in Quarkus platform descriptors and its integration into developer tools (e.g., code.quarkus.io, CLI).

Completed on: 2025-11-03

View the Offering Metadata and Tooling Integration Board

Chappie

Description: The main objective of this working group is to allow AI features in Quarkus Dev Mode (Dev UI and CLI)

Completed on: 2026-03-23

Deliverable: Quarkus Dev Assistant

View the Chappie Board

Quarkus to the CommonHaus Foundation

Description: Work needed around moving Quarkus to foundation and streamline open governance.

Completed on: 2026-03-23

View the Quarkus to the CommonHaus Foundation Board

WebSocket Next

Description: WebSocket-Next related tasks

Completed on: 2024-12-16

Deliverable: Quarkus Insight

View the WebSocket Next Board

Enhanced TLS support

Description: Track the progress around the new TLS configuration centralization and new features (like Let's Encrypt, Cert-Manager, and local experience...)

Completed on: 2024-09-29

Deliverable: Quarkus Insight

View the Enhanced TLS support Board