Skip to content

Commit e51eff3

Browse files
actions-useractions-user
committed
Sync working groups
1 parent 5db2592 commit e51eff3

1 file changed

Lines changed: 44 additions & 44 deletions

File tree

‎_data/wg.yaml‎

Lines changed: 44 additions & 44 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,49 @@
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: staled
38+
lts: false
39+
completed: false
40+
last-activity: 2026-01-16
41+
last-update-date: 2025-10-27
42+
last-update: |
43+
In the last month, the WG - Quarkus 4 did not close any issues but opened a new issue focused on improving the Event bus. Remember that this working group is about collecting features for Quarkus 4.
44+
On the technical side, we made progress on the Mutiny Bindings for Vert.x 5.
45+
46+
(This status update was automatically generated using AI.)
347
- title: "Observability.Next"
448
board-url: "https://github.com/orgs/quarkusio/projects/42"
549
short-description: |
@@ -106,50 +150,6 @@ working-groups:
106150
point-of-contact: "@holly-cummins (@<strong>Holly Cummins</strong> on Zulip)"
107151
proposal: https://github.com/quarkusio/quarkus/discussions/41867
108152
discussion: https://quarkusio.zulipchat.com/#narrow/channel/187038-dev/topic/WG.20.2330.20Test.20Classloading.20chatter/
109-
- title: "Quarkus 4"
110-
board-url: "https://github.com/orgs/quarkusio/projects/51"
111-
short-description: |
112-
The Quarkus 4 working group aims to coordinate and track all Quarkus 4-related development in a long-running effort.
113-
readme: |
114-
<h2>Objective</h2>
115-
<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>
116-
<h2>The Problem</h2>
117-
<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>
118-
<h2>Proposed Solution</h2>
119-
<p>Establish a designated WG to:</p>
120-
<ul>
121-
<li>Track all Quarkus 4‑related issues and PRs (using label triage/quarkus-4)</li>
122-
<li>Maintain a GitHub project board for feature status, blockers, and timelines</li>
123-
<li>Coordinate across teams (core, extensions, platform, tooling)</li>
124-
<li>Surface migration considerations and flag impacts (e.g. new --add-opens needs, optimized defaults) - useful to create the migration guide and rules</li>
125-
<li>Publish ADRs, migration guides, and summary docs</li>
126-
</ul>
127-
<h2>Definition of Done</h2>
128-
<p>This WG will be considered complete when:</p>
129-
<ul>
130-
<li>Quarkus 4 GA is released (including the platform)</li>
131-
<li>All major features are merged and tested</li>
132-
<li>Migration documentation is publicly available</li>
133-
</ul>
134-
<h2>Organizing the Work</h2>
135-
<p>Coordination via:</p>
136-
<ul>
137-
<li>GitHub Discussions: use design‑discussions category</li>
138-
<li>Issues/PRs: label with <code>triage/quarkus-4</code></li>
139-
<li>Project board to track status</li>
140-
</ul>
141-
<h2>Expected Timeline:</h2>
142-
<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>
143-
status: staled
144-
lts: false
145-
completed: false
146-
last-activity: 2026-01-14
147-
last-update-date: 2025-10-27
148-
last-update: |
149-
In the last month, the WG - Quarkus 4 did not close any issues but opened a new issue focused on improving the Event bus. Remember that this working group is about collecting features for Quarkus 4.
150-
On the technical side, we made progress on the Mutiny Bindings for Vert.x 5.
151-
152-
(This status update was automatically generated using AI.)
153153
- title: "Dev Services Lifecycle"
154154
board-url: "https://github.com/orgs/quarkusio/projects/49"
155155
short-description: |

0 commit comments

Comments
 (0)