Sync working groups

Author: actions-user

_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-17
+      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.
@@ -17,21 +32,6 @@ working-groups:
         Since we don't have a target date, and progress is being made, I can declare this on track, with only a slightly murky conscience. 
         
         This is a big change, and one which doesn't lend itself well to dividing into smaller chunks. I'm keeping a spreadsheet of build results. In the CI runs, the number of failing jobs was 31 at the last update, and it is now 25. A number of suites, such as `integration-tests/devtools` were failing, and are now passing.
-    - 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-16
-      last-update: |
-        Work is progressing. Still items that will need to be cleaned. Thus still at risk but managable.
     - title: "Enhanced TLS support"
       board-url: "https://github.com/orgs/quarkusio/projects/24"
       short-description: Track the progress around the new TLS configuration centralization and new features (like Let's Encrypt, Cert-Manager, and local experience...)