Skip to content

Commit 9c782bd

Browse files
actions-useractions-user
committed
Sync working groups
1 parent d896b1d commit 9c782bd

File tree

1 file changed

+113
-113
lines changed

1 file changed

+113
-113
lines changed

‎_data/wg.yaml‎

Lines changed: 113 additions & 113 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,117 @@
11
---
22
working-groups:
3+
- title: "Java 25 support"
4+
board-url: "https://github.com/orgs/quarkusio/projects/59"
5+
short-description: |
6+
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.
7+
readme: |
8+
<h3>Objective</h3>
9+
<p>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.</p>
10+
<h3>The Problem</h3>
11+
<p>Java 25 brings new features and platform-level changes (e.g., new JEPs, VM flags, performance tweaks) that may trigger warnings, break behavior, or degrade Quarkus experiences. Dependencies or extensions may also face compatibility challenges. A coordinated effort is needed to identify, fix, document, and optionally leverage these changes.</p>
12+
<h3>The Solution</h3>
13+
<p>The working group will:</p>
14+
<ul>
15+
<li>Attempt to run representative Quarkus applications under Java 25 in dev, test, and production modes.</li>
16+
<li>Catalog issues, warnings, or incompatibilities in a Wiki or issue tracker.</li>
17+
<li>Propose and implement fixes or mitigations (or document workarounds).</li>
18+
<li>Optionally explore beneficial Java 25 features (e.g., Scoped Values, Flexible Constructor Bodies), without requiring their use.</li>
19+
<li>Identify and remediate or flag problematic Quarkus extensions.
20+
⠀</li>
21+
</ul>
22+
<h3>Definition of Done</h3>
23+
<ul>
24+
<li>Publish a wiki page detailing issues and resolutions.</li>
25+
<li>Ensure Quarkus core and its ecosystem can operate cleanly under Java 25 in all modes.</li>
26+
<li>Integrate any selected Java 25 features in an optional, non-breaking manner.</li>
27+
<li>Document or fix problematic extensions, offering guidance where needed.</li>
28+
<li>Communicate results via a blog post or quarkus-dev announcement.
29+
⠀</li>
30+
</ul>
31+
<h3>Scope of Work</h3>
32+
<p><strong>In scope:</strong></p>
33+
<ul>
34+
<li>Running and diagnosing Quarkus on Java 25.</li>
35+
<li>Fixing issues in Quarkus core repository and extensions.</li>
36+
<li>Exploring select Java 25 enhancements.</li>
37+
</ul>
38+
<p>⠀
39+
<strong>Out of scope:</strong></p>
40+
<ul>
41+
<li>Mandating Java 25 as the minimum supported runtime.</li>
42+
</ul>
43+
<p>⠀</p>
44+
<h3>Organizing the Work</h3>
45+
<ol>
46+
<li><strong>Communication &amp; Transparency:</strong>
47+
<ul>
48+
<li>Use GitHub discussion, project board, and issues.</li>
49+
<li>Coordinate via Quarkus Zulip and GitHub.</li>
50+
</ul>
51+
</li>
52+
<li><strong>Timeline &amp; Milestones:</strong>
53+
<ul>
54+
<li><strong>Exploration Phase:</strong> Run tests on Java 25 Candidate Release, document findings before GA (target: <em>before September 16, 2025</em>), so we can guide our users as soon as Java 25 reaches GA.</li>
55+
</ul>
56+
</li>
57+
</ol>
58+
<hr />
59+
<ul>
60+
<li>Point of contact: @Sanne (@<strong>Sanne</strong> on Zulip) and @gsmet (@_<strong>Guillaume Smet</strong> on Zulip)</li>
61+
<li>Proposal: https://github.com/quarkusio/quarkus/discussions/49696</li>
62+
<li>Discussion: <a href="https://quarkusio.zulipchat.com/#narrow/channel/187038-dev/topic/WG.20-.20Java.2025.20chat">Zulip</a></li>
63+
</ul>
64+
status: on track
65+
lts: false
66+
completed: false
67+
last-activity: 2025-09-09
68+
last-update-date: 2025-08-27
69+
last-update: |
70+
Working group started.
71+
point-of-contact: "@Sanne (@<strong>Sanne</strong> on Zulip) and @gsmet (@_<strong>Guillaume Smet</strong> on Zulip)"
72+
proposal: https://github.com/quarkusio/quarkus/discussions/49696
73+
discussion: https://quarkusio.zulipchat.com/#narrow/channel/187038-dev/topic/WG.20-.20Java.2025.20chat
74+
- title: "Quarkus 4"
75+
board-url: "https://github.com/orgs/quarkusio/projects/51"
76+
short-description: |
77+
The Quarkus 4 working group aims to coordinate and track all Quarkus 4-related development in a long-running effort.
78+
readme: |
79+
<h2>Objective</h2>
80+
<p>This long‑running working group is dedicated to tracking development and ensuring a smooth rollout for Quarkus 4. It will serve as the central coordination point for feature tracking, release hygiene, migration guidance, and community alignment related to Quarkus 4.</p>
81+
<h2>The Problem</h2>
82+
<p>Quarkus 4 introduces significant shifts, including new Java 25 flags, architectural refinements, deprecations, and ecosystem changes. Without a focused group, efforts become fragmented, and downstream consumers (extensions, integrations, platform partners) may struggle to stay aligned.</p>
83+
<h2>Proposed Solution</h2>
84+
<p>Establish a designated WG to:</p>
85+
<ul>
86+
<li>Track all Quarkus 4‑related issues and PRs (using label triage/quarkus-4)</li>
87+
<li>Maintain a GitHub project board for feature status, blockers, and timelines</li>
88+
<li>Coordinate across teams (core, extensions, platform, tooling)</li>
89+
<li>Surface migration considerations and flag impacts (e.g. new --add-opens needs, optimized defaults) - useful to create the migration guide and rules</li>
90+
<li>Publish ADRs, migration guides, and summary docs</li>
91+
</ul>
92+
<h2>Definition of Done</h2>
93+
<p>This WG will be considered complete when:</p>
94+
<ul>
95+
<li>Quarkus 4 GA is released (including the platform)</li>
96+
<li>All major features are merged and tested</li>
97+
<li>Migration documentation is publicly available</li>
98+
</ul>
99+
<h2>Organizing the Work</h2>
100+
<p>Coordination via:</p>
101+
<ul>
102+
<li>GitHub Discussions: use design‑discussions category</li>
103+
<li>Issues/PRs: label with <code>triage/quarkus-4</code></li>
104+
<li>Project board to track status</li>
105+
</ul>
106+
<h2>Expected Timeline:</h2>
107+
<p>This is a long-running WG, starting now and wrapping up post‑GA (~late Q2 2026). We’ll mark it as “done” upon the public release of Quarkus 4 GA.</p>
108+
status: on track
109+
lts: false
110+
completed: false
111+
last-activity: 2025-09-09
112+
last-update-date: 2025-09-08
113+
last-update: |
114+
We identified several improvements we want to make for Quarkus 4, typically related to Vert.x 5/ Netty 4.2 (to support HTTP/3, gRPC transcoding, etc.).
3115
- title: "Observability.Next"
4116
board-url: "https://github.com/orgs/quarkusio/projects/42"
5117
short-description: |
@@ -69,85 +181,14 @@ working-groups:
69181
status: on track
70182
lts: false
71183
completed: false
72-
last-activity: 2025-09-08
184+
last-activity: 2025-09-09
73185
last-update-date: 2025-09-08
74186
last-update: |
75187
In the last month, the WG - Observability.Next focused on improving the observability stack within the Quarkus framework. The group successfully closed several issues, addressing duplicated OpenTelemetry metrics messages and resolving test failures related to constructor injection in @GrpcService-annotated classes. Additionally, they worked on enhancing documentation regarding the differences in semantic conventions between Micrometer and OpenTelemetry. Notably, a new documentation issue was opened to further refine the precision of this section, reflecting ongoing efforts to clarify and improve resources for users.
76188
77189
(This status update was automatically generated using AI.)
78190
point-of-contact: "@brunobat"
79191
proposal: https://github.com/quarkusio/quarkus/discussions/44423
80-
- title: "Java 25 support"
81-
board-url: "https://github.com/orgs/quarkusio/projects/59"
82-
short-description: |
83-
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.
84-
readme: |
85-
<h3>Objective</h3>
86-
<p>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.</p>
87-
<h3>The Problem</h3>
88-
<p>Java 25 brings new features and platform-level changes (e.g., new JEPs, VM flags, performance tweaks) that may trigger warnings, break behavior, or degrade Quarkus experiences. Dependencies or extensions may also face compatibility challenges. A coordinated effort is needed to identify, fix, document, and optionally leverage these changes.</p>
89-
<h3>The Solution</h3>
90-
<p>The working group will:</p>
91-
<ul>
92-
<li>Attempt to run representative Quarkus applications under Java 25 in dev, test, and production modes.</li>
93-
<li>Catalog issues, warnings, or incompatibilities in a Wiki or issue tracker.</li>
94-
<li>Propose and implement fixes or mitigations (or document workarounds).</li>
95-
<li>Optionally explore beneficial Java 25 features (e.g., Scoped Values, Flexible Constructor Bodies), without requiring their use.</li>
96-
<li>Identify and remediate or flag problematic Quarkus extensions.
97-
⠀</li>
98-
</ul>
99-
<h3>Definition of Done</h3>
100-
<ul>
101-
<li>Publish a wiki page detailing issues and resolutions.</li>
102-
<li>Ensure Quarkus core and its ecosystem can operate cleanly under Java 25 in all modes.</li>
103-
<li>Integrate any selected Java 25 features in an optional, non-breaking manner.</li>
104-
<li>Document or fix problematic extensions, offering guidance where needed.</li>
105-
<li>Communicate results via a blog post or quarkus-dev announcement.
106-
⠀</li>
107-
</ul>
108-
<h3>Scope of Work</h3>
109-
<p><strong>In scope:</strong></p>
110-
<ul>
111-
<li>Running and diagnosing Quarkus on Java 25.</li>
112-
<li>Fixing issues in Quarkus core repository and extensions.</li>
113-
<li>Exploring select Java 25 enhancements.</li>
114-
</ul>
115-
<p>⠀
116-
<strong>Out of scope:</strong></p>
117-
<ul>
118-
<li>Mandating Java 25 as the minimum supported runtime.</li>
119-
</ul>
120-
<p>⠀</p>
121-
<h3>Organizing the Work</h3>
122-
<ol>
123-
<li><strong>Communication &amp; Transparency:</strong>
124-
<ul>
125-
<li>Use GitHub discussion, project board, and issues.</li>
126-
<li>Coordinate via Quarkus Zulip and GitHub.</li>
127-
</ul>
128-
</li>
129-
<li><strong>Timeline &amp; Milestones:</strong>
130-
<ul>
131-
<li><strong>Exploration Phase:</strong> Run tests on Java 25 Candidate Release, document findings before GA (target: <em>before September 16, 2025</em>), so we can guide our users as soon as Java 25 reaches GA.</li>
132-
</ul>
133-
</li>
134-
</ol>
135-
<hr />
136-
<ul>
137-
<li>Point of contact: @Sanne (@<strong>Sanne</strong> on Zulip) and @gsmet (@_<strong>Guillaume Smet</strong> on Zulip)</li>
138-
<li>Proposal: https://github.com/quarkusio/quarkus/discussions/49696</li>
139-
<li>Discussion: <a href="https://quarkusio.zulipchat.com/#narrow/channel/187038-dev/topic/WG.20-.20Java.2025.20chat">Zulip</a></li>
140-
</ul>
141-
status: on track
142-
lts: false
143-
completed: false
144-
last-activity: 2025-09-08
145-
last-update-date: 2025-08-27
146-
last-update: |
147-
Working group started.
148-
point-of-contact: "@Sanne (@<strong>Sanne</strong> on Zulip) and @gsmet (@_<strong>Guillaume Smet</strong> on Zulip)"
149-
proposal: https://github.com/quarkusio/quarkus/discussions/49696
150-
discussion: https://quarkusio.zulipchat.com/#narrow/channel/187038-dev/topic/WG.20-.20Java.2025.20chat
151192
- title: "Offering Metadata and Tooling Integration"
152193
board-url: "https://github.com/orgs/quarkusio/projects/52"
153194
short-description: |
@@ -238,47 +279,6 @@ working-groups:
238279
In the last month, the WG - Quarkus to the CommonHaus Foundation successfully closed an issue related to setting up the recommended files necessary for the transition to the foundation. Additionally, a new issue was opened to enable a Sponsor button in the Quarkiverse, indicating ongoing efforts to enhance community engagement and streamline governance as Quarkus moves to CommonHaus Foundation.
239280
240281
(This status update was automatically generated using AI.)
241-
- title: "Quarkus 4"
242-
board-url: "https://github.com/orgs/quarkusio/projects/51"
243-
short-description: |
244-
The Quarkus 4 working group aims to coordinate and track all Quarkus 4-related development in a long-running effort.
245-
readme: |
246-
<h2>Objective</h2>
247-
<p>This long‑running working group is dedicated to tracking development and ensuring a smooth rollout for Quarkus 4. It will serve as the central coordination point for feature tracking, release hygiene, migration guidance, and community alignment related to Quarkus 4.</p>
248-
<h2>The Problem</h2>
249-
<p>Quarkus 4 introduces significant shifts, including new Java 25 flags, architectural refinements, deprecations, and ecosystem changes. Without a focused group, efforts become fragmented, and downstream consumers (extensions, integrations, platform partners) may struggle to stay aligned.</p>
250-
<h2>Proposed Solution</h2>
251-
<p>Establish a designated WG to:</p>
252-
<ul>
253-
<li>Track all Quarkus 4‑related issues and PRs (using label triage/quarkus-4)</li>
254-
<li>Maintain a GitHub project board for feature status, blockers, and timelines</li>
255-
<li>Coordinate across teams (core, extensions, platform, tooling)</li>
256-
<li>Surface migration considerations and flag impacts (e.g. new --add-opens needs, optimized defaults) - useful to create the migration guide and rules</li>
257-
<li>Publish ADRs, migration guides, and summary docs</li>
258-
</ul>
259-
<h2>Definition of Done</h2>
260-
<p>This WG will be considered complete when:</p>
261-
<ul>
262-
<li>Quarkus 4 GA is released (including the platform)</li>
263-
<li>All major features are merged and tested</li>
264-
<li>Migration documentation is publicly available</li>
265-
</ul>
266-
<h2>Organizing the Work</h2>
267-
<p>Coordination via:</p>
268-
<ul>
269-
<li>GitHub Discussions: use design‑discussions category</li>
270-
<li>Issues/PRs: label with <code>triage/quarkus-4</code></li>
271-
<li>Project board to track status</li>
272-
</ul>
273-
<h2>Expected Timeline:</h2>
274-
<p>This is a long-running WG, starting now and wrapping up post‑GA (~late Q2 2026). We’ll mark it as “done” upon the public release of Quarkus 4 GA.</p>
275-
status: on track
276-
lts: false
277-
completed: false
278-
last-activity: 2025-09-08
279-
last-update-date: 2025-09-08
280-
last-update: |
281-
We identified several improvements we want to make for Quarkus 4, typically related to Vert.x 5/ Netty 4.2 (to support HTTP/3, gRPC transcoding, etc.).
282282
- title: "Gizmo 2"
283283
board-url: "https://github.com/orgs/quarkusio/projects/43"
284284
short-description: |

0 commit comments

Comments
 (0)