From a068cd2bce588324e988d64fe3c5d117f276079c Mon Sep 17 00:00:00 2001
From: GitHub Action <action@github.com>
Date: Mon, 9 Sep 2024 15:01:57 +0000
Subject: [PATCH] Sync working groups

---
 _data/wg.yaml | 30 +++++++++++++++---------------
 1 file changed, 15 insertions(+), 15 deletions(-)

diff --git a/_data/wg.yaml b/_data/wg.yaml
index 59ce13c3e64..acb72c261e5 100644
--- a/_data/wg.yaml
+++ b/_data/wg.yaml
@@ -1,5 +1,20 @@
 ---
 working-groups:
+    - 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: at risk
+      last-activity: 2024-09-09
+      last-update: |
+        Work is progressing. Still items that will need to be cleaned. Thus still at risk but managable.
     - title: "Moving Quarkus to the CommonHaus Foundation"
       board-url: "https://github.com/orgs/quarkusio/projects/38"
       short-description: Work needed around moving Quarkus to foundation and streamline open governance.
@@ -32,21 +47,6 @@ working-groups:
       last-activity: 2024-09-09
       last-update: |
         Just got started.
-    - 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: at risk
-      last-activity: 2024-09-09
-      last-update: |
-        Work is progressing. Still items that will need to be cleaned. Thus still at risk but managable.
     - 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.