Sync working groups

Author: actions-user

_data/wg.yaml

@@ -1,35 +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: staled
-      completed: false
-      last-activity: 2025-02-24
-      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-02-18
-      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: "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.
@@ -48,7 +18,7 @@ working-groups:
         </ul>
       status: on track
       completed: false
-      last-activity: 2025-02-18
+      last-activity: 2025-02-25
       last-update-date: 2025-02-04
       last-update: |
         We have the first clean CI! It resolves the following issues:
@@ -68,6 +38,36 @@ 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.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-02-24
+      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-02-18
+      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: "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.
@@ -287,12 +287,13 @@ working-groups:
         <h1>When will this working group be done?</h1>
         <p>When Quarkus has an active working governance model in place and all major work items around setting up Quarkus at CommonHaus are completed - after that, its expected things will just be iteratively improved, and the dedicated working group will not be needed (others might start to continue more specific efforts).</p>
         <p>The majority of the work must be done before the end of December 2024. The latest deadline for CommonHaus is April 2025, when the bootstrap period of CommonHaus ends.</p>
-      status: staled
+      status: at risk
       completed: false
       last-activity: 2024-10-28
-      last-update-date: 2024-10-28
+      last-update-date: 2025-02-25
       last-update: |
-        Still on track. 
-        In the last period, we organized an international manhunt to find the owner of the quarkus.dev DNS name :-) We were able to identify the owner, and everything is fine. `quarkus.io` and `quarkus.dev` should be transferred to the foundation at some point.
+        Started working on full list of repos and infrastructure that needs clarifying. Can't share it publically yet due to red hat infrastructure details but will soon share.
+        
+        Marking as risk as deadline april 1st is looming and still things to define. 
         
-        Also, Emmanuel opened an ADR to discuss the reviewing process, which is essential for the project's open governance.
+        There is a Quarkus f2f meeting next week that could clarify/move things forward and start to share more publically as things get moved over from internal IT.