From ca8ac86a6012ac85db65c9ad3321cd99f270df37 Mon Sep 17 00:00:00 2001
From: Clement Escoffier This working group uses a different board: Let's define a format for the files containing the config model we will include in the jars for IDE consumption. See https://github.com/quarkusio/quarkus/discussions/42671 for more details. Point of contact: @gsmet (Zulip: @_Guillaume Smet ) The goal of this focus group is to continue integrating the TLS registry and improve Quarkus integration with certificate providers (Let's Encrypt, Cert-Manager). In addition, we would like to provide a frictionless local experience around TLS (i.e., without the infamous untrusted certificate screen). Point of contact: @cescoffier (@Clement Escoffier on Zulip) When Quarkus has an active working governance model in place and all major work items around setting up Quarkus at CommonHaus are completed - after that, its expected things will just be iteratively improved, and the dedicated working group will not be needed (others might start to continue more specific efforts). The majority of the work must be done before the end of December 2024. The latest deadline for CommonHaus is April 2025, when the bootstrap period of CommonHaus ends. This working group uses a different board: A final benefit is a reduction in the internal complexity of our code. Hopping between classloaders during test execution takes a lot of work, and adds a lot of code! It also is brittle in places. For example, because the hop between classloaders relies on serialization in some cases, it's becoming harder to do as the JVM tightens up security restrictions. We used to rely on xstream, but that stopped working in Java 17. In https://github.com/quarkusio/quarkus/pull/40601, @dmlloyd moved us to use the JBoss Serializer, which works better, but might still be affected by future restrictions on class access. The goal of this working group is to allow test classes to fully participate in the 'quarkification' of classes. The mechanism for this is probably just to load the test classes with the classloader we intend to run them with, so that JUnit sees the 'correct' version of the class. Let's define a format for the files containing the config model we will include in the jars for IDE consumption. See https://github.com/quarkusio/quarkus/discussions/42671 for more details. Point of contact: @gsmet (Zulip: @_Guillaume Smet ) This effort is now tracked using a "Working Group" project: https://github.com/orgs/quarkiverse/projects/6 This is a great opportunity to participate in fun effort and be involved with the Quarkus community, if anyone is interested in being a part of this, please reach out to me 🚀
+
+ status: on track
+ completed: false
+ last-activity: 2024-10-01
+ last-update: |
+ 3.15 has been cut.
+ The 3.15.x is the new LTS, starting with 3.15.1
+ - title: "Quarkus Config and IDEs"
+ board-url: "https://github.com/orgs/quarkusio/projects/32"
+ short-description: Let's define a format for the files containing the config model we will include in the jars for IDE consumption.
+ readme: |
+ under discussion
column contains the issues we would like to have in the next LTS but are still under consideration.out of scope
column contains the issues under discussion' that won't be included. The reason can be time or technical...in progress
means that the work has started and should be completed before the TLS cut datedone
column means that the issues have been completed
-
- status: on track
- last-activity: 2024-09-29
- last-update: |
- 3.15 has been cut.
- The 3.15.x is the new LTS, starting with 3.15.1
- title: "Test classloading"
board-url: "https://github.com/orgs/quarkusio/projects/30"
short-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.
@@ -74,20 +87,12 @@ working-groups:
under discussion
column contains the issues we would like to have in the next LTS but are still under consideration.out of scope
column contains the issues under discussion' that won't be included. The reason can be time or technical...in progress
means that the work has started and should be completed before the TLS cut datedone
column means that the issues have been completed
Point of contact: @iocanel (Ioannis Canellos
on Zulip)
Recently, we delivered a new approach to dealing with WebSocket (both for the server and client). This was the first step. There are still a few areas to improve, such as documentation, security, observability, and testability. The goal of this focus group is to track these efforts.
Point of contact: @mkouba (@Martin Kouba on Zulip)
status: on track + completed: false last-activity: 2024-09-05 last-update: | The last outstanding issue is OTel integration. @michalvavrik is working on a [pull request](https://github.com/quarkusio/quarkus/pull/41956). I will meet with Michal and Bruno in the coming weeks. The PR is quite massive and we need to review it carefully. diff --git a/_includes/working-group-band.html b/_includes/working-group-band.html index ef6bc686264..da17bf2af2a 100644 --- a/_includes/working-group-band.html +++ b/_includes/working-group-band.html @@ -9,6 +9,7 @@ {% for item in site.data.wg.working-groups %} + {% unless item.completed %}{{ item.title }}
@@ -22,6 +23,24 @@ View the {{ item.title }} Board+ These working groups have completed their work and are no longer active: +
+