Sync working groups

Author: actions-user

_data/wg.yaml

@@ -1,21 +1,5 @@
 ---
 working-groups:
-    - title: "Gizmo 2"
-      board-url: "https://github.com/orgs/quarkusio/projects/43"
-      short-description: Gizmo 2 related tasks
-      readme: |
-        <p>This _working group aims to make the <a href="https://github.com/dmlloyd/gizmo/tree/gizmo2">Gizmo 2 POC</a> production-ready and integrate it into Quarkus core.</p>
-        <ul>
-        <li>Point of contact: @mkouba (@<strong>Martin Kouba</strong>  on Zulip)</li>
-        <li>Proposal: https://github.com/quarkusio/quarkus/discussions/46627</li>
-        <li>Deliverable: TBD</li>
-        </ul>
-      status: inactive
-      completed: false
-      last-activity: 2025-03-11
-      deliverable: TBD
-      point-of-contact: "@mkouba (@<strong>Martin Kouba</strong>  on Zulip)"
-      proposal: https://github.com/quarkusio/quarkus/discussions/46627
     - title: "Test classloading"
       board-url: "https://github.com/orgs/quarkusio/projects/30"
       short-description: The goal of this working group is to rewrite Quarkus's test classloading, so that tests are run in the same classloader as the application under tests, and Quarkus extensions can do "Quarkus-y" manipulations of test classes.
@@ -34,13 +18,59 @@ working-groups:
         </ul>
       status: on track
       completed: false
-      last-activity: 2025-03-10
+      last-activity: 2025-03-11
       last-update-date: 2025-03-03
       last-update: |
         Code cleanup underway to remove TODOs and the most egregious hacks. CI is (mostly, sometimes) green: https://github.com/quarkusio/quarkus/actions/runs/13628335866/job/38090976898
       point-of-contact: "@holly-cummins (@<strong>Holly Cummins</strong>  on Zulip)"
       proposal: https://github.com/quarkusio/quarkus/discussions/41867
       discussion: https://quarkusio.zulipchat.com/#narrow/channel/187038-dev/topic/WG.20.2330.20Test.20Classloading.20chatter/
+    - title: "Quarkus 3.20 LTS"
+      board-url: "https://github.com/orgs/quarkusio/projects/41"
+      short-description: This working group aims to track the effort around the Quarkus 3.20 LTS version.
+      readme: |
+        <p>All the tasks related to the 3.20 LTS, including issues with backport, release process, and so on.</p>
+      status: staled
+      completed: false
+      last-activity: 2025-03-11
+      last-update-date: 2024-12-17
+      last-update: |
+        Starting tracking tasks fro the 3.19 LTS.
+    - title: "Quarkus 3.15 LTS"
+      board-url: "https://github.com/orgs/quarkusio/projects/28"
+      short-description: This WG focuses on defining the issues we would like to have in the next-to-be LTS (Quarkus 3.14/3.15)
+      readme: |
+        <p>This working group uses a different board:</p>
+        <ul>
+        <li>The <code>under discussion</code> column contains the issues we would like to have in the next LTS but are still under consideration.</li>
+        <li>The <code>out of scope</code> column contains the issues under discussion' that won't be included. The reason can be time or technical...</li>
+        <li>The <code>in progress</code> means that the work has started and should be completed before the TLS cut date</li>
+        <li>The <code>done</code> column means that the issues have been completed</li>
+        </ul>
+      status: staled
+      completed: false
+      last-activity: 2025-03-11
+      last-update-date: 2024-10-28
+      last-update: |
+        Everything is fine for now. 
+        
+        There are discussions on defining a regular cadence release. We will communicate when we have more details.
+    - title: "Gizmo 2"
+      board-url: "https://github.com/orgs/quarkusio/projects/43"
+      short-description: Gizmo 2 related tasks
+      readme: |
+        <p>This _working group aims to make the <a href="https://github.com/dmlloyd/gizmo/tree/gizmo2">Gizmo 2 POC</a> production-ready and integrate it into Quarkus core.</p>
+        <ul>
+        <li>Point of contact: @mkouba (@<strong>Martin Kouba</strong>  on Zulip)</li>
+        <li>Proposal: https://github.com/quarkusio/quarkus/discussions/46627</li>
+        <li>Deliverable: TBD</li>
+        </ul>
+      status: inactive
+      completed: false
+      last-activity: 2025-03-11
+      deliverable: TBD
+      point-of-contact: "@mkouba (@<strong>Martin Kouba</strong>  on Zulip)"
+      proposal: https://github.com/quarkusio/quarkus/discussions/46627
     - title: "Observability.Next"
       board-url: "https://github.com/orgs/quarkusio/projects/42"
       short-description: Observability.Next is a strategic initiative to modernize the observability stack within the Quarkus framework, aiming to streamline and enhance its ability to monitor and manage distributed systems.
@@ -114,36 +144,6 @@ working-groups:
         The initiative just started.
       point-of-contact: "@brunobat"
       proposal: https://github.com/quarkusio/quarkus/discussions/44423
-    - title: "Quarkus 3.20 LTS"
-      board-url: "https://github.com/orgs/quarkusio/projects/41"
-      short-description: This working group aims to track the effort around the Quarkus 3.20 LTS version.
-      readme: |
-        <p>All the tasks related to the 3.20 LTS, including issues with backport, release process, and so on.</p>
-      status: staled
-      completed: false
-      last-activity: 2025-03-04
-      last-update-date: 2024-12-17
-      last-update: |
-        Starting tracking tasks fro the 3.19 LTS.
-    - title: "Quarkus 3.15 LTS"
-      board-url: "https://github.com/orgs/quarkusio/projects/28"
-      short-description: This WG focuses on defining the issues we would like to have in the next-to-be LTS (Quarkus 3.14/3.15)
-      readme: |
-        <p>This working group uses a different board:</p>
-        <ul>
-        <li>The <code>under discussion</code> column contains the issues we would like to have in the next LTS but are still under consideration.</li>
-        <li>The <code>out of scope</code> column contains the issues under discussion' that won't be included. The reason can be time or technical...</li>
-        <li>The <code>in progress</code> means that the work has started and should be completed before the TLS cut date</li>
-        <li>The <code>done</code> column means that the issues have been completed</li>
-        </ul>
-      status: staled
-      completed: false
-      last-activity: 2025-03-03
-      last-update-date: 2024-10-28
-      last-update: |
-        Everything is fine for now. 
-        
-        There are discussions on defining a regular cadence release. We will communicate when we have more details.
     - title: "WebSocket Next"
       board-url: "https://github.com/orgs/quarkusio/projects/26"
       short-description: WebSocket-Next related tasks