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
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.
LTS versions
Quarkus LTS versions are managed as long-running working group to track releases and issues selection.
Paused working groups
These working groups have been paused (lack of bandwidth). If you are interested, feel free to reach out!
Quarkus 3.33 LTS
Status: paused
Description: This working group aims to track the effort around the Quarkus 3.33 LTS version.
Last Activity: February 26, 2026
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: September 08, 2025
Docker file generation
Status: paused
Description: A working group focusing on the generation of Dockerfile / ContainerFile
Last Activity: October 31, 2024
Completed working groups
These working groups have completed their work and are no longer active:
Quarkus 4
Description: The Quarkus 4 working group aims to coordinate and track all Quarkus 4-related development in a long-running effort.
Completed on: February 23, 2026
Graceful Shutdown
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
Completed on: March 25, 2026
Dev Star
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)
Completed on: March 25, 2026
Chappie
Description: The main objective of this working group is to allow AI features in Quarkus Dev Mode (Dev UI and CLI)
Completed on: March 23, 2026
Deliverable: Quarkus Dev Assistant
Quarkus Data
Description: The primary objective of this working group is to develop the next version of Panache, now known as Quarkus Data.
Completed on: February 23, 2026
Deliverable: Blog Post
Dev Services Lifecycle
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.
Completed on: February 23, 2026
Modularity (JPMS) and JLink
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
Completed on: March 25, 2026
Spring-Style Testing
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.
Completed on: October 27, 2025
Test classloading
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.
Completed on: February 23, 2026
Unified Event Bus
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
Completed on: March 25, 2026
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: March 23, 2026
Quarkus to the CommonHaus Foundation
Description: Work needed around moving Quarkus to foundation and streamline open governance.
Completed on: March 23, 2026
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: November 03, 2025
Unified Saga implementation
Description: The main objective of this working group is to unify Quarkus's story about Saga-based transactions.
Completed on: February 23, 2026
Deliverable: TBD
Java 25 support
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.
Completed on: February 23, 2026
AOT Support
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
Completed on: February 23, 2026
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: February 23, 2026
Observability.Next
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.
Completed on: February 23, 2026
Quarkus 3.33 LTS
Description: This working group aims to track the effort around the Quarkus 3.33 LTS version.
Completed on:
Gizmo 2
Roq :: Quarkus SSG
Description: Allow Static Site Generation with Quarkus.
Completed on: November 18, 2024
Deliverable: Quarkus Insight
Quarkus 3.27 LTS
Description: This working group aims to track the effort around the Quarkus 3.27 LTS version.
Completed on:
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: November 03, 2025
Quarkus Config and IDEs
Description: Let's define a format for the files containing the config model we will include in the jars for IDE consumption.
Completed on: July 22, 2025
Quarkus 3.20 LTS
Description: This working group aims to track the effort around the Quarkus 3.20 LTS version.
Completed on: April 01, 2025
WebSocket Next
Description: WebSocket-Next related tasks
Completed on: December 16, 2024
Deliverable: Quarkus Insight
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: September 29, 2024
Deliverable: Quarkus Insight
Docker file generation
Description: A working group focusing on the generation of Dockerfile / ContainerFile
Completed on: October 28, 2025
