Sync working groups

Author: actions-user

_data/wg.yaml

@@ -1,16 +1,5 @@
 ---
 working-groups:
-    - 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: 2025-02-03
-      last-update-date: 2024-12-17
-      last-update: |
-        Starting tracking tasks fro the 3.19 LTS.
     - 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.
@@ -78,12 +67,23 @@ working-groups:
         </ul>
       status: on track
       completed: false
-      last-activity: 2025-01-30
+      last-activity: 2025-02-03
       last-update-date: 2025-01-30
       last-update: |
         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: on track
+      completed: false
+      last-activity: 2025-02-03
+      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.