Skip to content

Commit 6821310

Browse files
actions-useractions-user
committed
Sync working groups
1 parent 766b4cd commit 6821310

1 file changed

Lines changed: 128 additions & 128 deletions

File tree

‎_data/wg.yaml‎

Lines changed: 128 additions & 128 deletions
Original file line numberDiff line numberDiff line change
@@ -1,24 +1,121 @@
11
---
22
working-groups:
3-
- title: "OIDC improvements"
4-
board-url: "https://github.com/orgs/quarkusio/projects/46"
3+
- title: "Java 25 support"
4+
board-url: "https://github.com/orgs/quarkusio/projects/59"
55
short-description: |
6-
The goal of this working group is to improve quarkus-oidc by: implementing crucial new security features, continuing with improving the way OIDC requests can be intercepted, prioritizing some other open issues, such as using JWT bearer client authentication to complete the authorization code flow
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.
77
readme: |
8-
<p>The goal of this working group is to improve quarkus-oidc by: implementing crucial new security features, continuing with improving the way OIDC requests can be intercepted, prioritizing some other open issues, such as using JWT bearer client authentication to complete the authorization code flow</p>
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>
914
<ul>
10-
<li>Point of contact: @sberyozkin (@_<strong>Sergey Beryozkin</strong> on Zulip)</li>
11-
<li>Proposal: https://github.com/quarkusio/quarkus/discussions/42116</li>
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>
1221
</ul>
13-
status: complete
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
1465
lts: false
15-
completed: true
66+
completed: false
1667
last-activity: 2026-04-30
17-
last-update-date: 2026-03-23
68+
last-update-date: 2026-03-30
1869
last-update: |
19-
Done! Lots of ODIC features have been shipped by this working group.
20-
point-of-contact: "@sberyozkin (@_<strong>Sergey Beryozkin</strong> on Zulip)"
21-
proposal: https://github.com/quarkusio/quarkus/discussions/42116
70+
We addressed the JIB issue regarding `jvm-additional-arguments` for AOT cache generation and updated the Deploy to Openshift guide for Java 25. Both are now back on the radar for further refinement. Also tracking a new Panache Next projection failure with Kotlin value classes.
71+
72+
(This status update was automatically generated using AI.)
73+
point-of-contact: "@Sanne (@<strong>Sanne</strong> on Zulip) and @gsmet (@_<strong>Guillaume Smet</strong> on Zulip)"
74+
proposal: https://github.com/quarkusio/quarkus/discussions/49696
75+
discussion: https://quarkusio.zulipchat.com/#narrow/channel/187038-dev/topic/WG.20-.20Java.2025.20chat
76+
- title: "Quarkus 4"
77+
board-url: "https://github.com/orgs/quarkusio/projects/51"
78+
short-description: |
79+
The Quarkus 4 working group aims to coordinate and track all Quarkus 4-related development in a long-running effort.
80+
readme: |
81+
<h2>Objective</h2>
82+
<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>
83+
<h2>The Problem</h2>
84+
<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>
85+
<h2>Proposed Solution</h2>
86+
<p>Establish a designated WG to:</p>
87+
<ul>
88+
<li>Track all Quarkus 4‑related issues and PRs (using label triage/quarkus-4)</li>
89+
<li>Maintain a GitHub project board for feature status, blockers, and timelines</li>
90+
<li>Coordinate across teams (core, extensions, platform, tooling)</li>
91+
<li>Surface migration considerations and flag impacts (e.g. new --add-opens needs, optimized defaults) - useful to create the migration guide and rules</li>
92+
<li>Publish ADRs, migration guides, and summary docs</li>
93+
</ul>
94+
<h2>Definition of Done</h2>
95+
<p>This WG will be considered complete when:</p>
96+
<ul>
97+
<li>Quarkus 4 GA is released (including the platform)</li>
98+
<li>All major features are merged and tested</li>
99+
<li>Migration documentation is publicly available</li>
100+
</ul>
101+
<h2>Organizing the Work</h2>
102+
<p>Coordination via:</p>
103+
<ul>
104+
<li>GitHub Discussions: use design‑discussions category</li>
105+
<li>Issues/PRs: label with <code>triage/quarkus-4</code></li>
106+
<li>Project board to track status</li>
107+
</ul>
108+
<h2>Expected Timeline:</h2>
109+
<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>
110+
status: on track
111+
lts: false
112+
completed: false
113+
last-activity: 2026-04-30
114+
last-update-date: 2026-03-30
115+
last-update: |
116+
The team closed out significant work on the Vert.x 5 upgrade and migration of its core extension for Quarkus 4. New tasks include updating Vert.x configuration, reworking CI, and addressing Kafka Kerberos authentication in native mode. We're also defining OpenTelemetry trace sampling defaults and looking into extension modularity.
117+
118+
(This status update was automatically generated using AI.)
22119
- title: "Quarkus Data"
23120
board-url: "https://github.com/orgs/quarkusio/projects/50"
24121
short-description: |
@@ -87,6 +184,25 @@ working-groups:
87184
point-of-contact: "@FroMage (@<strong>Stephane Epardaud</strong> on Zulip)"
88185
proposal: https://github.com/quarkusio/quarkus/discussions/48949
89186
discussion: https://quarkusio.zulipchat.com/#narrow/channel/187038-dev/topic/WG.20-.20Panache.2ENext/with/529258261
187+
- title: "OIDC improvements"
188+
board-url: "https://github.com/orgs/quarkusio/projects/46"
189+
short-description: |
190+
The goal of this working group is to improve quarkus-oidc by: implementing crucial new security features, continuing with improving the way OIDC requests can be intercepted, prioritizing some other open issues, such as using JWT bearer client authentication to complete the authorization code flow
191+
readme: |
192+
<p>The goal of this working group is to improve quarkus-oidc by: implementing crucial new security features, continuing with improving the way OIDC requests can be intercepted, prioritizing some other open issues, such as using JWT bearer client authentication to complete the authorization code flow</p>
193+
<ul>
194+
<li>Point of contact: @sberyozkin (@_<strong>Sergey Beryozkin</strong> on Zulip)</li>
195+
<li>Proposal: https://github.com/quarkusio/quarkus/discussions/42116</li>
196+
</ul>
197+
status: complete
198+
lts: false
199+
completed: true
200+
last-activity: 2026-04-30
201+
last-update-date: 2026-03-23
202+
last-update: |
203+
Done! Lots of ODIC features have been shipped by this working group.
204+
point-of-contact: "@sberyozkin (@_<strong>Sergey Beryozkin</strong> on Zulip)"
205+
proposal: https://github.com/quarkusio/quarkus/discussions/42116
90206
- title: "Dev Services Lifecycle"
91207
board-url: "https://github.com/orgs/quarkusio/projects/49"
92208
short-description: |
@@ -114,49 +230,6 @@ working-groups:
114230
point-of-contact: "@holly-cummins (@<strong>Holly Cummins</strong> on Zulip), @ozangunalp (@<strong>Ozan Günalp</strong> on Zulip )"
115231
proposal: https://github.com/quarkusio/quarkus/discussions/47683
116232
discussion: https://quarkusio.zulipchat.com/#narrow/channel/187038-dev
117-
- title: "Quarkus 4"
118-
board-url: "https://github.com/orgs/quarkusio/projects/51"
119-
short-description: |
120-
The Quarkus 4 working group aims to coordinate and track all Quarkus 4-related development in a long-running effort.
121-
readme: |
122-
<h2>Objective</h2>
123-
<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>
124-
<h2>The Problem</h2>
125-
<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>
126-
<h2>Proposed Solution</h2>
127-
<p>Establish a designated WG to:</p>
128-
<ul>
129-
<li>Track all Quarkus 4‑related issues and PRs (using label triage/quarkus-4)</li>
130-
<li>Maintain a GitHub project board for feature status, blockers, and timelines</li>
131-
<li>Coordinate across teams (core, extensions, platform, tooling)</li>
132-
<li>Surface migration considerations and flag impacts (e.g. new --add-opens needs, optimized defaults) - useful to create the migration guide and rules</li>
133-
<li>Publish ADRs, migration guides, and summary docs</li>
134-
</ul>
135-
<h2>Definition of Done</h2>
136-
<p>This WG will be considered complete when:</p>
137-
<ul>
138-
<li>Quarkus 4 GA is released (including the platform)</li>
139-
<li>All major features are merged and tested</li>
140-
<li>Migration documentation is publicly available</li>
141-
</ul>
142-
<h2>Organizing the Work</h2>
143-
<p>Coordination via:</p>
144-
<ul>
145-
<li>GitHub Discussions: use design‑discussions category</li>
146-
<li>Issues/PRs: label with <code>triage/quarkus-4</code></li>
147-
<li>Project board to track status</li>
148-
</ul>
149-
<h2>Expected Timeline:</h2>
150-
<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>
151-
status: on track
152-
lts: false
153-
completed: false
154-
last-activity: 2026-04-29
155-
last-update-date: 2026-03-30
156-
last-update: |
157-
The team closed out significant work on the Vert.x 5 upgrade and migration of its core extension for Quarkus 4. New tasks include updating Vert.x configuration, reworking CI, and addressing Kafka Kerberos authentication in native mode. We're also defining OpenTelemetry trace sampling defaults and looking into extension modularity.
158-
159-
(This status update was automatically generated using AI.)
160233
- title: "Observability.Next"
161234
board-url: "https://github.com/orgs/quarkusio/projects/42"
162235
short-description: |
@@ -878,79 +951,6 @@ working-groups:
878951
point-of-contact: "@phillip-kruger (@<strong>Phillip Krüger</strong> on Zulip)"
879952
proposal: https://github.com/quarkusio/quarkus/discussions/45377
880953
discussion: https://quarkusio.zulipchat.com/#narrow/stream/187038-dev
881-
- title: "Java 25 support"
882-
board-url: "https://github.com/orgs/quarkusio/projects/59"
883-
short-description: |
884-
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.
885-
readme: |
886-
<h3>Objective</h3>
887-
<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>
888-
<h3>The Problem</h3>
889-
<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>
890-
<h3>The Solution</h3>
891-
<p>The working group will:</p>
892-
<ul>
893-
<li>Attempt to run representative Quarkus applications under Java 25 in dev, test, and production modes.</li>
894-
<li>Catalog issues, warnings, or incompatibilities in a Wiki or issue tracker.</li>
895-
<li>Propose and implement fixes or mitigations (or document workarounds).</li>
896-
<li>Optionally explore beneficial Java 25 features (e.g., Scoped Values, Flexible Constructor Bodies), without requiring their use.</li>
897-
<li>Identify and remediate or flag problematic Quarkus extensions.
898-
⠀</li>
899-
</ul>
900-
<h3>Definition of Done</h3>
901-
<ul>
902-
<li>Publish a wiki page detailing issues and resolutions.</li>
903-
<li>Ensure Quarkus core and its ecosystem can operate cleanly under Java 25 in all modes.</li>
904-
<li>Integrate any selected Java 25 features in an optional, non-breaking manner.</li>
905-
<li>Document or fix problematic extensions, offering guidance where needed.</li>
906-
<li>Communicate results via a blog post or quarkus-dev announcement.
907-
⠀</li>
908-
</ul>
909-
<h3>Scope of Work</h3>
910-
<p><strong>In scope:</strong></p>
911-
<ul>
912-
<li>Running and diagnosing Quarkus on Java 25.</li>
913-
<li>Fixing issues in Quarkus core repository and extensions.</li>
914-
<li>Exploring select Java 25 enhancements.</li>
915-
</ul>
916-
<p>⠀
917-
<strong>Out of scope:</strong></p>
918-
<ul>
919-
<li>Mandating Java 25 as the minimum supported runtime.</li>
920-
</ul>
921-
<p>⠀</p>
922-
<h3>Organizing the Work</h3>
923-
<ol>
924-
<li><strong>Communication &amp; Transparency:</strong>
925-
<ul>
926-
<li>Use GitHub discussion, project board, and issues.</li>
927-
<li>Coordinate via Quarkus Zulip and GitHub.</li>
928-
</ul>
929-
</li>
930-
<li><strong>Timeline &amp; Milestones:</strong>
931-
<ul>
932-
<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>
933-
</ul>
934-
</li>
935-
</ol>
936-
<hr />
937-
<ul>
938-
<li>Point of contact: @Sanne (@<strong>Sanne</strong> on Zulip) and @gsmet (@_<strong>Guillaume Smet</strong> on Zulip)</li>
939-
<li>Proposal: https://github.com/quarkusio/quarkus/discussions/49696</li>
940-
<li>Discussion: <a href="https://quarkusio.zulipchat.com/#narrow/channel/187038-dev/topic/WG.20-.20Java.2025.20chat">Zulip</a></li>
941-
</ul>
942-
status: on track
943-
lts: false
944-
completed: false
945-
last-activity: 2026-04-13
946-
last-update-date: 2026-03-30
947-
last-update: |
948-
We addressed the JIB issue regarding `jvm-additional-arguments` for AOT cache generation and updated the Deploy to Openshift guide for Java 25. Both are now back on the radar for further refinement. Also tracking a new Panache Next projection failure with Kotlin value classes.
949-
950-
(This status update was automatically generated using AI.)
951-
point-of-contact: "@Sanne (@<strong>Sanne</strong> on Zulip) and @gsmet (@_<strong>Guillaume Smet</strong> on Zulip)"
952-
proposal: https://github.com/quarkusio/quarkus/discussions/49696
953-
discussion: https://quarkusio.zulipchat.com/#narrow/channel/187038-dev/topic/WG.20-.20Java.2025.20chat
954954
- title: "Modularity (JPMS) and JLink"
955955
board-url: "https://github.com/orgs/quarkusio/projects/76"
956956
short-description: |

0 commit comments

Comments
 (0)