Sync working groups

Author: actions-user

_data/wg.yaml

@@ -1,5 +1,46 @@
 ---
 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: 2025-10-15
+      last-update-date: 2025-09-08
+      last-update: |
+        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.).
     - title: "Quarkus 3.15 LTS"
       board-url: "https://github.com/orgs/quarkusio/projects/28"
       short-description: |
@@ -523,47 +564,6 @@ working-groups:
         (This status update was automatically generated using AI.)
       point-of-contact: "@brunobat"
       proposal: https://github.com/quarkusio/quarkus/discussions/44423
-    - 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: 2025-09-09
-      last-update-date: 2025-09-08
-      last-update: |
-        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.).
     - title: "Quarkus to the CommonHaus Foundation"
       board-url: "https://github.com/orgs/quarkusio/projects/38"
       short-description: |