Sync working groups

Author: actions-user

_data/wg.yaml

@@ -1,5 +1,48 @@
 ---
 working-groups:
+    - title: "Quarkus 4"
+      board-url: "https://github.com/orgs/quarkusio/projects/51"
+      short-description: |
+        The Quarkus 4 working group aims to coordinate and track all Quarkus 4-related development in a long-running effort.
+      readme: |
+        <h2>Objective</h2>
+        <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>
+        <h2>The Problem</h2>
+        <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>
+        <h2>Proposed Solution</h2>
+        <p>Establish a designated WG to:</p>
+        <ul>
+        <li>Track all Quarkus 4‑related issues and PRs (using label triage/quarkus-4)</li>
+        <li>Maintain a GitHub project board for feature status, blockers, and timelines</li>
+        <li>Coordinate across teams (core, extensions, platform, tooling)</li>
+        <li>Surface migration considerations and flag impacts (e.g. new --add-opens needs, optimized defaults) - useful to create the migration guide and rules</li>
+        <li>Publish ADRs, migration guides, and summary docs</li>
+        </ul>
+        <h2>Definition of Done</h2>
+        <p>This WG will be considered complete when:</p>
+        <ul>
+        <li>Quarkus 4 GA is released (including the platform)</li>
+        <li>All major features are merged and tested</li>
+        <li>Migration documentation is publicly available</li>
+        </ul>
+        <h2>Organizing the Work</h2>
+        <p>Coordination via:</p>
+        <ul>
+        <li>GitHub Discussions: use design‑discussions category</li>
+        <li>Issues/PRs: label with <code>triage/quarkus-4</code></li>
+        <li>Project board to track status</li>
+        </ul>
+        <h2>Expected Timeline:</h2>
+        <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>
+      status: on track
+      lts: false
+      completed: false
+      last-activity: 2026-05-07
+      last-update-date: 2026-03-30
+      last-update: |
+        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.
+        
+        (This status update was automatically generated using AI.)
     - title: "Quarkus Data"
       board-url: "https://github.com/orgs/quarkusio/projects/50"
       short-description: |
@@ -182,49 +225,6 @@ working-groups:
       point-of-contact: "@maxandersen"
       proposal: https://github.com/quarkusio/quarkus/discussions/53667
       discussion: https://quarkusio.zulipchat.com/#narrow/channel/187038-dev/topic/WG.20-.20Quarkus.20Terminal/with/587817394
-    - title: "Quarkus 4"
-      board-url: "https://github.com/orgs/quarkusio/projects/51"
-      short-description: |
-        The Quarkus 4 working group aims to coordinate and track all Quarkus 4-related development in a long-running effort.
-      readme: |
-        <h2>Objective</h2>
-        <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>
-        <h2>The Problem</h2>
-        <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>
-        <h2>Proposed Solution</h2>
-        <p>Establish a designated WG to:</p>
-        <ul>
-        <li>Track all Quarkus 4‑related issues and PRs (using label triage/quarkus-4)</li>
-        <li>Maintain a GitHub project board for feature status, blockers, and timelines</li>
-        <li>Coordinate across teams (core, extensions, platform, tooling)</li>
-        <li>Surface migration considerations and flag impacts (e.g. new --add-opens needs, optimized defaults) - useful to create the migration guide and rules</li>
-        <li>Publish ADRs, migration guides, and summary docs</li>
-        </ul>
-        <h2>Definition of Done</h2>
-        <p>This WG will be considered complete when:</p>
-        <ul>
-        <li>Quarkus 4 GA is released (including the platform)</li>
-        <li>All major features are merged and tested</li>
-        <li>Migration documentation is publicly available</li>
-        </ul>
-        <h2>Organizing the Work</h2>
-        <p>Coordination via:</p>
-        <ul>
-        <li>GitHub Discussions: use design‑discussions category</li>
-        <li>Issues/PRs: label with <code>triage/quarkus-4</code></li>
-        <li>Project board to track status</li>
-        </ul>
-        <h2>Expected Timeline:</h2>
-        <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>
-      status: on track
-      lts: false
-      completed: false
-      last-activity: 2026-05-06
-      last-update-date: 2026-03-30
-      last-update: |
-        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.
-        
-        (This status update was automatically generated using AI.)
     - title: "Dev Services Lifecycle"
       board-url: "https://github.com/orgs/quarkusio/projects/49"
       short-description: |