Sync working groups

Author: actions-user

_data/wg.yaml

@@ -1,5 +1,37 @@
 ---
 working-groups:
+    - title: "WebSocket Next"
+      board-url: "https://github.com/orgs/quarkusio/projects/26"
+      short-description: WebSocket-Next related tasks
+      readme: |
+        <p>The WebSocket Next <em>focus group</em> aims to improve our WebSocket experience.</p>
+        <p>Recently, we delivered a new approach to dealing with WebSocket (both for the server and client). This was the first step. There are still a few areas to improve, such as documentation, security, observability, and testability. The goal of this focus group is to track these efforts.</p>
+        <ul>
+        <li>Point of contact: @mkouba (@<strong>Martin Kouba</strong>  on Zulip)</li>
+        <li>Proposal: https://github.com/quarkusio/quarkus/discussions/38473</li>
+        <li>Deliverable: <a href="https://www.youtube.com/watch?v=9ALOZrlP7TE">Quarkus Insight</a></li>
+        </ul>
+      status: complete
+      completed: true
+      last-activity: 2024-12-17
+      last-update-date: 2024-12-16
+      last-update: |
+        Completed! 
+        See https://quarkus.io/guides/websockets-next-tutorial and https://quarkus.io/guides/websockets-next-reference
+      deliverable: <a rel="nofollow" href="https://www.youtube.com/watch?v=9ALOZrlP7TE">Quarkus Insight</a>
+      point-of-contact: "@mkouba (@<strong>Martin Kouba</strong>  on Zulip)"
+      proposal: https://github.com/quarkusio/quarkus/discussions/38473
+    - 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: on track
+      completed: false
+      last-activity: 2024-12-17
+      last-update-date: 2024-12-17
+      last-update: |
+        Starting tracking tasks fro the 3.19 LTS.
     - 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.
@@ -28,17 +60,6 @@ working-groups:
       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.19 LTS"
-      board-url: "https://github.com/orgs/quarkusio/projects/41"
-      short-description: This working group aims to track the effort around the Quarkus 3.19 LTS version.
-      readme: |
-        <p>All the tasks related to the 3.19 LTS, including issues with backport, release process, and so on.</p>
-      status: on track
-      completed: false
-      last-activity: 2024-12-17
-      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)
@@ -58,27 +79,6 @@ working-groups:
         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
-      readme: |
-        <p>The WebSocket Next <em>focus group</em> aims to improve our WebSocket experience.</p>
-        <p>Recently, we delivered a new approach to dealing with WebSocket (both for the server and client). This was the first step. There are still a few areas to improve, such as documentation, security, observability, and testability. The goal of this focus group is to track these efforts.</p>
-        <ul>
-        <li>Point of contact: @mkouba (@<strong>Martin Kouba</strong>  on Zulip)</li>
-        <li>Proposal: https://github.com/quarkusio/quarkus/discussions/38473</li>
-        <li>Deliverable: <a href="https://www.youtube.com/watch?v=9ALOZrlP7TE">Quarkus Insight</a></li>
-        </ul>
-      status: complete
-      completed: true
-      last-activity: 2024-12-16
-      last-update-date: 2024-12-16
-      last-update: |
-        Completed! 
-        See https://quarkus.io/guides/websockets-next-tutorial and https://quarkus.io/guides/websockets-next-reference
-      deliverable: <a rel="nofollow" href="https://www.youtube.com/watch?v=9ALOZrlP7TE">Quarkus Insight</a>
-      point-of-contact: "@mkouba (@<strong>Martin Kouba</strong>  on Zulip)"
-      proposal: https://github.com/quarkusio/quarkus/discussions/38473
     - title: "Quarkus Config and IDEs"
       board-url: "https://github.com/orgs/quarkusio/projects/32"
       short-description: Let's define a format for the files containing the config model we will include in the jars for IDE consumption.