Repository navigation
Working Group Activity (September 2026) #57006
cescoffier
started this conversation in
Design Discussions
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Working Group activities from 2026-08-29 to 2026-09-28
New working groups
These working groups were recently created.
Check them out!
Completed working groups
These working groups are now completed.
Latest updates
🟢 WG - Quarkus 4
The working group is on track. Some noticeable updates:
🟢 WG - Quarkus Data
The Quarkus Data group wrapped up a couple of items this month. They ensured Panache 2 prevents opening managed and stateless sessions simultaneously, and resolved a Panache Next projection failure involving Kotlin's value class.
(This status update was automatically generated using AI.)
🟢 WG - Observability.Next
The Observability.Next group completed substantial work, marking OpenTelemetry Metrics and Logs as stable and enabling them by default. We also switched the default OTel protocol to
http/protobufand added full gRPC server metrics support. Efforts are now tracking fixes for OTLP exporter shutdown, context propagation, and clarifying documentation.(This status update was automatically generated using AI.)
🟢 WG - Dev Star
The working group is collecting missing features and issues, but the initial scope is now complete.
🟢 WG - Java 25 support
Now that Quarkus supports Java 25, the few remaining issues are mostly about polishing. There are no more blockers.
We're now tracking an effort to eliminate the FFM downcall warning in dev-mode.
(This status update was automatically generated using AI.)
🟢 WG - Modularity (JPMS) and JLink
The Modularity and JLink group resolved two issues this week. They tackled the problem of
io.quarkus.oidc.client.filterbeing split across multiple modules. The team also addressed the missing ability to read the application name from configuration.(This status update was automatically generated using AI.)
🟢 WG - Dev Services Lifecycle
The Dev Services Lifecycle group addressed dependencies for the devservices runtime module. They resolved the problem of dev services containers not reusing across tests when profiles were set and bolstered test coverage, especially for container identity tracking. Further work is now open to improve lifecycle test coverage and specifically address container reuse/replacement with profile changes.
(This status update was automatically generated using AI.)
🟢 WG - Unified Event Bus
The Unified Event Bus group re-opened the task to document Signals. This work involves comparing its approach to CDI events and the Vert.x EventBus.
The working group is approaching completion, with only 3 more features to implement.
(This status update was automatically generated using AI.)
🟢 WG - Quarkus AI Coordination
WG started
🟢 WG - Unified Saga implementation
Work continued on OpenTelemetry trace context propagation for Signals; the original issue was closed and then reopened. We also started tracking an item to collect metrics covering messages, errors, and bytes transferred.
(This status update was automatically generated using AI.)
🟢 WG - AOT Support
The AOT Support WG wrapped up several key items. We handled AOT file management and integrated Semeru's AOT features into our configuration. Measurement work also concluded, covering RSS usage and warmup when using AOT.
(This status update was automatically generated using AI.)
🟢 WG - Test classloading
The Test classloading group addressed a specific issue this week. They resolved the problem where database dev services weren't reused when unit tests used a
@QuarkusTestResourceannotation, particularly in Quarkus 3.22.(This status update was automatically generated using AI.)
🟢 WG - Graceful Shutdown
The Graceful Shutdown group focused on tracing shutdown sequences this week, implementing JFR events for that purpose.
In addition to this, @ozangunalp has done a lot of work to standardize the graceful shutdown of reactive messaging connectors (and other components).
(This status update was automatically generated using AI.)
🟡 WG - Spring-Style Testing
🟢 WG - Binary Reproducibility
All the issues from the initial scope have been addressed. The working group is inventorying what's left and deciding whether to complete it.
Detailed activity
WG - Quarkus 4
Completed items
WG - Observability.Next
New items
QuarkusContextStorage.attach()leaves the OpenTelemetry context in thread-local storage on Vert.x event-loop threadso.quarkus.opentelemetry.runtime.*logs in testsCompleted items
QuarkusContextStorage.attach()leaves the OpenTelemetry context in thread-local storage on Vert.x event-loop threadsWG - Dev Star
New items
Completed items
WG - Quarkus 3.15 LTS
Completed items
WG - Java 25 support
New items
Completed items
queryOnlyoption in reflective registrationsWG - Modularity (JPMS) and JLink
New items
Completed items
WG - Dev Services Lifecycle
Completed items
WG - Convert quarkus.io to Roq
New items
Completed items
WG - Unified Event Bus
Completed items
WG - Quarkus AI Coordination
New items
WG - Unified Saga implementation
New items
Completed items
WG - Roq :: Quarkus SSG
Completed items
WG - AOT Support
Completed items
Completed working groups
All reactions