Skip to content

Commit 60306d0

Browse files
actions-useractions-user
committed
Sync working groups
1 parent c20e459 commit 60306d0

1 file changed

Lines changed: 43 additions & 43 deletions

File tree

‎_data/wg.yaml‎

Lines changed: 43 additions & 43 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,48 @@
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: 2026-06-02
41+
last-update-date: 2026-05-26
42+
last-update: |
43+
Big strides this week on the Quarkus 4 effort! We finally closed out the upgrade to Vert.x 5, including migrating the OpenTelemetry extension and several others. Also got the OpenShift, Kubernetes, and MongoDB dev services to behave and not start during augmentation.
44+
45+
(This status update was automatically generated using AI.)
346
- title: "Quarkus Data"
447
board-url: "https://github.com/orgs/quarkusio/projects/50"
548
short-description: |
@@ -445,49 +488,6 @@ working-groups:
445488
last-update-date: 2025-11-03
446489
last-update: |
447490
3.15 is now EOL.
448-
- title: "Quarkus 4"
449-
board-url: "https://github.com/orgs/quarkusio/projects/51"
450-
short-description: |
451-
The Quarkus 4 working group aims to coordinate and track all Quarkus 4-related development in a long-running effort.
452-
readme: |
453-
<h2>Objective</h2>
454-
<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>
455-
<h2>The Problem</h2>
456-
<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>
457-
<h2>Proposed Solution</h2>
458-
<p>Establish a designated WG to:</p>
459-
<ul>
460-
<li>Track all Quarkus 4‑related issues and PRs (using label triage/quarkus-4)</li>
461-
<li>Maintain a GitHub project board for feature status, blockers, and timelines</li>
462-
<li>Coordinate across teams (core, extensions, platform, tooling)</li>
463-
<li>Surface migration considerations and flag impacts (e.g. new --add-opens needs, optimized defaults) - useful to create the migration guide and rules</li>
464-
<li>Publish ADRs, migration guides, and summary docs</li>
465-
</ul>
466-
<h2>Definition of Done</h2>
467-
<p>This WG will be considered complete when:</p>
468-
<ul>
469-
<li>Quarkus 4 GA is released (including the platform)</li>
470-
<li>All major features are merged and tested</li>
471-
<li>Migration documentation is publicly available</li>
472-
</ul>
473-
<h2>Organizing the Work</h2>
474-
<p>Coordination via:</p>
475-
<ul>
476-
<li>GitHub Discussions: use design‑discussions category</li>
477-
<li>Issues/PRs: label with <code>triage/quarkus-4</code></li>
478-
<li>Project board to track status</li>
479-
</ul>
480-
<h2>Expected Timeline:</h2>
481-
<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>
482-
status: on track
483-
lts: false
484-
completed: false
485-
last-activity: 2026-06-02
486-
last-update-date: 2026-05-26
487-
last-update: |
488-
Big strides this week on the Quarkus 4 effort! We finally closed out the upgrade to Vert.x 5, including migrating the OpenTelemetry extension and several others. Also got the OpenShift, Kubernetes, and MongoDB dev services to behave and not start during augmentation.
489-
490-
(This status update was automatically generated using AI.)
491491
- title: "Test classloading"
492492
board-url: "https://github.com/orgs/quarkusio/projects/30"
493493
short-description: |

0 commit comments

Comments
 (0)