Skip to content

Commit d7c1064

Browse files
actions-useractions-user
committed
Sync working groups
1 parent c624f46 commit d7c1064

File tree

1 file changed

+41
-41
lines changed

1 file changed

+41
-41
lines changed

‎_data/wg.yaml‎

Lines changed: 41 additions & 41 deletions
Original file line numberDiff line numberDiff line change
@@ -1,46 +1,5 @@
11
---
22
working-groups:
3-
- title: "Quarkus 4"
4-
board-url: "https://github.com/orgs/quarkusio/projects/51"
5-
short-description: |
6-
The Quarkus 4 working group aims to coordinate and track all Quarkus 4-related development in a long-running effort.
7-
readme: |
8-
<h2>Objective</h2>
9-
<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>
10-
<h2>The Problem</h2>
11-
<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>
12-
<h2>Proposed Solution</h2>
13-
<p>Establish a designated WG to:</p>
14-
<ul>
15-
<li>Track all Quarkus 4‑related issues and PRs (using label triage/quarkus-4)</li>
16-
<li>Maintain a GitHub project board for feature status, blockers, and timelines</li>
17-
<li>Coordinate across teams (core, extensions, platform, tooling)</li>
18-
<li>Surface migration considerations and flag impacts (e.g. new --add-opens needs, optimized defaults) - useful to create the migration guide and rules</li>
19-
<li>Publish ADRs, migration guides, and summary docs</li>
20-
</ul>
21-
<h2>Definition of Done</h2>
22-
<p>This WG will be considered complete when:</p>
23-
<ul>
24-
<li>Quarkus 4 GA is released (including the platform)</li>
25-
<li>All major features are merged and tested</li>
26-
<li>Migration documentation is publicly available</li>
27-
</ul>
28-
<h2>Organizing the Work</h2>
29-
<p>Coordination via:</p>
30-
<ul>
31-
<li>GitHub Discussions: use design‑discussions category</li>
32-
<li>Issues/PRs: label with <code>triage/quarkus-4</code></li>
33-
<li>Project board to track status</li>
34-
</ul>
35-
<h2>Expected Timeline:</h2>
36-
<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>
37-
status: on track
38-
lts: false
39-
completed: false
40-
last-activity: 2025-09-09
41-
last-update-date: 2025-09-08
42-
last-update: |
43-
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.).
443
- title: "Observability.Next"
454
board-url: "https://github.com/orgs/quarkusio/projects/42"
465
short-description: |
@@ -118,6 +77,47 @@ working-groups:
11877
(This status update was automatically generated using AI.)
11978
point-of-contact: "@brunobat"
12079
proposal: https://github.com/quarkusio/quarkus/discussions/44423
80+
- title: "Quarkus 4"
81+
board-url: "https://github.com/orgs/quarkusio/projects/51"
82+
short-description: |
83+
The Quarkus 4 working group aims to coordinate and track all Quarkus 4-related development in a long-running effort.
84+
readme: |
85+
<h2>Objective</h2>
86+
<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>
87+
<h2>The Problem</h2>
88+
<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>
89+
<h2>Proposed Solution</h2>
90+
<p>Establish a designated WG to:</p>
91+
<ul>
92+
<li>Track all Quarkus 4‑related issues and PRs (using label triage/quarkus-4)</li>
93+
<li>Maintain a GitHub project board for feature status, blockers, and timelines</li>
94+
<li>Coordinate across teams (core, extensions, platform, tooling)</li>
95+
<li>Surface migration considerations and flag impacts (e.g. new --add-opens needs, optimized defaults) - useful to create the migration guide and rules</li>
96+
<li>Publish ADRs, migration guides, and summary docs</li>
97+
</ul>
98+
<h2>Definition of Done</h2>
99+
<p>This WG will be considered complete when:</p>
100+
<ul>
101+
<li>Quarkus 4 GA is released (including the platform)</li>
102+
<li>All major features are merged and tested</li>
103+
<li>Migration documentation is publicly available</li>
104+
</ul>
105+
<h2>Organizing the Work</h2>
106+
<p>Coordination via:</p>
107+
<ul>
108+
<li>GitHub Discussions: use design‑discussions category</li>
109+
<li>Issues/PRs: label with <code>triage/quarkus-4</code></li>
110+
<li>Project board to track status</li>
111+
</ul>
112+
<h2>Expected Timeline:</h2>
113+
<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>
114+
status: on track
115+
lts: false
116+
completed: false
117+
last-activity: 2025-09-09
118+
last-update-date: 2025-09-08
119+
last-update: |
120+
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.).
121121
- title: "Java 25 support"
122122
board-url: "https://github.com/orgs/quarkusio/projects/59"
123123
short-description: |

0 commit comments

Comments
 (0)