|
1 | 1 | --- |
2 | 2 | working-groups: |
| 3 | + - title: "Quarkus 3.15 LTS" |
| 4 | + board-url: "https://github.com/orgs/quarkusio/projects/28" |
| 5 | + 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) |
| 6 | + readme: | |
| 7 | + <p>This working group uses a different board:</p> |
| 8 | + <ul> |
| 9 | + <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> |
| 10 | + <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> |
| 11 | + <li>The <code>in progress</code> means that the work has started and should be completed before the TLS cut date</li> |
| 12 | + <li>The <code>done</code> column means that the issues have been completed</li> |
| 13 | + </ul> |
| 14 | + status: staled |
| 15 | + completed: false |
| 16 | + last-activity: 2025-03-19 |
| 17 | + last-update-date: 2024-10-28 |
| 18 | + last-update: | |
| 19 | + Everything is fine for now. |
| 20 | + |
| 21 | + There are discussions on defining a regular cadence release. We will communicate when we have more details. |
3 | 22 | - title: "Gizmo 2" |
4 | 23 | board-url: "https://github.com/orgs/quarkusio/projects/43" |
5 | 24 | short-description: Gizmo 2 related tasks |
@@ -72,25 +91,6 @@ working-groups: |
72 | 91 | point-of-contact: "@holly-cummins (@<strong>Holly Cummins</strong> on Zulip)" |
73 | 92 | proposal: https://github.com/quarkusio/quarkus/discussions/41867 |
74 | 93 | discussion: https://quarkusio.zulipchat.com/#narrow/channel/187038-dev/topic/WG.20.2330.20Test.20Classloading.20chatter/ |
75 | | - - title: "Quarkus 3.15 LTS" |
76 | | - board-url: "https://github.com/orgs/quarkusio/projects/28" |
77 | | - 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) |
78 | | - readme: | |
79 | | - <p>This working group uses a different board:</p> |
80 | | - <ul> |
81 | | - <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> |
82 | | - <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> |
83 | | - <li>The <code>in progress</code> means that the work has started and should be completed before the TLS cut date</li> |
84 | | - <li>The <code>done</code> column means that the issues have been completed</li> |
85 | | - </ul> |
86 | | - status: staled |
87 | | - completed: false |
88 | | - last-activity: 2025-03-12 |
89 | | - last-update-date: 2024-10-28 |
90 | | - last-update: | |
91 | | - Everything is fine for now. |
92 | | - |
93 | | - There are discussions on defining a regular cadence release. We will communicate when we have more details. |
94 | 94 | - title: "Observability.Next" |
95 | 95 | board-url: "https://github.com/orgs/quarkusio/projects/42" |
96 | 96 | 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. |
|
0 commit comments