You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This WG focuses on defining the issues we would like to have in the next-to-be LTS (Quarkus 3.14/3.15)
7
-
readme: |
8
-
<p>This working group uses a different board:</p>
9
-
<ul>
10
-
<li>The <code>under discussion</code> column contains the issues we would like to have in the next LTS but are still under consideration.</li>
11
-
<li>The <code>out of scope</code> column contains the issues under discussion' that won't be included. The reason can be time or technical...</li>
12
-
<li>The <code>in progress</code> means that the work has started and should be completed before the TLS cut date</li>
13
-
<li>The <code>done</code> column means that the issues have been completed</li>
14
-
</ul>
15
-
status: on track
16
-
lts: true
17
-
completed: false
18
-
last-activity: 2025-04-30
19
-
last-update-date: 2025-04-01
20
-
last-update: |
21
-
In the last month, the WG - Quarkus 3.15 LTS closed two issues: one regarding the assignment of random ports in the configuration and another updating the Kafka client version to 3.7.2 to address CVE-2024-56128. No new issues were opened, reflecting a commitment to resolving important topics for the upcoming LTS release.
In the last month, the WG - Test classloading successfully closed significant issues related to classloader behavior, including fixing ServiceLoader errors and NullPointerExceptions that impacted test discovery. However, several issues were opened, focusing on recurring ServiceConfigurationErrors and additional classloader-related concerns. The team also initiated communications with the first blog detailing test classloading changes. This ongoing work aims to enhance Quarkus's test environment by ensuring proper classloader interactions and minimizing errors during testing.
@@ -48,6 +29,25 @@ working-groups:
48
29
point-of-contact: "@holly-cummins (@<strong>Holly Cummins</strong> on Zulip)"
This WG focuses on defining the issues we would like to have in the next-to-be LTS (Quarkus 3.14/3.15)
36
+
readme: |
37
+
<p>This working group uses a different board:</p>
38
+
<ul>
39
+
<li>The <code>under discussion</code> column contains the issues we would like to have in the next LTS but are still under consideration.</li>
40
+
<li>The <code>out of scope</code> column contains the issues under discussion' that won't be included. The reason can be time or technical...</li>
41
+
<li>The <code>in progress</code> means that the work has started and should be completed before the TLS cut date</li>
42
+
<li>The <code>done</code> column means that the issues have been completed</li>
43
+
</ul>
44
+
status: on track
45
+
lts: true
46
+
completed: false
47
+
last-activity: 2025-04-30
48
+
last-update-date: 2025-04-01
49
+
last-update: |
50
+
In the last month, the WG - Quarkus 3.15 LTS closed two issues: one regarding the assignment of random ports in the configuration and another updating the Kafka client version to 3.7.2 to address CVE-2024-56128. No new issues were opened, reflecting a commitment to resolving important topics for the upcoming LTS release.
0 commit comments