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
Copy file name to clipboardExpand all lines: _data/wg.yaml
+64-64Lines changed: 64 additions & 64 deletions
Original file line number
Diff line number
Diff line change
@@ -15,7 +15,7 @@ working-groups:
15
15
status: on track
16
16
lts: false
17
17
completed: false
18
-
last-activity: 2025-05-28
18
+
last-activity: 2025-06-03
19
19
last-update-date: 2025-04-28
20
20
last-update: |
21
21
In the past month, the WG - Gizmo 2 successfully closed numerous issues, including improvements in error handling, support for instance field initializers, and updates to annotation handling. Key enhancements were made to Lambda singleton implementations and field check validations. Concurrently, several new issues were opened, still addressing challenges in error messaging, generic type handling, and improvements to operational efficiencies. The group remains focused on optimizing the Gizmo 2 framework while ensuring robust functionality and user experience.
@@ -25,6 +25,46 @@ working-groups:
25
25
point-of-contact: "@mkouba (@<strong>Martin Kouba</strong> on Zulip)"
Work needed around moving Quarkus to foundation and streamline open governance.
32
+
readme: |
33
+
<p>from Discussion at https://github.com/quarkusio/quarkus/discussions/43013</p>
34
+
<p>We started the move of Quarkus to a foundation <a href="https://quarkus.io/blog/quarkus-in-a-foundation/">earlier this year</a> and recently <a href="https://quarkus.io/blog/quarkus-moving-to-commonhaus/">set the direction</a> towards <a href="https://www.commonhaus.org/">CommonHaus</a> and during the summer break the CommonHaus council <a href="https://github.com/commonhaus/foundation/pull/183">approved our request</a> to join.</p>
35
+
<p>Thus, now the real work starts, and it's just fitting we set up a working group for the effort getting Quarkus to CommonHaus foundation.</p>
36
+
<h1>Goal</h1>
37
+
<p>Two parts</p>
38
+
<ul>
39
+
<li>setup Quarkus to have transparent and open governance</li>
40
+
<li>Go through the few but important requirements for a CommonHaus project.</li>
41
+
</ul>
42
+
<h1>Initial work items/questions:</h1>
43
+
<p>Current known list, but not limited to:</p>
44
+
<ul>
45
+
<li>identify design communication channels (i.e. #41973)</li>
46
+
<li>which repositories / code will move</li>
47
+
<li>impact (if any) on quarkiverse projects</li>
48
+
<li>how will trademarks work/change</li>
49
+
<li>identify running services and setup/maintain them (registry.quarkus.io, code.quarkus.io etc.)</li>
50
+
<li>add required metadata/files to the various repositories</li>
51
+
</ul>
52
+
<h1>Tracking</h1>
53
+
<p>We will use the working group board to track publicly all the known relevant work and questions.For the few exception cases where, for legal or personal constraints, the work must happen in private, we will post the outcome and results in public places (like a GitHub discussion of a GitHub issue tracked on the working group board).</p>
54
+
<h1>When will this working group be done?</h1>
55
+
<p>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).</p>
56
+
<p>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.</p>
57
+
status: staled
58
+
lts: false
59
+
completed: false
60
+
last-activity: 2025-06-03
61
+
last-update-date: 2025-02-25
62
+
last-update: |
63
+
Started working on full list of repos and infrastructure that needs clarifying. Can't share it publically yet due to red hat infrastructure details but will soon share.
64
+
65
+
Marking as risk as deadline april 1st is looming and still things to define.
66
+
67
+
There is a Quarkus f2f meeting next week that could clarify/move things forward and start to share more publically as things get moved over from internal IT.
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.
@@ -54,6 +94,25 @@ working-groups:
54
94
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)
101
+
readme: |
102
+
<p>This working group uses a different board:</p>
103
+
<ul>
104
+
<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>
105
+
<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>
106
+
<li>The <code>in progress</code> means that the work has started and should be completed before the TLS cut date</li>
107
+
<li>The <code>done</code> column means that the issues have been completed</li>
108
+
</ul>
109
+
status: on track
110
+
lts: true
111
+
completed: false
112
+
last-activity: 2025-06-03
113
+
last-update-date: 2025-04-01
114
+
last-update: |
115
+
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 past month, the WG - Quarkus 3.20 LTS successfully closed three issues, addressing an exception related to missing Maven classes in the dev-ui for Gradle projects, enhancing the Grafana LGTM dashboards, and determining the appropriate Kafka client version for the 3.20 LTS release. No new issues were opened during this period, indicating focused progress on existing challenges.
This WG focuses on defining the issues we would like to have in the next-to-be LTS (Quarkus 3.14/3.15)
98
-
readme: |
99
-
<p>This working group uses a different board:</p>
100
-
<ul>
101
-
<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>
102
-
<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>
103
-
<li>The <code>in progress</code> means that the work has started and should be completed before the TLS cut date</li>
104
-
<li>The <code>done</code> column means that the issues have been completed</li>
105
-
</ul>
106
-
status: on track
107
-
lts: true
108
-
completed: false
109
-
last-activity: 2025-05-20
110
-
last-update-date: 2025-04-01
111
-
last-update: |
112
-
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.
Work needed around moving Quarkus to foundation and streamline open governance.
414
-
readme: |
415
-
<p>from Discussion at https://github.com/quarkusio/quarkus/discussions/43013</p>
416
-
<p>We started the move of Quarkus to a foundation <a href="https://quarkus.io/blog/quarkus-in-a-foundation/">earlier this year</a> and recently <a href="https://quarkus.io/blog/quarkus-moving-to-commonhaus/">set the direction</a> towards <a href="https://www.commonhaus.org/">CommonHaus</a> and during the summer break the CommonHaus council <a href="https://github.com/commonhaus/foundation/pull/183">approved our request</a> to join.</p>
417
-
<p>Thus, now the real work starts, and it's just fitting we set up a working group for the effort getting Quarkus to CommonHaus foundation.</p>
418
-
<h1>Goal</h1>
419
-
<p>Two parts</p>
420
-
<ul>
421
-
<li>setup Quarkus to have transparent and open governance</li>
422
-
<li>Go through the few but important requirements for a CommonHaus project.</li>
423
-
</ul>
424
-
<h1>Initial work items/questions:</h1>
425
-
<p>Current known list, but not limited to:</p>
426
-
<ul>
427
-
<li>identify design communication channels (i.e. #41973)</li>
428
-
<li>which repositories / code will move</li>
429
-
<li>impact (if any) on quarkiverse projects</li>
430
-
<li>how will trademarks work/change</li>
431
-
<li>identify running services and setup/maintain them (registry.quarkus.io, code.quarkus.io etc.)</li>
432
-
<li>add required metadata/files to the various repositories</li>
433
-
</ul>
434
-
<h1>Tracking</h1>
435
-
<p>We will use the working group board to track publicly all the known relevant work and questions.For the few exception cases where, for legal or personal constraints, the work must happen in private, we will post the outcome and results in public places (like a GitHub discussion of a GitHub issue tracked on the working group board).</p>
436
-
<h1>When will this working group be done?</h1>
437
-
<p>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).</p>
438
-
<p>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.</p>
439
-
status: staled
440
-
lts: false
441
-
completed: false
442
-
last-activity: 2024-10-28
443
-
last-update-date: 2025-02-25
444
-
last-update: |
445
-
Started working on full list of repos and infrastructure that needs clarifying. Can't share it publically yet due to red hat infrastructure details but will soon share.
446
-
447
-
Marking as risk as deadline april 1st is looming and still things to define.
448
-
449
-
There is a Quarkus f2f meeting next week that could clarify/move things forward and start to share more publically as things get moved over from internal IT.
Copy file name to clipboardExpand all lines: _generated-doc/main/config/quarkus-all-config.adoc
+23-2Lines changed: 23 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -74017,7 +74017,7 @@ Enable metrics with OpenTelemetry.
74017
74017
74018
74018
This property is not available in the Open Telemetry SDK. It's Quarkus specific.
74019
74019
74020
-
Support for metrics will be enabled if OpenTelemetry support is enabled and either this value is true, or this value is unset.
74020
+
Support for OpenTelemetry Metrics will be enabled if this value is true. The OpenTelemetry SDK ( `io.quarkus.opentelemetry.runtime.config.build.OTelBuildConfig++#++enabled()` ) is enabled by default and if disabled, OpenTelemetry Metrics will also be disabled.
74021
74021
74022
74022
74023
74023
ifdef::add-copy-button-to-env-var[]
@@ -74063,7 +74063,7 @@ Enable logs with OpenTelemetry.
74063
74063
74064
74064
This property is not available in the Open Telemetry SDK. It's Quarkus specific.
74065
74065
74066
-
Support for logs will be enabled if OpenTelemetry support is enabled and either this value is true, or this value is unset.
74066
+
Support for OpenTelemetry Logs will be enabled if this value is true. The OpenTelemetry SDK ( `io.quarkus.opentelemetry.runtime.config.build.OTelBuildConfig++#++enabled()` ) is enabled by default and if disabled, OpenTelemetry Logs will also be disabled.
This will automatically add the OpenAPI specification document endpoint to the schema. It also adds "openapi" to the list of tags and specify an "operationId"
Copy file name to clipboardExpand all lines: _generated-doc/main/config/quarkus-opentelemetry.adoc
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -138,7 +138,7 @@ Enable metrics with OpenTelemetry.
138
138
139
139
This property is not available in the Open Telemetry SDK. It's Quarkus specific.
140
140
141
-
Support for metrics will be enabled if OpenTelemetry support is enabled and either this value is true, or this value is unset.
141
+
Support for OpenTelemetry Metrics will be enabled if this value is true. The OpenTelemetry SDK ( `io.quarkus.opentelemetry.runtime.config.build.OTelBuildConfig++#++enabled()` ) is enabled by default and if disabled, OpenTelemetry Metrics will also be disabled.
142
142
143
143
144
144
ifdef::add-copy-button-to-env-var[]
@@ -184,7 +184,7 @@ Enable logs with OpenTelemetry.
184
184
185
185
This property is not available in the Open Telemetry SDK. It's Quarkus specific.
186
186
187
-
Support for logs will be enabled if OpenTelemetry support is enabled and either this value is true, or this value is unset.
187
+
Support for OpenTelemetry Logs will be enabled if this value is true. The OpenTelemetry SDK ( `io.quarkus.opentelemetry.runtime.config.build.OTelBuildConfig++#++enabled()` ) is enabled by default and if disabled, OpenTelemetry Logs will also be disabled.
Copy file name to clipboardExpand all lines: _generated-doc/main/config/quarkus-opentelemetry_quarkus.otel.adoc
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -138,7 +138,7 @@ Enable metrics with OpenTelemetry.
138
138
139
139
This property is not available in the Open Telemetry SDK. It's Quarkus specific.
140
140
141
-
Support for metrics will be enabled if OpenTelemetry support is enabled and either this value is true, or this value is unset.
141
+
Support for OpenTelemetry Metrics will be enabled if this value is true. The OpenTelemetry SDK ( `io.quarkus.opentelemetry.runtime.config.build.OTelBuildConfig++#++enabled()` ) is enabled by default and if disabled, OpenTelemetry Metrics will also be disabled.
142
142
143
143
144
144
ifdef::add-copy-button-to-env-var[]
@@ -184,7 +184,7 @@ Enable logs with OpenTelemetry.
184
184
185
185
This property is not available in the Open Telemetry SDK. It's Quarkus specific.
186
186
187
-
Support for logs will be enabled if OpenTelemetry support is enabled and either this value is true, or this value is unset.
187
+
Support for OpenTelemetry Logs will be enabled if this value is true. The OpenTelemetry SDK ( `io.quarkus.opentelemetry.runtime.config.build.OTelBuildConfig++#++enabled()` ) is enabled by default and if disabled, OpenTelemetry Logs will also be disabled.
0 commit comments