|
1 | 1 | --- |
2 | 2 | working-groups: |
| 3 | + - title: "Gizmo 2" |
| 4 | + board-url: "https://github.com/orgs/quarkusio/projects/43" |
| 5 | + short-description: | |
| 6 | + Gizmo 2 related tasks |
| 7 | + readme: | |
| 8 | + <p>This _working group aims to make the <a href="https://github.com/dmlloyd/gizmo/tree/gizmo2">Gizmo 2 POC</a> production-ready and integrate it into Quarkus core.</p> |
| 9 | + <ul> |
| 10 | + <li>Point of contact: @mkouba (@<strong>Martin Kouba</strong> on Zulip)</li> |
| 11 | + <li>Proposal: https://github.com/quarkusio/quarkus/discussions/46627</li> |
| 12 | + <li>Discussion: <a href="https://quarkusio.zulipchat.com/#narrow/channel/187038-dev/topic/Gizmo.202.2Ex.20WG.20chat">Zulip topic</a></li> |
| 13 | + <li>Deliverable: <a href="https://quarkus.io/blog/arc-migrates-to-gizmo2/">Blog</a></li> |
| 14 | + </ul> |
| 15 | + status: complete |
| 16 | + lts: false |
| 17 | + completed: true |
| 18 | + last-activity: 2025-11-03 |
| 19 | + last-update-date: 2025-11-03 |
| 20 | + last-update: | |
| 21 | + While there are still tons of work to do on Gizmo 2, it meets the definition of done from the proposal. |
| 22 | + Arc got migrated to Gizmo 2 - see https://quarkus.io/blog/arc-migrates-to-gizmo2/. |
| 23 | + deliverable: <a rel="nofollow" href="https://quarkus.io/blog/arc-migrates-to-gizmo2/">Blog</a> |
| 24 | + point-of-contact: "@mkouba (@<strong>Martin Kouba</strong> on Zulip)" |
| 25 | + proposal: https://github.com/quarkusio/quarkus/discussions/46627 |
| 26 | + discussion: https://quarkusio.zulipchat.com/#narrow/channel/187038-dev/topic/Gizmo.202.2Ex.20WG.20chat |
| 27 | + - title: "Quarkus 3.27 LTS" |
| 28 | + board-url: "https://github.com/orgs/quarkusio/projects/65" |
| 29 | + short-description: | |
| 30 | + This working group aims to track the effort around the Quarkus 3.27 LTS version. |
| 31 | + readme: | |
| 32 | + <p>All the tasks related to the 3.27 LTS, including issues with backport, release process, and so on.</p> |
| 33 | + <hr /> |
| 34 | + <ul> |
| 35 | + <li>Backports: https://github.com/orgs/quarkusio/projects/62</li> |
| 36 | + </ul> |
| 37 | + status: on track |
| 38 | + lts: true |
| 39 | + completed: false |
| 40 | + last-activity: 2025-11-03 |
| 41 | + - title: "Quarkus 3.15 LTS" |
| 42 | + board-url: "https://github.com/orgs/quarkusio/projects/28" |
| 43 | + short-description: | |
| 44 | + This WG focuses on defining the issues we would like to have in the next-to-be LTS (Quarkus 3.14/3.15) |
| 45 | + readme: | |
| 46 | + <p>This working group uses a different board:</p> |
| 47 | + <ul> |
| 48 | + <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> |
| 49 | + <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> |
| 50 | + <li>The <code>in progress</code> means that the work has started and should be completed before the TLS cut date</li> |
| 51 | + <li>The <code>done</code> column means that the issues have been completed</li> |
| 52 | + </ul> |
| 53 | + status: complete |
| 54 | + lts: true |
| 55 | + completed: true |
| 56 | + last-activity: 2025-11-03 |
| 57 | + last-update-date: 2025-11-03 |
| 58 | + last-update: | |
| 59 | + 3.15 is now EOL. |
3 | 60 | - title: "Observability.Next" |
4 | 61 | board-url: "https://github.com/orgs/quarkusio/projects/42" |
5 | 62 | short-description: | |
@@ -119,13 +176,13 @@ working-groups: |
119 | 176 | <p>Point of contact: @ia3andy (@<strong>Andy Damevin</strong> on Zulip) and @aloubyansky (@<strong>Alexey Loubyansky</strong> on Zulip)</p> |
120 | 177 | </li> |
121 | 178 | </ul> |
122 | | - status: on track |
| 179 | + status: complete |
123 | 180 | lts: false |
124 | | - completed: false |
| 181 | + completed: true |
125 | 182 | last-activity: 2025-11-03 |
126 | 183 | last-update-date: 2025-11-03 |
127 | 184 | last-update: | |
128 | | - @aloubyansky @ia3andy I'm considering closing the working group as the 2 last two issues won't make any progress in the near future. We can handle them separately later. |
| 185 | + Feature shipped - completing this working group! |
129 | 186 | point-of-contact: "@ia3andy (@<strong>Andy Damevin</strong> on Zulip) and @aloubyansky (@<strong>Alexey Loubyansky</strong> on Zulip)" |
130 | 187 | - title: "Java 25 support" |
131 | 188 | board-url: "https://github.com/orgs/quarkusio/projects/59" |
@@ -616,48 +673,6 @@ working-groups: |
616 | 673 | On the technical side, we made progress on the Mutiny Bindings for Vert.x 5. |
617 | 674 | |
618 | 675 | (This status update was automatically generated using AI.) |
619 | | - - title: "Quarkus 3.15 LTS" |
620 | | - board-url: "https://github.com/orgs/quarkusio/projects/28" |
621 | | - short-description: | |
622 | | - This WG focuses on defining the issues we would like to have in the next-to-be LTS (Quarkus 3.14/3.15) |
623 | | - readme: | |
624 | | - <p>This working group uses a different board:</p> |
625 | | - <ul> |
626 | | - <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> |
627 | | - <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> |
628 | | - <li>The <code>in progress</code> means that the work has started and should be completed before the TLS cut date</li> |
629 | | - <li>The <code>done</code> column means that the issues have been completed</li> |
630 | | - </ul> |
631 | | - status: on track |
632 | | - lts: true |
633 | | - completed: false |
634 | | - last-activity: 2025-10-14 |
635 | | - last-update-date: 2025-04-01 |
636 | | - last-update: | |
637 | | - In the last month, the WG - Quarkus 3.15 LTS closed two issues: one regarding the assignment of random ports in the configuration and another updating the Kafka client version to 3.7.2 to address CVE-2024-56128. No new issues were opened, reflecting a commitment to resolving important topics for the upcoming LTS release. |
638 | | - - title: "Gizmo 2" |
639 | | - board-url: "https://github.com/orgs/quarkusio/projects/43" |
640 | | - short-description: | |
641 | | - Gizmo 2 related tasks |
642 | | - readme: | |
643 | | - <p>This _working group aims to make the <a href="https://github.com/dmlloyd/gizmo/tree/gizmo2">Gizmo 2 POC</a> production-ready and integrate it into Quarkus core.</p> |
644 | | - <ul> |
645 | | - <li>Point of contact: @mkouba (@<strong>Martin Kouba</strong> on Zulip)</li> |
646 | | - <li>Proposal: https://github.com/quarkusio/quarkus/discussions/46627</li> |
647 | | - <li>Discussion: <a href="https://quarkusio.zulipchat.com/#narrow/channel/187038-dev/topic/Gizmo.202.2Ex.20WG.20chat">Zulip topic</a></li> |
648 | | - <li>Deliverable: TBD</li> |
649 | | - </ul> |
650 | | - status: on track |
651 | | - lts: false |
652 | | - completed: false |
653 | | - last-activity: 2025-10-07 |
654 | | - last-update-date: 2025-10-27 |
655 | | - last-update: | |
656 | | - The working group focused on improving the performance of the generation, but also of the memory usage at runtime. |
657 | | - deliverable: TBD |
658 | | - point-of-contact: "@mkouba (@<strong>Martin Kouba</strong> on Zulip)" |
659 | | - proposal: https://github.com/quarkusio/quarkus/discussions/46627 |
660 | | - discussion: https://quarkusio.zulipchat.com/#narrow/channel/187038-dev/topic/Gizmo.202.2Ex.20WG.20chat |
661 | 676 | - title: "Dev Services Lifecycle" |
662 | 677 | board-url: "https://github.com/orgs/quarkusio/projects/49" |
663 | 678 | short-description: | |
|
0 commit comments